Bug 486246 - Cannot open Kickoff by pressing "Activate Application Launcher" shortcut after restarting Plasma by running "plasmashell --replace"
Summary: Cannot open Kickoff by pressing "Activate Application Launcher" shortcut afte...
Status: RESOLVED DUPLICATE of bug 493200
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-28 11:54 UTC by Patrick Silva
Modified: 2024-09-21 10:59 UTC (History)
5 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 Patrick Silva 2024-04-28 11:54:01 UTC
STEPS TO REPRODUCE
1. run "plasmashell --replace" with Krunner
2. try to open Kickoff by pressing meta key
3. 

OBSERVED RESULT
Kickoff does not open

EXPECTED RESULT
Kickoff opens

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Graphics Platform: Wayland
Comment 1 Nate Graham 2024-05-14 23:15:41 UTC
Can reproduce, only for the Meta key when KWin is handling it via the IIRC now-deprecated global "Activate Application Launcher" shortcut. Works fine when for shortcuts set on Kickoff itself.

Cannot reproduce when restarting plasmashell via systemd.
Comment 2 Nate Graham 2024-05-14 23:16:31 UTC
Moving back to Plasma as the shortcut is actually provided by Plasmashell, not KWin.
Comment 3 fanzhuyifan 2024-06-15 22:12:13 UTC
This also happens for the Meta+Q shortcut for switching activities. So this seems like an issue with all shortcuts registered by plasma shell, instead of an issue specific to the Meta shortcut

Only happens if plasmashell --replace is run while the old plasmashell process is running. If the old plasmashell process is first terminated, then this bug does not occur.
Comment 4 Patrick Silva 2024-09-21 10:59:41 UTC

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