After installing the macOS 13.3 update I'm suddenly having an absolutely bizarre problem on my M1 Max MBP: Files whose filenames contain most Japanese kanji characters won't open in the associated program when double clicked unless I edit the filename.
For the problem files, when I double-click on it in the Finder, the Finder does the open animation and the associated app opens, but the file does not. The app just sits there like I hadn't clicked anything. Dragging the file to the app's icon does the same thing--it accepts the drop but nothing opens. If I manually open the file from within the application (via an "Open" dialogue), it opens fine.
Rebooting, moving the file or its parent folder, or renaming the parent folder did not make any difference, nor did modifying the default "open with" program for the file or its file type. What does fix it is editing the filename, at all, even if nothing at all is changed. Even just selecting the file, hitting return to put the filename into edit, then hitting return again without touching anything will restore normal behavior.
I've experimented with a bunch, and it's not just non-English filenames or filenames of a certain length; files with all English characters and some with just a couple of simple kanji all seem to open normally, but files with anything more than a couple of kanji (some of which are relatively short--less than 32 characters) all fail.
Figuring directory corruption, I rebooted in Recovery Mode and ran Disk Utility's First Aid on the Data volume and got a bunch of "warning: inode (...): dir-stats key xf does not exist, despite internal_flags (0x8412)" messages, which apparently repaired successfully and it now checks without throwing any errors or warnings... but the behavior remains.
I'm not excited about wiping and reformatting the whole thing since otherwise it seems okay, nor do I particularly want to have to touch hundreds of files, so I'm wondering if anybody has seen something similar or has any suggestions before I go nuclear.
Possibly related: After doing that update, all of the Touch ID fingerprints also disappeared. I was able to recreate new ones without issue, but have never had that happen before.
For the problem files, when I double-click on it in the Finder, the Finder does the open animation and the associated app opens, but the file does not. The app just sits there like I hadn't clicked anything. Dragging the file to the app's icon does the same thing--it accepts the drop but nothing opens. If I manually open the file from within the application (via an "Open" dialogue), it opens fine.
Rebooting, moving the file or its parent folder, or renaming the parent folder did not make any difference, nor did modifying the default "open with" program for the file or its file type. What does fix it is editing the filename, at all, even if nothing at all is changed. Even just selecting the file, hitting return to put the filename into edit, then hitting return again without touching anything will restore normal behavior.
I've experimented with a bunch, and it's not just non-English filenames or filenames of a certain length; files with all English characters and some with just a couple of simple kanji all seem to open normally, but files with anything more than a couple of kanji (some of which are relatively short--less than 32 characters) all fail.
Figuring directory corruption, I rebooted in Recovery Mode and ran Disk Utility's First Aid on the Data volume and got a bunch of "warning: inode (...): dir-stats key xf does not exist, despite internal_flags (0x8412)" messages, which apparently repaired successfully and it now checks without throwing any errors or warnings... but the behavior remains.
I'm not excited about wiping and reformatting the whole thing since otherwise it seems okay, nor do I particularly want to have to touch hundreds of files, so I'm wondering if anybody has seen something similar or has any suggestions before I go nuclear.
Possibly related: After doing that update, all of the Touch ID fingerprints also disappeared. I was able to recreate new ones without issue, but have never had that happen before.
