Hi All, I am getting below error while booting my MacBook Air M1. I tried OS Upgrade , SMS , NVRAM , PRAM Reset but its not working . In safe mode the laptop is working fine. Current OS : Catalina 10.15.7 panic(cpu 0 caller 0xffffff801b447cba): Kernel trap at 0xffffff801b9f7938, type 14=page fault, registers: CR0: 0x0000000080010033, CR2: 0xffffff80d8e87760, CR3: 0x000000024d7d802e, CR4: 0x00000000003626e0 RAX: 0xffffff80d8e876d8, RBX: 0xffffff803133f7c0, RCX: 0x0000000000000004, RDX: 0xffffff80ebab9908 RSP: 0xffffff812672b910, RBP: 0xffffff812672b940, RSI: 0xffffff7f9da23e70, RDI: 0xffffff801be23248 R8: 0x0000000000000001, R9: 0x0000000000000004, R10: 0x0000000000000001, R11: 0xffffff801bdf5280 R12: 0x0000000000000004, R13: 0xffffff80ebab9908, R14: 0xffffff80ebab6000, R15: 0xffffff7f9da23e70 RFL: 0x0000000000010246, RIP: 0xffffff801b9f7938, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff80d8e87760, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffff812672b370 : 0xffffff801b31b54d 0xffffff812672b3c0 : 0xffffff801b455d85 0xffffff812672b400 : 0xffffff801b44790e 0xffffff812672b450 : 0xffffff801b2c1a40 0xffffff812672b470 : 0xffffff801b31ac17 0xffffff812672b570 : 0xffffff801b31b007 0xffffff812672b5c0 : 0xffffff801bac03bc 0xffffff812672b630 : 0xffffff801b447cba 0xffffff812672b7b0 : 0xffffff801b4479b8 0xffffff812672b800 : 0xffffff801b2c1a40 0xffffff812672b820 : 0xffffff801b9f7938 0xffffff812672b940 : 0xffffff7f9d9cbd10 0xffffff812672b9a0 : 0xffffff7f9d88ea8f 0xffffff812672ba30 : 0xffffff7f9d88e8ec 0xffffff812672bac0 : 0xffffff801ba522ce 0xffffff812672bb10 : 0xffffff7f9d894f98 0xffffff812672bb60 : 0xffffff801ba5b4f3 0xffffff812672bca0 : 0xffffff801b404612 0xffffff812672bdb0 : 0xffffff801b3212c8 0xffffff812672be10 : 0xffffff801b2f7bd5 0xffffff812672be70 : 0xffffff801b30ea02 0xffffff812672bf00 : 0xffffff801b42d095 0xffffff812672bfa0 : 0xffffff801b2c2226 Kernel Extensions in backtrace: com.apple.iokit.IOGraphicsFamily(576.2)[0821E1B7-9024-3953-97BB-992587177A8C]@0xffffff7f9d872000->0xffffff7f9d8c2fff dependency: com.apple.iokit.IOPCIFamily(2.9)[26F2BEB0-18DA-3B16-82FE-86A7E6EA9677]@0xffffff7f9bf02000 com.apple.driver.AppleIntelBDWGraphicsFramebuffer(14.0.7)[8657F9F6-11CF-37B1-B070-701A6BCA36B3]@0xffffff7f9d9ba000->0xffffff7f9db51fff dependency: com.apple.iokit.IOPCIFamily(2.9)[26F2BEB0-18DA-3B16-82FE-86A7E6EA9677]@0xffffff7f9bf02000 dependency: com.apple.iokit.IOACPIFamily(1.4)[EEA1F8DE-7566-3725-A90B-FF30414CAC1B]@0xffffff7f9bef0000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.7.4)[D8A0CDBA-825E-327C-A749-D65A6565023A]@0xffffff7f9d8ec000 dependency: com.apple.iokit.IOReportFamily(47)[2582E4D4-95E3-35F6-9E36-3D3503E7D000]@0xffffff7f9be30000 dependency: com.apple.AppleGraphicsDeviceControl(5.2.7)[9B35EBE6-D428-3E98-9193-ADF0EB8C9B14]@0xffffff7f9d9b0000 dependency: com.apple.iokit.IOGraphicsFamily(576.2)[0821E1B7-9024-3953-97BB-992587177A8C]@0xffffff7f9d872000 BSD process name corresponding to current thread: WindowServer Mac OS version: 19H2026 Kernel version: Darwin Kernel Version 19.6.0: Tue Jun 21 21:18:39 PDT 2022; root:xnu-6153.141.66~1/RELEASE_X86_64 Kernel UUID: D5630E55-7695-313B-B468-6347805B0B6F Kernel slide: 0x000000001b000000 Kernel text base: 0xffffff801b200000 __HIB text base: 0xffffff801b100000 System model name: MacBookAir7,2 (Mac-937CB26E2E02BB01) System shutdown begun: NO Panic diags file available: YES (0x0) System uptime in nanoseconds: 15258441387 last loaded kext at 14651290543: >AudioAUUC 1.70 (addr 0xffffff7f9ea40000, size 28672)

