Bug 375858 - kglobalaccel incorrectly grabs keys
Summary: kglobalaccel incorrectly grabs keys
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kglobalaccel
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: VLO normal
Target Milestone: ---
Assignee: Martin Flöser
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-01 17:43 UTC by Henry Hu
Modified: 2022-11-29 05:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:
mgraesslin: corner_case+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henry Hu 2017-02-01 17:43:48 UTC
To use Win+Left/Right to adjust volume, I have this in .Xmodmap:

keysym Left = Left Left Left XF86AudioLowerVolume
keysym Right = Right Right Right XF86AudioRaiseVolume

However, with this setting, kglobalaccel grabs all the combinations of modifiers with the left key. This prevents using the left/right key for normal text input.
I understand that you want volume keys to work with any modifier, but kglobalaccel should only grab combinations of modifiers which includes the original modifier, i.e., you should only grab meta + left + (other modifiers).

A workaround is just specifying Meta+Left/Right in Shortcuts setting, but this does not work across desktop environments.
Comment 1 Martin Flöser 2017-02-01 20:34:07 UTC
I'm sorry, but that is quite a corner case and I doubt we can fix it. Kglobalaccel performs an XGrabKey (see https://tronche.com/gui/x/xlib/input/XGrabKey.html ) with the XF86AudioLowerVolume as key. In your case it seems that core X grabs it for too many cases. There is not much we can do here about that.

Also I must say that the X11 implementation of KGlobalAccel is rather unmaintained since I switched to Wayland. On the other hand I consider it as very likely that this issue is not present on Wayland at all.
Comment 2 Justin Zobel 2022-10-30 00:37:25 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-14 05:15:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-11-29 05:19:34 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!