8000 [BUG] Rofi does not detect [133] key press when fcitx5 is running · Issue #2123 · davatorium/rofi · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BUG] Rofi does not detect [133] key press when fcitx5 is running #2123

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.

Sign up for GitHub

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

Jump to bottom
Open
2 tasks done
imsuck opened this issue Apr 15, 2025 · 8 comments
Open
2 tasks done

[BUG] Rofi does not detect [133] key press when fcitx5 is running #2123

imsuck opened this issue Apr 15, 2025 · 8 comments
Labels
bug

Comments

@imsuck
Copy link
imsuck commented Apr 15, 2025 •
edited
Loading

Rofi version (rofi -v)

1.7.8 and 1.7.8-31-gf0ccf4c1 (makepkg)

Configuration

https://gist.github.com/imsuck/36ad7b25cee9244c42c82c53734a4e33#file-config-rasi

Theme

https://gist.github.com/imsuck/36ad7b25cee9244c42c82c53734a4e33#file-theme-rasi

Timing report

No response

Launch command

rofi -show drun -kb-cancel '[133]'

Step to reproduce

  1. Have fcitx5 running in the background.
  2. Run rofi -show drun -kb-cancel '[133]'
  3. Press the Super key, rofi does not close.

Expected behavior

Rofi closes after pressing Super.

Actual behavior

Rofi does not close.

Additional information

Running G_MESSAGES_DEBUG=IMDKit rofi -show keys -kb-cancel "[133]" with fcitx5 gives:

Mode keys is not enabled. I have enabled it for now.
Please consider adding keys to the list of enabled modes: modes: [drun,keys].
(process:5049): IMDKit-DEBUG: 08:01:41.255: release handler 36
(process:5049): IMDKit-DEBUG: 08:01:42.004: press key 133 to xim
(process:5049): IMDKit-DEBUG: 08:01:42.008: press handler 133
(process:5049): IMDKit-DEBUG: 08:01:42.090: release key 133 to xim
(process:5049): IMDKit-DEBUG: 08:01:42.097: release handler 133
(process:5049): IMDKit-DEBUG: 08:01:42.467: press key 36 to xim
(process:5049): IMDKit-DEBUG: 08:01:42.469: press handler 36

And without fcitx5:

Mode keys is not enabled. I have enabled it for now.
Please consider adding keys to the list of enabled modes: modes: [drun,keys].
(process:13059): IMDKit-DEBUG: 08:06:25.594: release handler 36
(process:13059): IMDKit-DEBUG: 08:06:25.977: press handler 133

Using wayland display server protocol

  • No, I don't use the wayland display server protocol

I've checked if the issue exists in the latest stable release

  • Yes, I have checked the problem exists in the latest stable version
@imsuck imsuck added the bug label Apr 15, 2025
@DaveDavenport
Copy link
Collaborator

Is super key bound do something in fcitx5?

@imsuck
Copy link
Author
imsuck commented Apr 15, 2025 •
edited
Loading

I have tried removing every keybind in fcitx that contains super but nothing changes. Rofi still receive press handler 133 though why would it not work?

@julianullrich99
Copy link

I have the same issue, appeared in recent system-update that introduced fcitx5

@DaveDavenport
Copy link
Collaborator

I did not make the patch, I asked somebody who helped with the patch to look at it, but have not heard back.
You can (build time) disable imdkit support in rofi.

@amosbird
Copy link
Contributor

Handling modifiers with rofi and fcitx5 has been a nightmare. After spending quite some time debugging, I came up with a workaround that works for most major scenarios: #2015.

I don't think there's much more we can do on the rofi side. The key events seem to get lost somewhere inside https://github.com/fcitx/xcb-imdkit.

@DaveDavenport
Copy link
Collaborator

@amosbird maybe a run-time flag to disable imdkit can be helpfull?

@amosbird
Copy link
Contributor

maybe a run-time flag to disable imdkit can be helpfull?

That's a good idea. Actually I rarely use input method inside rofi TBH. I'll submit a PR for it.

@DaveDavenport
Copy link
Collaborator

Thanks!

@amosbird amosbird mentioned this issue Apr 26, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@DaveDavenport @amosbird @julianullrich99 @imsuck
0