SUMMARY I refresh Plasma Shell via DBus whenever my screen arrangement changes as a workaround to make the minimize effect go to the right place, and sometimes restart it via `plasmashell --replace` if it acts weird in a different way. Any time I restart or refresh it this way, I become unable to open the application launcher both via its keyboard shortcut as well as via the DBus command (and the keyboard shortcut might just be doing the DBus command for all I know). STEPS TO REPRODUCE 1. `qdbus org.kde.plasmashell /PlasmaShell refreshCurrentShell` or `plasmashell --replace` 2. `qdbus org.kde.plasmashell /PlasmaShell activateLauncherMenu` OBSERVED RESULT The application launcher does not open. There is nothing in console output from Plasma Shell or the qdbus command to indicate that there is anything wrong. EXPECTED RESULT The application launcher opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.24.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3
Hmm, those exact steps work for me. Is this X11 or Wayland?
(In reply to Nate Graham from comment #1) > Hmm, those exact steps work for me. Is this X11 or Wayland? X11. I'm using an Optimus laptop with NVidia as the primary GPU to get around an xorg/kernel bug that makes the entire display stack lock up when playing games.
Can you try on Wayland?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Nate Graham from comment #3) > Can you try on Wayland? I'm sorry it's taken me so long to get a reply to this. Nate, I have to be real with you. I am absolutely terrified to even *look* in Wayland's direction on this Optimus laptop. Because for the past few weeks, if trying to use Wayland broke anything on my system, I would be in *huge* trouble. I finally found some time to make islolated snapshots of my BTRFS subvolumes and boot into them so I could finally test this. Attempting to start Wayland on this computer takes me to a black screen and a cursor. No panel, no wallpaper. No keyboard shortcuts. Nothing. So Wayland has bigger problems on this setup. Sorry I made you wait so long only to give you no useful information other than "Wayland broke on Optimus, big surprise."
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
Hi there. Nate, I noticed in one of your blog posts, you mentioned the following bug fix: > Application Launcher widgets that you activate by pressing the Meta key no longer require that the Alt+F1 shortcut to be set, which should dramatically reduce instances where you press the Meta key and nothing happens. After I used the Configure Application Launcher dialog to set the keyboard shortcut to Alt+F1, the qdbus command to open the launcher menu started to work again. What's funny is that if you restart plasmashell, the keyboard shortcut still stops working, but the qdbus command continues to work. The keyboard shortcut I really want for the launcher is Meta+Space, so I left Alt+F1 there, and created a custom shortcut that executes the qdbus command, and it continues to work across multiple restarts of plasmashell. So this bug is tangentially related to #391322, maybe? I think that what this proves is that the two symptoms: "keyboard shortcut stops working after restarting plasmashell" and "dbus command stops working after restarting plasmashell" are separate and not tied to the same root cause.
If Kickoff also loses the Alt+F1 shortcut, it would make sense. That part of the bug is fixed in Plasma 5.26 at least, which should effectively fix this bug for you. Losing the shortcut still isn't ideal though. Can you confirm that when you run `qdbus org.kde.plasmashell /PlasmaShell refreshCurrentShell` or `plasmashell --replace`, Kickoff explicitly loses its default Alt+F1 shortcut?
(In reply to Nate Graham from comment #9) > Can you confirm that when you run `qdbus org.kde.plasmashell /PlasmaShell > refreshCurrentShell` or `plasmashell --replace`, Kickoff explicitly loses > its default Alt+F1 shortcut? It doesn't seem to *lose* the shortcut, however, the presence of any *default* shortcut is gone, and doesn't ever come back. To clarify what I mean by that, in System Settings, the keyboard shortcut for Plasma -> Activate Application Launcher, there are no checkboxes at all under default shortcuts. The only shortcut that exists is Alt+F1 explicitly defined as a custom shortcut. So I guess the *default* shorcut is lost, and doesn't come back. But the *custom* shortcut is left alone. > If Kickoff also loses the Alt+F1 shortcut, it would make sense. That part of > the bug is fixed in Plasma 5.26 at least, which should effectively fix this > bug for you. Losing the shortcut still isn't ideal though. I suppose it would "effectively" be the case, but with that same definition, I "fixed" the bug by setting Meta+Space to run the qdbus command to open the launcher, which only works if the launcher has an Alt+F1 shortcut. I'd prefer to just bind the launcher to Meta+Space directly, but no keyboard shortcut at all--Alt+F1, Meta+Space, or otherwise--works after restarting plasmashell. Perhaps the "remove shortcut requirement for activating launcher" part of the fix 391322 might have a positive effect on the reliability of shortcuts other than the default one?
Yeah, that was the idea. And it should fix this bug for you.