rust-windowing
Receiving `+[IMKClient subclass]: chose IMKClient_Legacy` logs after updating to MacOS Sequoia
Description
I am not sure if this is a MacOS Sequoia bug, or something winit needs to fix.
When I run any winit-based app on my Mac, I get messages like this:
2024-09-25 11:41:42.291 rust-testing[86791:3027734] +[IMKClient subclass]: chose IMKClient_Legacy
2024-09-25 11:41:42.291 rust-testing[86791:3027734] +[IMKInputSession subclass]: chose IMKInputSession_Legacy
When I searched the message, I found that some other non-winit projects are having this issue as well, which makes me think it could be a MacOS Sequoia bug.
macOS version
ProductName: macOS
ProductVersion: 15.0
BuildVersion: 24A335
Winit version
0.30.5
I also noticed this just a few days ago, quite possibly right after I updated to Sequoia.
Sounds like a macOS bug indeed, a quick internet search reveals a few other instances.
Would be nice if someone could create a bog-standard macOS application in Xcode, perhaps with a text field (since it sounds related to the issue), and see if the problem is present there too?
In any case, I'll leave this issue open for a while for visibility, though I doubt there is anything for us to do.
Would be nice if someone could create a bog-standard macOS application in Xcode, perhaps with a text field (since it sounds related to the issue), and see if the problem is present there too?
I tested it with the default Xcode MacOs app template. The issue occurs there as well.
Nothing to do then other than reporting the bug to Apple. See also https://developer.apple.com/forums/thread/115461.
do you still have the bug after macOS 15.0.1 update ?
I just updated and checked, the issue is still occurring.
Hi, do you still have the bug after macOS 15.0.1 update ?
Yes, it is still occurring
I also noticed the same problem when using ROOT analysis software. At first it didn't seem to cause any particular problems, but now I have serious problems viewing graphs and the like. As soon as I try to view something the software crashes
As a temporary workaround, you can pipe stderr through grep and filter the offending lines:
cargo run 2> >(grep -Ev 'IMKClient|IMKInputSession' >&2)
if it just logs it does it really matter? Like hiding the error doesn't make the error not appear at all...
I'm getting this when starting my Tauri 2 app on MacOS 15.1.1.
And yes, I think it matters because it adds noise to my logs.
If y'all are really annoyed by this, I guess you could try to investigate with a debugger and see if there's a way to prevent it from happening, it's not the first time we've carried patches for such logs (see below for an example), so if you do find a way I'd be glad to take a PR.
https://github.com/rust-windowing/winit/blob/62cb23f45b4591f0922d3cf5fc7b7c87e4eb5013/src/platform_impl/apple/appkit/view.rs#L215-L222
I have the same message, running my C++ program with SFML...
Upd. found something https://github.com/homebrew-zathura/homebrew-zathura/issues/129#issuecomment-2360382975
I tried this on macOS Sequoia 15.6.1 today, and couldn't reproduce it there, so I suspect it has been fixed by Apple in the meantime?
As such, I'm going to close this, feel free to reopen if you still encounter this in newer macOS versions.