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

Sequoia issues #129

Closed
mjachi opened this issue Sep 19, 2024 · 7 comments
Closed

Sequoia issues #129

mjachi opened this issue Sep 19, 2024 · 7 comments

Comments

@mjachi
Copy link

mjachi commented Sep 19, 2024

Recent update to Sequoia has broken something.

Screenshot 2024-09-19 at 3 15 01 AM

This issue is popping up elsewhere:

I'm not sure if anything can actually be done here though?

@nowjiin
Copy link

nowjiin commented Sep 19, 2024

I'm experiencing the same thing.
Is this message pops up on only terminal ?
Mine appears only on IDE console

@mjachi
Copy link
Author

mjachi commented Sep 19, 2024

There should be no difference functionally. The above is just from my terminal trying to open a random PDF I have (rather than anything with VimTex)

In the meantime, I'm checking out Skim as an alternative. Not ideal but I don't think fixing this is within our control.

@nowjiin
Copy link

nowjiin commented Sep 19, 2024

Why This Message Appears

  1. Input Method Kit (IMK):
    • macOS uses the Input Method Kit (IMK) to handle keyboard input and text input methods, including internationalization and other text input scenarios.
    • When a Python application initializes certain GUI frameworks or interacts with the graphical user interface, macOS tries to determine which IMKClient and IMKInputSession subclasses to use for handling input.
  2. IMKClient_Legacy and IMKInputSession_Legacy:
    • The messages indicate that macOS is using legacy versions of IMKClient and IMKInputSession for handling input. This usually happens when the Python process does not fully support or register with the latest macOS input systems.
  3. Python GUI Frameworks:
    • GUI frameworks such as OpenCV, matplotlib, or Tkinter may trigger this log when they create windows or handle user input. This is because they might not be optimized for the latest macOS input system APIs.
  4. Logging Behavior:
    • macOS logs this information for diagnostic purposes, but it does not impact the functionality of your Python script. It’s essentially just informational output.

How to Suppress or Address the Issue

  1. Ignore the Logs:
    • Since these logs do not affect your program’s functionality, the simplest approach is to ignore them.
  2. Suppressing Warnings in Python:
    • If you find the logs annoying, you can suppress such output by setting environment variables or redirecting stderr. For example, you can run your Python script with:
    python -W ignore script.py
    • This will suppress warnings, but may not completely remove these specific logs.

Quick Answer from GPT.
I did not tried python script but, hope this will help thx.

@zegervdv
Copy link
Owner

@mjachi have you tried removing and reinstalling (i.e., recompiling)?

@mjachi
Copy link
Author

mjachi commented Sep 22, 2024

Ah reading the error message makes it clear that I should have tried doing so.

Just did brew reinstall zathura and fixed the error, but it is still warning about IMKClient and IMKInputSession versioning.

@mjachi mjachi closed this as completed Sep 22, 2024
@zegervdv
Copy link
Owner

I suspect that warning is coming from gtk. It will probably get resolved eventually

@torarnv
Copy link

torarnv commented Dec 1, 2024

The log comes from a non-categorized NSLog in +[IMKClient subclass] and +[IMKInputSession subclass], and whether IMKClient_Modern or IMKClient_Legacy is in use doesn't change whether the NSLog is called.

It doesn’t seem to output when running via Xcode, presumably because Xcode filters it out in its oslog shim.

It does however pop up when running an app via the terminal.

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

No branches or pull requests

4 participants