| Summary: | Regression: krunner shortcuts do not invoke it | ||
|---|---|---|---|
| Product: | [Plasma] krunner | Reporter: | Dan Dascalescu <ddascalescu+kde> |
| Component: | general | Assignee: | Alexander Lohnau <alexander.lohnau> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | arojas, i, kde, kde, maugrerain, nate, plasma-bugs, prettyvanilla |
| Priority: | NOR | ||
| Version: | 5.21.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Jrunner screenshots are set | ||
Issue with the new DBus activation thing? Or was that master-only? Works for me FWIW. That was master only. Could you provide a dbus log what happens when you press the shortcut? either output from dbus-monitor (--pcap if possible) or capture recorder with bustle. Same here, but only when using systemd startup. dbus log:
method call time=1613931939.468899 sender=:1.10 -> destination=org.freedesktop.DBus serial=773 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameHasOwner
string "org.kde.klauncher5"
method return time=1613931939.469050 sender=org.freedesktop.DBus -> destination=:1.10 serial=20 reply_serial=773
boolean true
method call time=1613931939.469782 sender=:1.10 -> destination=org.kde.klauncher5 serial=774 path=/KLauncher; interface=org.kde.KLauncher; member=exec_blind
string "dbus-send"
array [
string "--type=method_call"
string "--dest=org.kde.krunner"
string "/App"
string "org.kde.krunner.App.toggleDisplay"
]
method return time=1613931939.491513 sender=:1.38 -> destination=:1.10 serial=74 reply_serial=774
So maybe dbus activation doesn't work with the systemd start? Is there something in the journal? >member=exec_blind string "dbus-send" array [ string "--type=method_call" string "--dest=org.kde.krunner" string "/App" string "org.kde.krunner.App.toggleDisplay" ] that's the old path. >but only when using systemd startup. Are you sure? The systemd startup isn't involved in this. It's a DBus call to krunner that goes into the same codepath on both. (In reply to David Edmundson from comment #5) > Are you sure? The systemd startup isn't involved in this. It's a DBus call > to krunner that goes into the same codepath on both. Well, it might be a coincidente. I could reproduce in 2/2 systemd boots and could not reproduce in 2/2 non-systemd boot. Does nothing happen either when you manually invoke the dbus-send method? (In reply to David Redondo from comment #7) > Does nothing happen either when you manually invoke the dbus-send method? Running the dbus command directly brings up the krunner window, as expected. Now KRunner is launched when I press Alt+Space or Alt+F2. I haven't changed any shortcut settings. Maybe the latest batch of updates fixed it? I'm on KDE neon. I can still reproduce it on 5.21.1, but seems to work on random (very few) boots. Not working for me with 5.79/5.21.2 on Manjaro. From dbus-monitor: method call time=1615155173.079010 sender=:1.12 -> destination=org.freedesktop.DBus serial=1008 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameHasOwner string "org.kde.klauncher5" method return time=1615155173.079025 sender=org.freedesktop.DBus -> destination=:1.12 serial=24 reply_serial=1008 boolean true method call time=1615155173.079137 sender=:1.12 -> destination=org.kde.klauncher5 serial=1009 path=/KLauncher; interface=org.kde.KLauncher; member=exec_blind string "" array [ ] method return time=1615155173.082874 sender=:1.5 -> destination=:1.12 serial=75 reply_serial=1009 *** This bug has been marked as a duplicate of bug 413368 *** |
Created attachment 135918 [details] Jrunner screenshots are set I've installed KDE neon 5.21, and none of the listed shortcuts invoke Krunner. Other global shortcuts do work, such as Print invoking Spectacle, or Alt+F3 triggering the window menu. `krunner` does launch from the terminal, or from Kickoff via `Run krunner`.