========================== Version ======= KWin version: 5.12.5 Qt Version: 5.10.1 Qt compile version: 5.10.1 XCB compile version: 1.13 Operation Mode: X11 only Sometimes some shortcuts do not work although xinput is seeing the key presses. Only the shortcuts Mod+Shift+2 and Mod+Shift+3 do not work. They should move the focused window to the Desktop 2,3. Logging out and back in always fixes the problem.
please include output of dbus-monitor followed by pressing the relevant shortcut
(In reply to David Edmundson from comment #1) > please include output of > > dbus-monitor > followed by pressing the relevant shortcut When the shortcut doesn't work dbus_monitor doesn't generate any output for the action, otherwise is generates: signal time=1530630874.732729 sender=:1.58 -> destination=(null destination) serial=643 path=/component/kwin; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "kwin" string "Window to Desktop 2" int64 158181
updating to unconfirmed as the requested information is required. Moving to kglobalaccel as it seems to be kglobalaccel not sending the dbus method.
@Matthieu Can you run the following kquitapp5 kglobalaccel QT_LOGGING_RULES=kglobalaccel-runtime.debug=true kglobalaccel5 and note all output.
(In reply to David Edmundson from comment #4) > @Matthieu > > Can you run the following > > kquitapp5 kglobalaccel > QT_LOGGING_RULES=kglobalaccel-runtime.debug=true kglobalaccel5 > > and note all output. Doesn't work because the problem disappears if I restart kglobalaccel5. Is it possible to launch the application is debug mode and redirect the output to a file? Or maybe I should try to replace it by a wrapper script
Created attachment 113740 [details] Requested output
(In reply to David Edmundson from comment #4) > @Matthieu > > Can you run the following > > kquitapp5 kglobalaccel > QT_LOGGING_RULES=kglobalaccel-runtime.debug=true kglobalaccel5 > > and note all output. This part in the file kglobalaccel_x11.cpp is causing the failure: xcb_keycode_t *keyCodes = xcb_key_symbols_get_keycode(m_keySymbols, keySymX); if (!keyCodes) { qCDebug(KGLOBALACCELD) << "returning false"; return false; }
*** Bug 396189 has been marked as a duplicate of this bug. ***
Matthieu, would you be interested in producing a patch? Here's the documentation: - https://community.kde.org/Get_Involved/development - https://community.kde.org/Infrastructure/Phabricator
(In reply to Nate Graham from comment #9) > Matthieu, would you be interested in producing a patch? Here's the > documentation: > > - https://community.kde.org/Get_Involved/development > - https://community.kde.org/Infrastructure/Phabricator I am not exactly sure what is causing the bug. xcb_key_symbols_get_keycode returns null the first time the application is started. If I restart kdeglobalaccel it returns a valid ptr. It might be a XCB bug.
Or maybe a race condition when kde plasma starts? The problem shows only up after a reboot. "sleep 3; kquitapp5 kglobalaccel; kglobalaccel5" - this is my workaround
I wonder if this race condition is a result of our work to improve plasmashell's start times. :)
I have the same problem, but its about kwin effects shortcuts. I have to to restart kglobalaccel5 to make it recognize shortucs
Is this bug reproduceable *without* autologin into the kde-session? Otherwise it might be a duplicate of bug 394684 ...
(In reply to Holger from comment #14) > Is this bug reproduceable *without* autologin into the kde-session? > Otherwise it might be a duplicate of bug 394684 ... I start kde with startx from tty
Thank you for reporting this issue 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!
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!
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!