After an update to Sonoma 14.1.2, ALL of my printers are offline. I restarted the printers and my computer. Nothing.

I was getting continued prompts to enter my password for some code signing and eventually discovered that I could unlock the system keychain, which I did. However, it keeps locking by itself, seemingly when I click on another chain, and possibly even by itself sometimes. The "Login" window has the option to change lock settings but it is current configured to never lock. Any idea how to fix this? This is on macOS 10.15 which I still need to keep around to build versions of my product for older systems. Thanks in advance

After installing the latest stable version of Chromium, I have been getting the following warnings when running an XProtect Remediator scan. I'm not sure if this is a bad issue, but I think it is something Apple should look at. Thanks. Latest version of XProtectPayloads_10_15-120 now shows the following: 2023-12-03 14:45:17.487 BadGacha 👉 no status_message report time 0.0000000 {"process":{"pid":2265,"name":"crashpad_handler"},"status":null,"action":"report"} 2023-12-03 14:45:17.488 BadGacha 👉 no status_message report time 0.0000000 {"process":{"pid":2263,"name":"GoogleSoftwareUpdateAgent"},"status":null,"action":"report"} 2023-12-03 14:45:17.488 BadGacha 👉 no status_message report time 0.0000000 {"process":{"pid":2235,"name":"crashpad_handler"},"status":null,"action":"report"} 2023-12-03 14:45:17.488 BadGacha 👉 no status_message report time 0.0000000 {"process":{"pid":2233,"name":"GoogleSoftwareUpdateAgent"},"status":null,"action":"report"} 2023-12-03 14:45:17.512 BadGacha NoThreatDetected status_code 20 time 0.0000191

Why doesn't apple allow us to customize our Live Screensaver to a video file of our choice and allow us to set it as a live Screensaver in settings? I shouldn't have to go to a third party app to have a cool artistic customizable background work on my screens. Personally I don't like the way these apps work. They aren't bad but they don't serve my purpose. I have multiple monitors and multiple screens on those monitors and I would like more customizability when it comes to the different backgrounds on these screens. I can set different wallpapers and even the different apple Live Screensavers but it doesn't work nicely if I were to try to add some .mov files of my own in the wallpaper settings. Does anyone have any suggestions or even know how the process of how apple created the source files of these screensavers? It would be great if there was some sort of work around to this.

Hi i've never posted in here but i'm desperate. I've been attempting to start a streaming channel and i've run into every issue imaginable along the way. The latest is that I purchased the new M3 macbook pro and i want to use my old 2015 macbook pro as a display screen. The OLD macbook wont pop up when I go to the display settings in the new mac. However, the new mac pops up in the display settings on the old mac (but this is not want i want to do). I also tried using a traditional HDMI cord in both devices and a USB-C HDMI. Nothing worked. What i want to know is: If the new M3 macbook pro is capable of supporting an external monitor (the system manual claims it is) And if so, how do i turn my old mac (or any external monitor for that matter) into an external monitor. PLEASE HELP - thank you

Sonoma Spotlight image results drag 'n drop not working. thank you

I just updated my macbook pro 2019 to Sonoma 14.2 a couple of days ago and have not been able to get my AWS VPN Client to work since. It was working fine before that. From the logs it appears that it is unable to connect to its endpoint, possibly because openVPN can't connect. I've tried uinstalling and reinstalling the AWS VPN Client. I also tried uninstalling my Sophos antivirus entirely in case it was blocking the VPN. I've done some reading but have found no answer regarding this specific issue. Is there some way to roll back this update? Is there a known workaround for this issue? I use the AWS VPN Client for my work so it's something I use almost every day and it's a real problem that it stopped working now.

