Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Oddly enough! Just in the last week or so I installed Asahi Linux on my M1 MBP and have had no issues with macOS since. I think there’s a difference between restarting and shutting down and back on again? With me, I’m shutting down after using Linux and then waiting 15-20 seconds and then booting back up into macOS.

Yeah I have no idea what it is, but definitely using another OS helped sort it out (how in the hell is that possible?!)

I am not responding to your problems. I am rather sharing my case to this group as a whole.

Sorry I didn't mean to come on so aggressively, just saying, you and I are having the same issues, but I am NOT using Firefox, so there must be something else going on there. Also, my machine is a Mac Pro, and yours is running Apple Silicon, so this issue is not specific to Intel, but it looks to be a direct issue within the OS itself.

I really hope they sort this out on macOS 14, that would be a total bummer for this to continue to happen!
 
  • Like
Reactions: gank41
Updated yesterday to 13.4 22FF66 and now my PGUP and PGDN do not work in any apps. Also, PGUP & PGDN seem to break/kill other keystrokes. i.e. I can use the up/down/left/right arrows in every app until I hit PGUP or PGDN and thereafter the arrow keys are dead. Until I CMD+TAB twice. (The first time there is no response. The second time it switches apps and the arrow keys are reenabled.) Until I hit PGUP or PGDN again by habit - something I do in Excel hundreds of times per day. I checked the keys using Karabiner Event Viewer and it indicates all of the keys are working properly (even after using PGUP/PGDN). Tried it using a USB-connected keyboard and a Mac Bluetooth keyboard. Same results. Baffling... No, I'm not interested in doing a NVRAM reset at the current time.

FF Tech iMacPro about this mac settings.png
 
Got sick of waiting so I just upgraded to 13.4. Big risk but we'll see how stability goes over the next couple of weeks in common workflows. If everything is stable I will finally turn on Advanced Data Protection.
 
  • Like
Reactions: osplo
One of the most obvious (and irritating) changes made is the new trackpad scrolling algorithm. It's bloody awful, it feels 'heavier' if that makes sense, like there's more friction; a muscle memory flick now only scrolls a few items in finder when it used to be 10s of items. It honestly feels like scrolling is broken.

One test I'm trying is repeat scrolling flicks of roughly the same speed in succession. In macOS 12 each scroll would add the same 'amount' of scroll as the last but in 13 each flick will randomly change the speed of the scroll. Again, like it's broken.

This is almost enough to revert to 12 because anything that screws with a fundamental muscle memory behavior is unacceptable but I suspect this change is permanent so I'll have to get used to it.

EDIT: I should add this only appears to be happening in Finder so far, Firefox seems to be ok.
 
Last edited:
One of the most obvious (and irritating) changes made is the new trackpad scrolling algorithm. It's bloody awful, it feels 'heavier' if that makes sense, like there's more friction; a muscle memory flick now only scrolls a few items in finder when it used to be 10s of items.

Strange. Tested this in my MBA M1, trackpad scrolling in Finder seems as fast as Monterey. Maybe there are some trackpad settings you may revise?
 
My Universal Control stopped working with 13.4 connecting to 12.6.3.
Known workaround?
Universal Control is also very flaky for me from macOS 13.4.1 to ipadOS 16.5.1. It will work for a few minutes, then not work for some time, the randomly connect again, and so on. Nothing I have tried makes it stay connected. I'll report back if I ever come up with a fix.
 
Where are you getting that from? -- this is a 2019 Mac Pro 7,1 (same as in my sig).

From the log: System model name: MacPro7,1 (Mac-27AD2F918AE68F61)

View attachment 2209008

unfortunately, Apple Diagnostic reveals no errors, and when I run Disk Utility Repair from within recovery, no errors on any of my drives.

I have been thinking of trying Apple Configurator, but I will need to read up more on that, as it will require me to use another mac to revive and restore.

Hi, I have a hackintosh, ventura 13.3.1, smbios 7.1, radeon 6800 xt, with exactly the same problem. I have an asus tuf radeon 6800 xt.

I've checked my opencore installation several times and I can't seem to fix this KP. It was also happening to me in smbios 20.2 but with smbios 7.1 by deactivating my igpu it seems less recurent for me. I wondered if this was due to the gpu itself. Then I started to wonder if it wasn't coming from macOS itself and I finally came across your post.

You've simply done benchmarks and that has solved your problems; it's really strange though. Is everything back to normal with you? Can you tell me a little more. Thank you
 
