Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS Ventura (13.x) - Bugs

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.
24-hour clock not working for anyone else even though it's on in settings? I get the 24-hour clock on my Lock Screen, but after logging in, I'm stuck on the 12-hour clock
 
  • Angry
Reactions: ScrumpyDaniel
Stage Manager is a little broken. After dragging a "minimised" app on top of another, its old position on the screen is forgotten.

 
Still a couple too tree restarts until System Pref- I mean System Settings remembers things like what apps have Full Disk Access along with all of the other permissions?

Also, whomever is responsible for not including the option to hide launched apps at login should reevaluate their role.
 
Did you check your installation of `command line` tools. I get an error when I run git:

```
$-> git

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
```
 
On macOS 12, my old BenQ XL2410T works at 120hz hooked up via DVI to my CalDigit TS4.

On macOS 13, the monitor is detected but there is no 120hz option. Checking the monitor status, it is running only at 60hz.
 
George Dawes said:
I recall the days when I really looked forward to Mac OS Updates

Nowadays I dread them and from reading about all the glaring issues in Ventura I think I've got a point

The whole WFH debacle has a LOT to answer for imo
Click to expand...
Nail on the head.
I’ve resorted to sticking with the OS that came with my macs (currently both on Monterey after recent purchases). No desire to update.
 
  • Like
Reactions: Makisupa Policeman and George Dawes
What some folks fail to understand about the different beta builds is that, besides having the extra logging and stuff enabled (which can sometimes cause its own issues), sometimes things are 'broken' on purpose for testing. Because it's a beta. Maybe one specific model could be impacted by some showstopper type of issue while a large series of there models have no impact at all. It's during the RC (and maybe RC2) that these things are set to be 'shored up' and on par with each other.

If someone wants to use a prior beta or even a prior RC build, have at it! You do what you want with your stuff. Just know that sometimes memory leaks don't happen until an app is running for maybe 2-3 days and then you start seeing kernel panics 5-8 times a day. After a couple days of RC1. Or maybe not! Betas. whadayagonnado
 
  • Like
Reactions: gwhizkids
It's probably been mentioned earlier in the thread, but if you have two monitors Stage Manager is a bit wonky at times.

Here's a specific scenario - lets say the left monitor is my main one, and the right is my secondary. I'm working on the right monitor and I have two 'stages' showing on the left hand side of it. If I want to drag a window from one stage into the one I'm working on, it flies over to the left monitor and takes a lot of dragging just to get it in place.

Anyone else?
 
Anyone having issues with Maps not being able to calculate driving directions? It accepts the designation and shows my starting point as current location, but it just spins indefinitely when trying to calculate a route.

Had this same issue for the past few months on Monterey, was hoping Ventura would fix.

This is on a Mac Studio, so it's not a horsepower issue.
 
Have two MBPs -- one work, one personal -- using Universal Control.

This has been working fine on Monterey on both MBPs. Updated one (personal MBP) to Ventura. Now the Universal control "stutters".

Issue: when mouse from "master" MBP (running Monterey) is on the other MBP (running Ventura), the mouse and keyboard isn't smooth, but they "stutter", i.e. not smooth. Using a separate mouse connected (via BT) to the Ventura laptop is fine; scrolls smoothly. When the mouse is over on the "master" MBP, all's silky smooth.

Have only had this behaviour since updating one of them to Ventura.
 
I love the new Settings (Preferences) and how it mimics iOS, but. Is it a little laggy for anyone else? Or am I just comparing it to how instantly the menus load on iOS?
 
  • Like
Reactions: H_D
I'm finding that from time to time the Settings app in Ventura stops working for certain things. For example I couldn't toggle Stage Manager on or off through the Settings app (control center worked). Another example is the Screen Time screen stops updating after awhile.

Both of these are fixed by logging out and back in, but there is something wrong with the Settings app.

Also the sdiff terminal command is missing in Ventura. The man page is there, but the command is not.
 
Is it just me or is the function key toggle (from volume etc to F1—F12) gone? Cannot find it in the keyboard settings
 
H_D said:
Is it just me or is the function key toggle (from volume etc to F1—F12) gone? Cannot find it in the keyboard settings
Click to expand...
It's in the keyboard settings under Touch Bar Settings...

1666853986697.png
 
  • Like
Reactions: H_D and GlenK
Glenny2lappies said:
Have two MBPs -- one work, one personal -- using Universal Control.

This has been working fine on Monterey on both MBPs. Updated one (personal MBP) to Ventura. Now the Universal control "stutters".

Issue: when mouse from "master" MBP (running Monterey) is on the other MBP (running Ventura), the mouse and keyboard isn't smooth, but they "stutter", i.e. not smooth. Using a separate mouse connected (via BT) to the Ventura laptop is fine; scrolls smoothly. When the mouse is over on the "master" MBP, all's silky smooth.

Have only had this behaviour since updating one of them to Ventura.
Click to expand...
Weird; changed the colour scheme from Dark to Auto and suddenly the mouse is responsive!
 
I have quite a lot of WindowServer crashes since one of the Ventura betas and they still occur with the final version.

This is from the logs

2022-10-27 11:00:10.198174+0200 0xafbb2 Fault 0x2c73c1 35423 14 WindowServer: (QuartzCore) [com.apple.coreanimation:WindowServer] kIOMFBMaxCompressedSizeInBytes missing!
2022-10-27 11:00:10.206861+0200 0xafbb2 Fault 0x2c73c2 35423 14 WindowServer: (QuartzCore) [com.apple.coreanimation:WindowServer] kIOMFBMaxCompressedSizeInBytes missing!
2022-10-27 11:00:10.227534+0200 0xafbb2 Fault 0x2c73c3 35423 14 WindowServer: (QuartzCore) [com.apple.coreanimation:WindowServer] kIOMFBMaxCompressedSizeInBytes missing!

Anyone else having this? Is there something I can do?
 
  • Like
Reactions: adrianlondon and gank41
Glenny2lappies said:
It's in the keyboard settings under Touch Bar Settings...

View attachment 2102995
Click to expand...
Man, that was driving me crazy. It had to work because on the Studio, where they keys were set to work as function keys, they did, on the MBP they were brightness/sound-controls and I could not find the toggle. Makes VERY MUCH SENSE in the Touch Bar section, Apple. None of my devices has a Touch Bar anymore (though I am of the 1& of people who actually liked the bar ;-))

Many thanks for the help, very much appreciated! 🙏
 
  • Like
Reactions: Glenny2lappies
By the way, the weird thing upon installing the official version & replacing the RC/Beta was that with the beta the machine worked perfectly fine, and with the official release I had multiple brutal crashes (Setapp, Mail, Adobe Desk, Safari, you name it...). A couple of reboots later it seems to have caught up, but that was ... unsettling. I cannot stress that despite my love for all things Apple I feel more and more like OSX is coming close to a Vista-Moment.
 
  • Like
Reactions: George Dawes and gank41
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back