Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13.4 (Final) - Bug fixes, changes, and more
- Thread starter WilliApple
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Most likely? Do you have a source?
I think it is extremely unlikely that macOS 14 will not support intel macs, because Apple still sells a MacPro for thousands of dollars that has an intel chip inside of it. Also, dropping software support for products that were launched within the last 3 years is very un-Apple. Only the Apple Watch Series 3 comes to mind.
I've always had some problems sending sound from M1 mac mini to Homepod mini, esp. bad with 13.3/16.4 combined. Indeed, with 13.3 I struggled for days to get it working at all.
So far, 13.4/16.5 seems to be working as expected. Certainly I hope so as it is such a pain going round the loop of rebooting, checking, switching audio output, etc. Just to hear the next phrase in DuoLingo!
Fingers well and truly crossed.
So far, 13.4/16.5 seems to be working as expected. Certainly I hope so as it is such a pain going round the loop of rebooting, checking, switching audio output, etc. Just to hear the next phrase in DuoLingo!
Fingers well and truly crossed.
strange issue with finder/ quicklook and even QuickTime. Files just don't show thumbnails or work. Not sure why. Sony A7SIII files. Some of them worked and then there are like 70 that didn't from a shoot tonight. I posted in Final Cut group and others are having similar issues. This is a huge problem for video editors. Attached a photo for a big more detailed explanation. i Can upload test files to a Dropbox and have others test on their version of 13.4 or if anyone is running 13.5 ?
Attachments
Just seeing this post now, but I can second that there were plenty of WindowServer crashes earlier on, and from what I could tell it was just a matter of some apps being updated AND Apple fixing some stuff..
macOS 13.4 has been A O K for me
I took the plunge and upgraded to 13.4, and so far everything has been good (minus one major issue with Apple ID/iCloud in system settings not working), but we will see if WindowServer comes back.
Yes, for sure.
I'd estimate at least 95% of the bugs that are fixed are handled that way...
Last edited:
When I was involved in software development and maintenance, we'd sometimes intentionally fix an issue but not realise that we'd fixed other issues at the same time. At least, not immediately. And especially not if they were difficult to test and maybe only rarely occurred.
If someone looked at the list of fixed issues, they'd not see the additional issues listed.
updated to Mac OS Vetura 13.4 (22F66). I have a problem with bluetooth and the Logitech MX master 3S mouse again, after coming out of sleep, the pointer slows down and moves a little jerkily (Only a reboot via the sudo pkill bluetoothd command helps, It used to be like this, but in the previous version everything was fine. I have a Mac studio computer
Hi everyone! On m1 macbook (Ventura 13.4 (22F66)) an SD card disappears after reboot until I replug it phisicaly into the macbook, what can be done?
I use Logitech Pebble M350 on both M1 mac mini and M1 MBP - no issues with Bluetooth since update (or before, for that matter!)
Well.... I have some bad news...
Code:
Date/Time: 2023-05-23 23:03:47.605 -0700
End time: 2023-05-23 23:06:54.584 -0700
OS Version: macOS 13.4 (Build 22F66)
Architecture: x86_64h
Report Version: 40
Incident Identifier: ACC2A947-D957-4AAB-94C7-D9E4CF635FB8
Data Source: Microstackshots
Shared Cache: 867BF49E-1375-3009-9693-A1621961928A slid base address 0x7ff80b406000, slide 0xb406000
Command: WindowServer
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Codesigning ID: com.apple.WindowServer
Resource Coalition ID: 143
Architecture: x86_64
Parent: launchd [1]
PID: 159
Event: wakeups
Action taken: none
Wakeups: 45001 wakeups over the last 187 seconds (241 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds
Wakeups limit: 45000
Limit duration: 300s
Wakeups caused: 45001
Wakeups duration: 187s
Duration: 186.98s
Duration Sampled: 183.22s
Steps: 68
Hardware model: MacPro7,1
Active cpus: 24
HW page size: 4096
VM page size: 4096
Fan speed: 502 rpm
Advisory levels: Battery -> 3, User -> 2, ThermalPressure -> 0, Combined -> 2
Free disk space: 1447.97 GB/1863.39 GB, low space threshold 3072 MB
Vnodes Available: 23.95% (63018/263168)
Preferred User Language: en-US
Country Code: US
Keyboards: U.S.
OS Cryptex File Extents: 1
Heaviest stack for the target process:
6 start + 1903 (dyld + 25631) [0x7ff80b4a441f]
6 ??? (WindowServer + 13452) [0x10fbcf48c]
6 ??? (SkyLight + 3254343) [0x7ff810787847]
6 ??? (SkyLight + 3254766) [0x7ff8107879ee]
6 ??? (SkyLight + 3252127) [0x7ff810786f9f]
5 ??? (SkyLight + 3253019) [0x7ff81078731b]
5 ??? (SkyLight + 2994210) [0x7ff810748022]
5 ??? (SkyLight + 2993968) [0x7ff810747f30]
4 ??? (SkyLight + 2465345) [0x7ff8106c6e41]
3 ??? (SkyLight + 2514230) [0x7ff8106d2d36]
1 ??? (SkyLight + 2553259) [0x7ff8106dc5ab]
1 ??? (SkyLight + 2647104) [0x7ff8106f3440]
1 _CFRetain + 237 (CoreFoundation + 1134843) [0x7ff80b9720fb]
Powerstats for: WindowServer [159]
UUID: EACA179E-9CDF-3CA4-8B0C-EA3923177D6A
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Codesigning ID: com.apple.WindowServer
Resource Coalition ID: 143
Architecture: x86_64
Parent: launchd [1]
UID: 88
Footprint: 515.08 MB
Start time: 2023-05-23 23:03:50.938 -0700
End time: 2023-05-23 23:06:24.711 -0700
Num samples: 6 (9%)
Primary state: 6 samples Non-Frontmost App, Non-Suppressed, User mode, Effective Thread QoS Unspecified, Requested Thread QoS Unspecified, Override Thread QoS Unspecified
User Activity: 0 samples Idle, 6 samples Active
Power Source: 0 samples on Battery, 6 samples on AC
6 start + 1903 (dyld + 25631) [0x7ff80b4a441f]
6 ??? (WindowServer + 13452) [0x10fbcf48c]
6 ??? (SkyLight + 3254343) [0x7ff810787847]
6 ??? (SkyLight + 3254766) [0x7ff8107879ee]
6 ??? (SkyLight + 3252127) [0x7ff810786f9f]
5 ??? (SkyLight + 3253019) [0x7ff81078731b]
5 ??? (SkyLight + 2994210) [0x7ff810748022]
5 ??? (SkyLight + 2993968) [0x7ff810747f30]
4 ??? (SkyLight + 2465345) [0x7ff8106c6e41]
3 ??? (SkyLight + 2514230) [0x7ff8106d2d36]
1 ??? (SkyLight + 2553259) [0x7ff8106dc5ab]
1 ??? (SkyLight + 2647104) [0x7ff8106f3440]
1 _CFRetain + 237 (CoreFoundation + 1134843) [0x7ff80b9720fb]
1 ??? (SkyLight + 2553020) [0x7ff8106dc4bc]
1 ??? (SkyLight + 2636398) [0x7ff8106f0a6e]
1 ??? (SkyLight + 1994120) [0x7ff810653d88]
1 ??? (SkyLight + 2208522) [0x7ff81068830a]
1 ??? (QuartzCore + 1707339) [0x7ff81331ad4b]
1 ??? (QuartzCore + 588931) [0x7ff813209c83]
1 ??? (QuartzCore + 1663924) [0x7ff8133103b4]
1 ??? (QuartzCore + 1663924) [0x7ff8133103b4]
1 ??? (QuartzCore + 1663924) [0x7ff8133103b4]
1 ??? (QuartzCore + 1663924) [0x7ff8133103b4]
1 ??? (QuartzCore + 1673588) [0x7ff813312974]
1 ??? (SkyLight + 2552761) [0x7ff8106dc3b9]
1 ??? (SkyLight + 2003054) [0x7ff81065606e]
1 ??? (SkyLight + 1998431) [0x7ff810654e5f]
1 ??? (QuartzCore + 2857786) [0x7ff813433b3a]
1 ??? (SkyLight + 2538881) [0x7ff8106d8d81]
1 ??? (SkyLight + 2504667) [0x7ff8106d07db]
1 ??? (libsystem_trace.dylib + 48136) [0x7ff80b587c08]
1 ??? (libsystem_trace.dylib + 89536) [0x7ff80b591dc0]
1 ??? (libsystem_trace.dylib + 26508) [0x7ff80b58278c]
1 ??? (SkyLight + 2465941) [0x7ff8106c7095]
1 ??? (SkyLight + 2469576) [0x7ff8106c7ec8]
1 ??? (SkyLight + 2495796) [0x7ff8106ce534]
1 ??? (SkyLight + 477879) [0x7ff8104e1ab7]
1 CFRetain + 19 (CoreFoundation + 18118) [0x7ff80b8616c6]
1 ??? (SkyLight + 3253001) [0x7ff810787309]
1 ??? (SkyLight + 2351306) [0x7ff8106ab0ca]
Binary Images:
0x10fbcc000 - 0x10fbdbfff WindowServer (763.4) <EACA179E-9CDF-3CB4-8A0C-EA3954178D3A> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServerDo you have a Dock you connect your Mac Pro to? I was getting similar crash reports consistently not too long ago, and it turned out to be a bad Dock. Only found out thru testing plugging in various drives and peripherals to check. Although with a MacPro you might not need a Dock.
I just noticed that now, for me, on macOS 13.4 I am able to select a folder from the Photos app to select my Desktop Wallpaper, and I'm able to select the option to Auto-Rotate and by time frame (I'm going with every 5 minutes). But as soon as I select the 'Random' check box, it stays as the Default Dark Mode Wallpaper. If I uncheck it, boom- right back to my wallpaper in the folder. So, no Random Wallpapers for me.
I am having a massive problem with the update to 13.4 which went out last week and wonder if anyone knows anything about this problem.
When I updated my 2019 MBP to 13.4, all my data in my DOCUMENTS folder disappeared!. Every single file! The files may well still be on the ssd but none show!
I have spent few hours with apple over the phone about this and have gone to the genius bar and their only answer is to wipe the drive and restore from a backup. However, my letest backup is dated may 2nd so I would have to lose all my most recent files AND all my open tabs on my browsers ]
My downloads folder is intact, as are my pictures and movie folders but Documents has completely disappeared .
Does anyone know anything about this please? Is there any report or thread on it please?
When I updated my 2019 MBP to 13.4, all my data in my DOCUMENTS folder disappeared!. Every single file! The files may well still be on the ssd but none show!
I have spent few hours with apple over the phone about this and have gone to the genius bar and their only answer is to wipe the drive and restore from a backup. However, my letest backup is dated may 2nd so I would have to lose all my most recent files AND all my open tabs on my browsers ]
My downloads folder is intact, as are my pictures and movie folders but Documents has completely disappeared .
Does anyone know anything about this please? Is there any report or thread on it please?
sorry to hear that; odd one. but it's a reminder to back up often. and i always back up my macs before an OS update, seems a good idea.
i'd try apple again, nothing to lose. there must be some reason for this. do you have documents & desktop in the cloud??
Then I'd suggest unplugging as much as possible leaving maybe just power and Ethernet (and Keyboard & Mouse if needed) and then over a little bit of time try plugging in each different peripheral separately and see if something is causing it. OR, it could actually be a physical USB port or ThunderBolt port that's broken. That's a tough one.
What FOR SURE triggered it last night is using my second monitor (had been just using 1 since 13.4) but yesterday I decided to test/see if this was truly fixed as some other users reported in this thread.
Really stupid that something so simple would cause this, and it doesn't seem apple cares, as it's been happening since inception...
I will try your suggestion as well, thanks!