rust-windowing / winit

Window handling library in pure Rust
https://docs.rs/winit/
Apache License 2.0
4.8k stars 899 forks source link

Receiving `+[IMKClient subclass]: chose IMKClient_Legacy` logs after updating to MacOS Sequoia #3931

Open hooded-shrimp opened 2 weeks ago

hooded-shrimp commented 2 weeks ago

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

einarsi commented 2 weeks ago

I also noticed this just a few days ago, quite possibly right after I updated to Sequoia.

madsmtm commented 2 weeks ago

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.

hooded-shrimp commented 2 weeks ago

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.

madsmtm commented 2 weeks ago

Nothing to do then other than reporting the bug to Apple.

passCulture-JL commented 5 days ago

Hi, do you still have the bug after macOS 15.0.1 update ?

hooded-shrimp commented 5 days ago

do you still have the bug after macOS 15.0.1 update ?

I just updated and checked, the issue is still occurring.