Summary: | Keyboard shortcuts ignored after restarting kwin | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | avalonvales |
Component: | input | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | nate, o.ruze, thubble+kdebugs |
Priority: | NOR | ||
Version: | 5.23.5 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=448435 | ||
Latest Commit: | https://invent.kde.org/frameworks/kglobalaccel/commit/f31f4976cd8d17f6b890f7617b364cf2ee6ea2ce | Version Fixed In: | 5.91 |
Sentry Crash Report: |
Description
avalonvales
2022-01-13 14:50:39 UTC
Do in-app keyboard shortcuts still work? Like Ctrl+T in Firefox or Dolphin? I'm having an identical issue. Same symptoms as the original report: Alt+F4 to close a window and Alt+Tab to switch windows no longer work. I've verified that these keybindings are set in the Shortcuts KCM - I've even tried disabling Alt+F4, saving, and re-enabling it; no luck. This happens whether I do "kwin_x11 --replace" or kill and restart kwin_x11 manually. I did notice that a couple of applications still work with Alt+F4: Ungoogled Chromium and QMPlay2 are the only 2 I've found. Maybe these 2 applications have this functionality built in? I've tried a few others (Firefox, Thunderbird, even KDE apps like Dolphin and System Settings) and they all fail to close windows with Alt+F4. Alt+Tab never works no matter what application is active. Unfortunately I can't remember when it started, but it was quite recently (I only use kwin keyboard shortcuts occasionally). SOFTWARE/OS VERSIONS Gentoo, kernel 5.15.5, x86_64 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2, with KDE patches up to https://invent.kde.org/qt/qt/qtbase/-/commit/f4ac0b55c37f2b594ffbe639db43dac365825c7c On Wayland, I've been seeing *some* KWin shortcuts break a lot, most notably Meta+W for Overview and Meta+plus and Meta+minus for zoom in and zoom out. But Alt+Tab always works for me. Actually on a hunch, right after I posted my last comment, I tried killing kwin_x11 and then launching it with "dbus-launch kwin_x11", and that fixed it. So it looks like it just got out of sync with the kglobalaccel dbus service. (I might have updated kwin and/or frameworks at some point, I don't remember exactly when it started). This did break latte-dock's ability to launch the Present Windows effect, and restarting latte with dbus-launch didn't work either, only a full session restart got everything working again. That's probably outside the scope of this issue though. After I got everything working again, I did "kwin_x11 --replace" without dbus-launch, and everything's still working fine - so I'm not sure my issue was the same as the original report. Maybe worth a try for the original reporter though, if they're still having the issue? It looks like it was broken with 25e84f3f6ac54097d9c021705dc18b187352fa02 in kglobalaccel A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/39 Git commit f31f4976cd8d17f6b890f7617b364cf2ee6ea2ce by Vlad Zahorodnii. Committed on 04/02/2022 at 12:12. Pushed by vladz into branch 'master'. Fix action registration and unregistration order It appears like the order between QDBus::NoBlock and QDBus::Block calls is undefined. If a blocking call is made after a few non-block calls, those non-block calls can arrive at the destination after the blocking call. This is the root cause of some global shortcuts not working in kwin. When restarting compositing, the effects will release and register shortcuts but kglobalacceld receives setInactive() and doRegister() requests in the opposite expected order. kglobalaccel either should use QDBus::NoBlock for all requests or none. M +2 -2 src/kglobalaccel.cpp https://invent.kde.org/frameworks/kglobalaccel/commit/f31f4976cd8d17f6b890f7617b364cf2ee6ea2ce *** Bug 449428 has been marked as a duplicate of this bug. *** |