Bug 416776 - Colourschemes window accepts input when I press krunner shortcut (alt + space)
Summary: Colourschemes window accepts input when I press krunner shortcut (alt + space)
Status: RESOLVED DUPLICATE of bug 416145
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.17.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-26 03:25 UTC by Kishore Gopalakrishnan
Modified: 2020-01-28 19:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kishore Gopalakrishnan 2020-01-26 03:25:50 UTC
SUMMARY
If the focus is on the 'edit colour scheme' button, pressing alt+space to invoke krunner results in the button also being activated.

STEPS TO REPRODUCE
1. Open the colour schemes selection screen (Appearance > Colours).
2. Press the edit button on a colour scheme.
3. Close the edit window which opens.
4. Now press Alt+Space to invoke krunner.

OBSERVED RESULT
Krunner opens, but immediately closes since the edit button also somehow detects the 'space' key and opens the edit window.

EXPECTED RESULT
Krunner should open, and nothing should happen in the system settings application.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0

ADDITIONAL INFORMATION
I'm not sure if this is a bug in the system settings application, in krunner or in whatever handle keyboard shortcuts, but I'm reporting it here.
Comment 1 Matthew Woehlke 2020-01-27 15:28:22 UTC
I've experienced this with other applications. Pretty sure it's somewhere in the krunner/kwin/plasma/dbus stack. Ways in which it the bug could live there are pretty obvious; ways in which kcmshell / a specific kcm could be at fault are difficult to imagine (aside from being deliberate, anyway).

FWIW, in my experience, it seems more likely to happen either during a long-running session and/or when KF5 packages are upgraded during a session (i.e. before logging out and back in).
Comment 2 Nate Graham 2020-01-28 19:08:58 UTC

*** This bug has been marked as a duplicate of bug 416145 ***