Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I wouldn't call it serious in any case, since there are workarounds. But it's not particularly important if it's the OS or in an app that is preinstalled and integral to the OS, in my view.
I agree - Apple is responsible for this problem anyway, and can only fix this one with an OS update, as it is inseparably interconnected with the OS (in strong contradiction to software like Python, which was bundled with pre-Monterey Versions of macOS but exists completely independent from it - what an obviously inappropriate comparison).

The question remains how serious this bug really is. From what I've seen, it couldn't be much less important.
 
  • Like
Reactions: AlixSPQR and chrfr
I was going to submit a bug report, but found out I need to pay for a year of developer account so it is easy to submit bug reports. So I will report the bug here instead.

To Reproduce Bug:
Run MacOS Ventura on Mac Silicon (I think it affects Intel too)
Get an image file on your Mac (you can use "ScreenShot" to get one quick).
Go to the image using Finder and right click on it (it will probably be on your Desktop).
Select "Open With" ColorSync utility
Go to the top menu and select "File"->"Save As..."
Leave the default .jpg file format near the bottom and you can optionally change the name of the file.
Try to click on the "Save" button.

It will say "The operation couldn’t be completed. Not a directory"

Workaround:
Change the "Where" directory from the current "Desktop" to ANOTHER location (any location)" then change it back to "Desktop".
Then it should save correctly.
Does the same problem occur if you save your screenshots to a different folder or only on Desktop? Desktop is sometimes handled a little differently. I don’t like a bunch of screenshots clutterint up my desktop so I configured them to go do ~\Pictures\screenshots. If this problem doesn’t reproduce in other directories, that might be a simple workaround.
 
Last edited:
The process is difficult no matter your account status.

? The only difficult thing I've found with Feedback on MacOS is finding the Feedback App. You have to search for it (command spacebar) as it doesn't seem to show up in Applications.

Although checking it I see that one problem that I submitted (minutes long waits for folders to display contents) has disappeared.
 
? The only difficult thing I've found with Feedback on MacOS is finding the Feedback App. You have to search for it (command spacebar) as it doesn't seem to show up in Applications.

Although checking it I see that one problem that I submitted (minutes long waits for folders to display contents) has disappeared.
Search path for the app is: /System/Library/CoreServices/Applications
 
I was going to submit a bug report, but found out I need to pay for a year of developer account so it is easy to submit bug reports. So I will report the bug here instead.

To Reproduce Bug:
Run MacOS Ventura on Mac Silicon (I think it affects Intel too)
Get an image file on your Mac (you can use "ScreenShot" to get one quick).
Go to the image using Finder and right click on it (it will probably be on your Desktop).
Select "Open With" ColorSync utility
Go to the top menu and select "File"->"Save As..."
Leave the default .jpg file format near the bottom and you can optionally change the name of the file.
Try to click on the "Save" button.

It will say "The operation couldn’t be completed. Not a directory"

Workaround:
Change the "Where" directory from the current "Desktop" to ANOTHER location (any location)" then change it back to "Desktop".
Then it should save correctly.

Apple will never see this. You can file one easily at https://www.apple.com/feedback
 
  • Like
Reactions: Tagbert
I 100% hate hyperbole and click bait. It is NOT a serious bug with MacOS, and it is, at best, an edge case that is a slight inconvenience.

I'll just throw this out there, and also caveat it by saying that I'm not even on Ventura on my M1 MBP (still on Monterey). That said...

This could possibly be a serious bug in MacOS. What if the issue is related to the desktop, where the user logged in may not be given the privileges to write to its own ~/Desktop directory, or if for some reason, the process trying to write to ~/Desktop requires some sort of elevated privileges to do so. Yes, ownership and permissions can be changed on the directory, but if there is an issue with the Desktop directory itself, or if the process writing the file to ~/Desktop does not have the permission to write the file there (despite it being the same user that owns ~/Desktop), then there could be a major bug there that needs to be addressed.

In short, one may have to look deeper at the issue instead of what you see at the UI to determine if it is click bait, hyperbole, an actual bug, or otherwise.

BL.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.