[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Nate Graham changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #11 from Nate Graham --- As announced in https://pointieststick.com/2023/07/26/what-we-plan-to-remove-in-plasma-6/ and https://community.kde.org/Plasma/Plasma_6#Removals, I'm afraid KHotKeys has reached end-of-life in Plasma 6. Accordingly, all bug reports and feature requests for it must be closed now. Most of what KHotKeys could do can already be done with the newer KGlobalAccel system in Plasma 6. A few features such as mouse gestures and triggering conditions based on changes to window states are not yet implemented in the new system. These will be added in the future if and when resources materialize for them, and/or when a kind soul submits patches to implement them! :) Meanwhile, the 3rd-party "Mouse Actions" app (https://github.com/jersou/mouse-actions) may be usable for implementing your own mouse gestures again. Thanks for your understanding, everyone. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 ivan.tsyauk2...@yandex.ru changed: What|Removed |Added CC||ivan.tsyauk2...@yandex.ru --- Comment #10 from ivan.tsyauk2...@yandex.ru --- I have exactly the same bug. Operating System: Manjaro Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.1.53-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550 AORUS PRO AC -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #9 from Mariusz Libera --- Still an issue in plasma 5.23.4. Detecting window properties works in "Window Rules" but is broken in "Custom Shortcuts". Maybe move the functionality of executing a custom command on window events to "Window Rules"? I was surprised to find it in the shortcut section of System Setting. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Dmitry Alexandrov changed: What|Removed |Added CC||d...@gnui.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Adam Fontenot changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||adam.m.fontenot+kde@gmail.c ||om Ever confirmed|0 |1 --- Comment #8 from Adam Fontenot --- This issue has seemingly been around since around the time of the switch from QT4 to QT5. The main issue is here: https://invent.kde.org/plasma/khotkeys/-/blob/master/kcm_hotkeys/helper_widgets/window_selector.cpp#L36 QT5 passes xinput events here, but the filter only looks for the XCB_BUTTON_PRESS response type. Proper handling would involve looking for a XCB_GE_GENERIC response type as well, casting to a xcb_ge_generic_event_t, and checking that event for the XCB_INPUT_BUTTON_PRESS event type. I wrote an ugly proof of concept showing that this does fix the basic problem, but I didn't fully get the feature working again. Among other issues, clicking on a window that doesn't belong to the KCM seemingly gives a different event type, and the crosshair cursor is not used over these windows either. Probably KWin has changed how windows are given access to other windows they don't own, or something along those lines. Wasn't sure how to investigate this further. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 --- Comment #7 from dolge...@informatik.uni-erlangen.de --- Comment on attachment 137101 --> https://bugs.kde.org/attachment.cgi?id=137101 Current state on KDE Neon user Edition [Ubuntu 20-04 based] Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.6.0-1028-oem OS Type: 64-bit Graphics Platform: X11 Graphics Processor: Mesa Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 --- Comment #6 from dolge...@informatik.uni-erlangen.de --- Created attachment 137101 --> https://bugs.kde.org/attachment.cgi?id=137101&action=edit Current state on KDE Neon user Edition [Ubuntu 20-04 based] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 dolge...@informatik.uni-erlangen.de changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from dolge...@informatik.uni-erlangen.de --- After clicking the autodetect button, cursor turns into a crosshair. If you then click on the window whose properties should be transferred into the properties dialog, nothing else happens. Neither window title nor window class nor role or type of the window are recognized and inserted. The crosshair cursor also no longer disappears until systemsettings are closed, hence the dialog can only be closed with key actions. Apparently, somehow the communication between the GUI and some command called under the hood fails. The only workaround so far is to determine the window properties manually, e.g. with 'xprop'. This behavior has not changed since the original publication of this bug report until today, as of 2021-03-27. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 --- Comment #4 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||justin.zo...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #3 from Justin Zobel --- Thanks for the report. It appears this feature may have been removed since this report as I cannot find it from: System Settings > Shortcuts > Custom Shortcuts > (select group or make a new one) > Conditions tab > New > Active Window > Autodetect button under "Window Data" Can you please confirm if this feature is still present and if so, if the issues still persist? I've set this bug to NEEDSINFO. When you reply, please change the bug back to REPORTED so we know it's ready for investigation or RESOLVED/WORKSFORME if the issue is now resolved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109
dolge...@informatik.uni-erlangen.de changed:
What|Removed |Added
CC||dolge...@informatik.uni-erl
||angen.de
--- Comment #2 from dolge...@informatik.uni-erlangen.de ---
Can confirm: Sadly, this is still true for systemsettings 5.8.7, KDE
Frameworks 5.28.0, as shipped with Debian 9 stable ('stretch').
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Christoph Feck changed: What|Removed |Added Severity|crash |grave -- You are receiving this mail because: You are watching all bug changes.
