Bug 1974589

Summary:	krunner fails to open by ALT-F2 shortcut
Product:	[Fedora] Fedora	Reporter:	Stefan Neufeind <redhat>
Component:	plasma-workspace	Assignee:	KDE SIG <kde-sig>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	34	CC:	constantine.karnacevych, jgrulich, jmulligan, kde-sig, me, m, pv.bugzilla, rdieter, sbobber, svcrdhtbgzll, than
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-07 22:26:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stefan Neufeind 2021-06-22 06:29:59 UTC

Trying to open krunner using Alt-F2 does not show the runnner. Instead it logs:
plasmashell[4884]: Cannot load library libkdeinit5_: (libkdeinit5_: cannot open shared object file: No such file or directory)

Works fine with:
plasma-workspace-5.21.5-3.fc34.x86_64
kf5-krunner-5.82.0-1.fc34.x86_64

Fails with:
plasma-workspace-5.22.1-1.fc34.x86_64
kf5-krunner-5.83.0-1.fc34.x86_64
(from updates-testing)

Downgrading only of the two packages didn't seem to resolve the issue. Works fine after both downgrades (with dependencies of plasma-workspace).

Comment 1 Rex Dieter 2021-06-22 17:02:40 UTC

The error mentioned is a false-alarm I believe (I've seen similar errors when krunner if functioning properly too).

But ALt-F2 not showing krunner *is* a problem, does manually running this fix it for you:
/usr/lib64/kconf_update_bin/krunnerglobalshortcuts

?? 

If so, that's a known upstream issue.

Comment 2 Rex Dieter 2021-06-22 18:13:56 UTC

Upstream bug,
https://bugs.kde.org/show_bug.cgi?id=437364

Thought they claim it should be fixed in 5.22.1 release. :(

Comment 3 Stefan Neufeind 2021-06-24 07:06:54 UTC

* Reinstalled updates, problem appeared
* Run /usr/lib64/kconf_update_bin/krunnerglobalshortcuts and rebootet
* Now Alt-F2 works as usual.

Comment 4 Rex Dieter 2021-07-07 16:40:26 UTC

*** Bug 1978825 has been marked as a duplicate of this bug. ***

Comment 5 Rex Dieter 2021-07-07 16:42:21 UTC

Anyone still experiencing this, can you please attach your ~/.config/kglobalshortcutsrc here on in the upstream bug,
https://bugs.kde.org/show_bug.cgi?id=437364

Comment 6 Rex Dieter 2021-08-03 13:39:49 UTC

*** Bug 1989307 has been marked as a duplicate of this bug. ***

Comment 7 Michael Tunnell 2021-08-05 16:01:24 UTC

Here is the krunner data from kglobalshortcutsrc, maybe it's because there are now 2 entries krunner in this config file.


[krunner.desktop]
RunClipboard=Alt+Shift+F2,Alt+Shift+F2,Run command on clipboard contents
_k_friendly_name=KRunner
_launch=Search\tAlt+F2\tMeta+Space,Alt+Space\tAlt+F2\tSearch,KRunner

[org.kde.krunner.desktop]
RunClipboard=,Alt+Shift+F2,Run command on clipboard contents
_k_friendly_name=KRunner
_launch=\t\t,Alt+Space\tAlt+F2\tSearch,KRunner

Comment 8 Phil V 2021-08-17 03:46:22 UTC

Michael, I had this also, and running /usr/lib64/kconf_update_bin/krunnerglobalshortcuts removed one and got it working.

(In reply to Michael Tunnell from comment #7)
> Here is the krunner data from kglobalshortcutsrc, maybe it's because there
> are now 2 entries krunner in this config file.
> 
> 
> [krunner.desktop]
> RunClipboard=Alt+Shift+F2,Alt+Shift+F2,Run command on clipboard contents
> _k_friendly_name=KRunner
> _launch=Search\tAlt+F2\tMeta+Space,Alt+Space\tAlt+F2\tSearch,KRunner
> 
> [org.kde.krunner.desktop]
> RunClipboard=,Alt+Shift+F2,Run command on clipboard contents
> _k_friendly_name=KRunner
> _launch=\t\t,Alt+Space\tAlt+F2\tSearch,KRunner

Comment 9 Ben Cotton 2022-05-12 15:36:40 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 10 Ben Cotton 2022-06-07 22:26:46 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.