Last edited:
I finished upgrading all my Macs to Ventura. I was wary for all the threads in this forum but in the end it has been rock solid for me.
 
Installed 13.4.1 (c) Rapid Security Response on my MacBook 2017 Intel . . .
Trying to Spaces (i.e. virtual desktops) caused the OS to destabilize, eventually making it unstable to Mouse and Keyboard.
The Rollback feature did not resolve this problem.
Now my MacBook is a shining piece of mess. I have to remote login to it to shutdown.
OMG what is Apple doing to MacOS Ventura ?
It is a massive mess.
 
Installed 13.4.1 (c) Rapid Security Response on my MacBook 2017 Intel . . .
Trying to Spaces (i.e. virtual desktops) caused the OS to destabilize, eventually making it unstable to Mouse and Keyboard.
The Rollback feature did not resolve this problem.
Now my MacBook is a shining piece of mess. I have to remote login to it to shutdown.
OMG what is Apple doing to MacOS Ventura ?
It is a massive mess.

Disabled Stage Manager but no improvement.
Any Mission Control feature destabilizes the operating system.

I should have known better than to give Apple the benefit of the doubt.
I encountered the same problem when I installed an RSR for 13.3.1 but the rollback did resolve all the problems introduced with the RSR, so I thought worse case I could fallback to that.

Not this time, whatever the RSR changed, the rollback was flawed faulty and a joke.
Reset NVRAM did not fix it either.

I am constantly remote logging into my MacBook and shutting it down.
 
Disabled Stage Manager but no improvement.
Any Mission Control feature destabilizes the operating system.

I should have known better than to give Apple the benefit of the doubt.
I encountered the same problem when I installed an RSR for 13.3.1 but the rollback did resolve all the problems introduced with the RSR, so I thought worse case I could fallback to that.

Not this time, whatever the RSR changed, the rollback was flawed faulty and a joke.
Reset NVRAM did not fix it either.

I am constantly remote logging into my MacBook and shutting it down.

A temporary fix is to remote login and execute command "killall Dock".
This resolves the problem, until the next reboot, or some random time in the future which I have not reached yet.
 
A temporary fix is to remote login and execute command "killall Dock".
This resolves the problem, until the next reboot, or some random time in the future which I have not reached yet.

Just incase someone else also is encountering the same issue, renaming the dock preference file to something else, then rebooting, will make the OS create a fresh new dock preference file, and the issue no longer happens, even after reboots.

But why a Rapid Security Response to fix a Safari vulnerability would corrupt a dock preference file, is another MacOS Ventura mystery.
 
  • Like
Reactions: osplo
Just in case someone else also is encountering the same issue, renaming the dock preference file to something else, then rebooting, will make the OS create a fresh new dock preference file, and the issue no longer happens, even after reboots.

Thanks for sharing.
 
Just incase someone else also is encountering the same issue, renaming the dock preference file to something else, then rebooting, will make the OS create a fresh new dock preference file, and the issue no longer happens, even after reboots.

But why a Rapid Security Response to fix a Safari vulnerability would corrupt a dock preference file, is another MacOS Ventura mystery.

Just FYI . . .
I was able to recreate the Mission Control & Spaces (virtual desktops) problem in 13.5 and resolving it using the renaming of the Dock preferences file, in my 2017 MacBook.

In this case, the cause was putting too many app icons in the Dock.
To be specific, after I added all the additional apps back into the Dock (the way I like), I was using TinkerTool to add spaces (putting a space between app icons) to logically group the app icons into visually convenient segments. Each time a space is added the Dock is restarted to reflect the changes, I did this many times.
Then the moment one space insert and Dock restart did not reflect the change, I checked if Mission Control is still okay, and that is when I noticed that the Spaces function was not working properly, and from that point the OS user interface continued to become unstable.
I tried a couple of remote logins and reboots, but the problem persisted, so I renamed the Dock preferences file and the problem was fixed.

I had to go back and redo my Dock app icon additions again, but I did not add any spaces between app icons this time. I can deal with a less visual convenience over an unstable user interface.

I am thinking about finding and using a preferences file editor or similar tool to see what might be the culprit, when I have time and the motivation.

I hope this helps.
 
  • Like
Reactions: TheGeneralist
I took a chance, updated my 2018 MacMini to 13.5 and can say that external display to my 49" ultra-wide Dell U4919DW monitor works fine (USB-C to DP cable), and also no issues encountered with the two old 20" wide flat-panel displays on either side of the ultra-wide.

Keeping my fingers crossed it stays working as it is supposed to.
 
  • Like
Reactions: gank41
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.