Hello, we're trying to running Unity game built for iPhones and iPads on Mac, just like this. https://developer.apple.com/documentation/apple-silicon/running-your-ios-apps-in-macos Getting device model with Unity API works on iPhone and iPad, but we got "iPad8,1"(or iPad8,2/3/4/..., one of the model of iPad Pro 3) for device model, and get "iPadOS 16.6" for Operating system on Mac. They are not Mac device information, how we get Mac device model and Mac OS version if we are running on Mac? (Additionally, not Mac Catalyst.)

Hello, My laptop keeps crashing with a pink screen and restarts every hour. This only happens when I connect my bluetooth devices (apple Magic Mouse 2 and keyboard). In Diagnostics it comes up with a ND007 code. I have updated, wiped, reinstalled software, done a first aid repair, booted in safe mode etc.... Help! Report shows kernel problem as well. Here is the crash report: Translated Report (Full Report Below) Process: SecurityAgent [329] Path: /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent Identifier: com.apple.SecurityAgent Version: 9.0 (55567) Build Info: SecurityAgent-55567000000000000~288 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 92 Date/Time: 2023-11-28 09:55:03.7411 +0000 OS Version: macOS 14.1.1 (23B81) Report Version: 12 Anonymous UUID: A61DC7C5-8273-0ADF-C5EE-9E67D7736272 Time Awake Since Boot: 12 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: SecurityAgent [329] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x187c5111c __pthread_kill + 8 1 libsystem_pthread.dylib 0x187c88cc0 pthread_kill + 288 2 libsystem_c.dylib 0x187b98a40 abort + 180 3 libc++abi.dylib 0x187c406d8 abort_message + 132 4 libc++abi.dylib 0x187c307c8 demangling_terminate_handler() + 348 5 libobjc.A.dylib 0x1878db894 _objc_terminate() + 144 6 libc++abi.dylib 0x187c3fa9c std::__terminate(void (*)()) + 16 7 libc++abi.dylib 0x187c3fa40 std::terminate() + 56 8 libdispatch.dylib 0x187adb924 _dispatch_client_callout + 40 9 libdispatch.dylib 0x187aead9c _dispatch_async_and_wait_invoke + 92 10 libdispatch.dylib 0x187adb910 _dispatch_client_callout + 20 11 libdispatch.dylib 0x187ae9fa8 _dispatch_main_queue_drain + 984 12 libdispatch.dylib 0x187ae9bc0 _dispatch_main_queue_callback_4CF + 44 13 CoreFoundation 0x187da715c CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16 14 CoreFoundation 0x187d64a80 __CFRunLoopRun + 1996 15 CoreFoundation 0x187d63c5c CFRunLoopRunSpecific + 608 16 HIToolbox 0x1922e0448 RunCurrentEventLoopInMode + 292 17 HIToolbox 0x1922e0284 ReceiveNextEventCommon + 648 18 HIToolbox 0x1922dffdc _BlockUntilNextEventMatchingListInModeWithFilter + 76 19 AppKit 0x18b53ec54 _DPSNextEvent + 660 20 AppKit 0x18bd14ebc -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716 21 AppKit 0x18b532100 -[NSApplication run] + 476 22 AppKit 0x18b5093cc NSApplicationMain + 880 23 SecurityAgent 0x1029ef238 main + 428 24 dyld 0x18790d0e0 start + 2360

Hi, I have a macbook pro mid 2014 running on big sur 11.7.10. It often crashes with the first Extensions in backtrace :\n com.apple.driver.usb.AppleUSBCommon(1.0)[49E3B22A-D9C6-3608-94CC-2E4E5597E772]@0xffffff800f6a7000->0xffffff800f6aafff\n Attached is the report, any help with resolving this issue would be greatly appreciated. Kernel Panic Extract Thanks

I was watching a video when I noticed a periodical popping sound. Thought it was a problem with the video, but the issue persists on all other videos or sound tracks. Gets very annoying! Quite disappointed to find this flaw in a brand new Mac Book Pro.

I really need HELP!!! Who,what.how. is controlling my entire Technology. For many years I have been compromised and Apple are unable to help.Apple reformatted my mac 9 times last year. Apple cannot work work it out. Last time I went to store I was advised to HIRE A PRIVATE INVESTIGATOR . I have been and still am going through Hell. Not to mention new devices countless new apple iD's, New phone numbers New Emails Paid for VPN's, Cyber crime reports. My system tells me I am the Administrator but I have very limited permissions If anyone can help or needs further evidence to support please suggest and I will scene shot and upload here.

