Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
hooded-shrimp opened this issue Sep 25, 2024 · 4 comments

Comments

@hooded-shrimp
Copy link

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

@hooded-shrimp hooded-shrimp added B - bug Dang, that shouldn't have happened DS - macos labels Sep 25, 2024
@einarsi
Copy link

einarsi commented Sep 26, 2024

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

@madsmtm
Copy link
Member

madsmtm commented Sep 26, 2024

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.

@madsmtm madsmtm removed the B - bug Dang, that shouldn't have happened label Sep 26, 2024
@hooded-shrimp
Copy link
Author

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
Copy link
Member

madsmtm commented Sep 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants