| Summary: | Cannot open "Toggle Tiles Editor" | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Alexander Potashev <aspotashev> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | nate, treble-acid-copied |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Alexander Potashev
2025-05-04 18:12:05 UTC
Works for me on Wayland. Does it work there for you, or is it also broken on Wayland? 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME. Is also broken on Wayland. Tried with custom shortcut Alt+Shift+T. Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.17.4-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 16 ГиБ of RAM (15.4 ГиБ usable) Graphics Processor 1: Intel® HD Graphics 530 Graphics Processor 2: NVIDIA GeForce GTX 960M This discussion seems to be relevant: https://discuss.kde.org/t/tiles-editor-shortcut-stopped-working-after-6-2-2-upgrade/24915 - particularly the "solution" response (which is not quite a solution, rather a workaround). TL;DR: increasing the key repeat delay alleviates the problem. I started getting this after upgrading to 6.5.2 but it probably lurked earlier (I didn't need to edit tiles for some time). The problem fairly consistently reproduces with the keyboard delay of ~400ms and below; fairly consistently doesn't reproduce with the delay of ~500ms and above (could be machine specific? Doing this on Lenovo X1 nano gen2, FWIW). In the search of the reasons, I opened QDbusViewer and discovered that whenever the tiles editor fails to open up, I see globalShortcutRepeated signal being unexpectedly fired. Specifically, after connecting to all the three globalShortcut* signals, I get this sequence when the tiles editor opens: Received signal from :1.21, path /component/kwin, interface org.kde.kglobalaccel.Component, member globalShortcutPressed Arguments: "kwin", "Edit Tiles", 0 Received signal from :1.21, path /component/kwin, interface org.kde.kglobalaccel.Component, member globalShortcutReleased Arguments: "kwin", "Edit Tiles", 0 and this when the tiles editor doesn't end up showing: Received signal from :1.21, path /component/kwin, interface org.kde.kglobalaccel.Component, member globalShortcutPressed Arguments: "kwin", "Edit Tiles", 0 Received signal from :1.21, path /component/kwin, interface org.kde.kglobalaccel.Component, member globalShortcutRepeated Arguments: "kwin", "Edit Tiles", 0 Received signal from :1.21, path /component/kwin, interface org.kde.kglobalaccel.Component, member globalShortcutReleased Arguments: "kwin", "Edit Tiles", 0 So the tiles editor tries to open but just as it is about to show it gets cancelled by another simulated Meta+T event. This reproduces with non-standard shortcuts too, even not involving Meta modifier. Oh, and I forgot to mention that I'm on Wayland: Operating System: Fedora Linux 43 KDE Plasma Version: 6.5.2 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.0 Kernel Version: 6.17.6-300.fc43.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 32 GiB of RAM (31.0 GiB usable) Graphics Processor: Intel® Iris® Xe Graphics |