Something significant changed between MacOS 14.2b1 and the subsequent betas of 14.2. Photoshop, which has been running fine up to the first beta, suddenly refuses to run. The splash screen shows and then the application dies. I've been in communication with Adobe about this, and from the logs they can see that the problem is with MacOS. While this is not a crisis for me since I have three other machines running either 14.2b1, 14.1.1 and 14.1.1, I can complete my tasks, but this is an annoying problem. Attached is a log from beta 3 just to illustrate the problem. ACPL__2023-11-09_22-40-47.131385Z_00.log Just for the record, what is the most efficient way to roll back to the current released version of Sonoma. I've got multiple system backups, so restoration isn't an issue. Just looking for an approach that doesn't require half a day if possible.

Hello - We would like to request the ability to log into a Mac with Touch ID after restart (rather than having to enter our credentials).

Any plans to create a screen that you can fold up then when required unfold in to a circa 28" monitor ready for use with my MacBook?

I know this is a bit late in the Sonoma beta-program, but I wanted to ask here, since I got directed here by Apple support, even though it appears I got Sonoma-14.0 release a day before the non-beta users. And/or I want leave a marker for others with the same needs. I have a 2019 Mac Pro with a dual-port 100GbE ATTO card in it. I run Adobe Premiere, DaVinci Resolve and Autodesk Flame. I would like to do editing and color correcting 4K and 8K frame-based video. 8K video is 4.5GB/sec per DPX stream. (not Gigabit). I connect to a SMB server which is all flash, and runs SMB-Multichannel. This same NIC in a windows box can run 9GB/sec. but in the MacPro, it gets about 3GB/sec. if you run netstat, smbutil, or "nettop" (the builtin MacOS utility) it shows only ONE TCP socket talking to my server on port 445. This is the reason it goes no faster than 3GB/sec. Windows shows 8 or 16, whatever I set it to number of RSS channels, and goes full speed of the NIC. When is MacOS SMB-Multi-channel going to be multi-channel on one NIC port and perform at 8 or 9 GB/sec for a 100Gbit Nic? Nobody wants SMB-MC for "active/passive backup" they want it to go FAST. To prove it is single channel you see only one line: Mac-Pro ~ % netstat -an | grep 445 tcp4 0 0 172.200.5.77.49309 172.200.203.5.445 ESTABLISHED Mac-Pro ~ % smbutil multichannel -a Session: /Volumes/rob-smb Info: Setup Time: 2023-09-25 18:09:01, Multichannel ON: yes, Reconnect Count: 0 Total RX Bytes: 72216 (Packets: 193) Total TX Bytes: 52051 (Packets: 193) id client IF server IF state server ip port speed ======================================================================================================================== M 0 en8 (Ethernet) 16 7 (RSS_0) [session active ] 172.200.203.5 445 100.0 Gb Server NIC: name: NA, idx: 7, type: NA, speed 100.0 Gb, state connected ip_addr: 172.200.203.5 capabilities: RSS_CAPABLE ...see that last line? I would think RSS_CAPABLE means I should be able to connect with multiple SMB channels up to the number of RSS channels configured on the NIC. iperf2 gets > 80Gbit/sec on this 100Gbit ATTO Fastframe with 8 flows (-P 8). So it's not an under-performing network. The results are with or without any "third party ATTO drivers", so please don't blame it on them, because the MacOS mlx5 driver performs the same. It's the SMB client in Big Sur, Catalina, Ventura, Sonoma, which seems to be incomplete.

