Bug 1781054 - alt+f2 dos not bring up krunner
Summary: alt+f2 dos not bring up krunner
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-09 08:06 UTC by Karel Volný
Modified: 2020-01-08 17:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
KDE Software Compilation 413368 NOR REOPENED upgraded to 5.17.x, krunner alt-f2 shortcut stopped working 2020-01-27 14:07:40 UTC

Description Karel Volný 2019-12-09 08:06:40 UTC
Description of problem:
After upgrade to 5.17.4, I cannot run krunner via Alt+F2.

To be precise, after system start, I've successfully started konversation, kmail and one doplhin window via Alt+F2 and the application name. This was like within one minute from start.

Trying to start second Dolphin window, hitting Alt+F2 does not bring it (the krunner) up.

If I switch to konsole and try Alt+F2, it writes the capital "Q". Other Alt+F? combos seem to work without any problem.

Version-Release number of selected component (if applicable):
plasma-workspace-5.17.4-1.fc31.x86_64

Comment 1 Rex Dieter 2019-12-09 13:40:12 UTC
Known issue,
https://bugs.kde.org/show_bug.cgi?id=413368

The upstream bug includes some workarounds.

Comment 2 Karel Volný 2019-12-09 14:21:07 UTC
ok, thanks, running

/usr/lib64/kconf_update_bin/krunnerglobalshortcuts

(as user)

seems to fix the problem

now I just wonder how this could be put into the package so that it fixes itself on upgrade, not breaking users systems ...

Comment 3 Rex Dieter 2019-12-09 14:27:28 UTC
That is the mystery, those kconf_update scripts are supposed to run automatically to do just that.


Note You need to log in before you can comment on or make changes to this bug.