I performed disk utility first aid on my Macintosh HD volume and all was good as indicated below Running First Aid on “Macintosh HD” (disk3s1s1) Verifying the startup volume will cause this computer to stop responding. Verifying file system. Volume could not be unmounted. Using live mode. Performing fsck_apfs -n -l -x /dev/rdisk3s1 Checking the container superblock. Checking the checkpoint with transaction ID 6455794. Checking the space manager. Checking the space manager free queue trees. Checking the object map. Checking the encryption key structures. Checking volume /dev/rdisk3s1. Checking the APFS volume superblock. The volume Macintosh HD was formatted by newfs_apfs (945.200.129.100.12) and last modified by apfs_kext (2235.40.6.0.2). Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking snapshot 1 of 1 (com.apple.os.update-22777703CDA46B0180D024D76346C01E8072257DCCD38AB80036A71F7EAB46B4) Checking the fsroot tree. Checking the file extent tree. Checking the extent ref tree. Verifying volume object map space. Verifying allocated space. The volume /dev/rdisk3s1 with UUID 0C9FBACC-9665-469A-A543-4BA9BE3DEB85 appears to be OK. File system check exit code is 0. Restoring the original state found as mounted. Operation successful. Then I performed disk utility first aid on my Data volume and saw so many warnings as per below 😭 Running First Aid on “Data” (disk3s5) Verifying the startup volume will cause this computer to stop responding. Verifying file system. Volume could not be unmounted. Using live mode. Performing fsck_apfs -n -l -x /dev/rdisk3s5 Checking the container superblock. Checking the checkpoint with transaction ID 6455648. Checking the space manager. Checking the space manager free queue trees. Checking the object map. Checking the encryption key structures. Checking volume /dev/rdisk3s5. Checking the APFS volume superblock. The volume Data was formatted by newfs_apfs (1933.41.2) and last modified by apfs_kext (2235.40.6.0.2). Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking the document ID tree. Checking the fsroot tree. warning: descendants (2727) of dir-stats object (id 272950) is less than expected (2729) warning: physical_size (6608224256) of dir-stats object (id 272950) is greater than expected (6580809728) warning: descendants (99) of dir-stats object (id 272984) is greater than expected (93) warning: descendants (28439) of dir-stats object (id 272999) is greater than expected (20095) warning: physical_size (1097056256) of dir-stats object (id 273004) is greater than expected (791777280) warning: descendants (609) of dir-stats object (id 728074) is greater than expected (583) warning: physical_size (10944512) of dir-stats object (id 728092) is greater than expected (9261056) warning: physical_size (22069248) of dir-stats object (id 728124) is greater than expected (22036480) warning: physical_size (8192) of dir-stats object (id 10260401) is greater than expected (4096) warning: physical_size (8192) of dir-stats object (id 11230429) is greater than expected (4096) warning: physical_size (8192) of dir-stats object (id 12377650) is greater than expected (4096) Checking the extent ref tree. Checking the file key rolling tree. Verifying volume object map space. The volume /dev/rdisk3s5 with UUID 8AB03DF3-ED19-45FA-A5D0-0818F0BB40C7 was found to be corrupt and needs to be repaired. Verifying allocated space. Performing deferred repairs. The volume /dev/rdisk3s5 with UUID 8AB03DF3-ED19-45FA-A5D0-0818F0BB40C7 appears to be OK. File system check exit code is 0. Restoring the original state found as mounted. Operation successful. I am using time machine backup as a double protection other than iCloud. Are the above warnings will affect my data integrity in the future ? If so what should I do to get rid all of those warnings. I can still use my M1 Macbook Air without any issues so far. But I worry this warnings will create further damage in the future. Thank you guys.

I recently updated to Xcode 15 and have encountered a frustrating issue with my React Native app. Before the update, everything was working perfectly, but now I'm unable to run or build my project. I would greatly appreciate your help in resolving this problem. Issue: After updating to Xcode 15, my React Native app is not working as expected. I'm unable to run the project on my simulator or device. Building the app fails with errors that I didn't encounter in Xcode 14. Additional Information: I have ensured that my Node.js and React Native dependencies are up-to-date. I've tried cleaning the project and deleting derived data, but the issue persists. Xcode 15 is up to date, and I've also updated my macOS to the latest version. Steps I've Tried: Cleaned the project. Deleted derived data. Reinstalled Xcode. Updated NPM packages. Checked for Xcode updates. Verified the Xcode build settings. Environment: macOS version: macOS Sonoma 14 Xcode version: 15.0 Node.js version: 20

The Ventura 13.4 update introduced a display signal lost bug which when the monitor is put to sleep after power saving setting is reached or if manually using the shortcut keys to put sleep the display, it wakes up the monitor briefly then tries to go back to sleep for 15 seconds and then wakes up with the “no signal” warning in an infinite loop. It's starting to be reported by others, where this did not exist until after the update. Reddit: Ventura 13.4 Display Sleep Issue https://www.reddit.com/r/MacOS/comments/13lyu2y/macos_ventura_134_display_sleep_issue/ I tried everything from turning off power saving settings, turned off screen saver, WoL, uninstalled color calibration software, reset monitor to factory settings, booted into safe mood, nothing had an effect. Should I submit a bug report?