[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #11 from Nate Graham --- Yeah, that was the idea. And it should fix this bug for you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 Trent M changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED --- Comment #10 from Trent M --- (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? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #9 from Nate Graham --- 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? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 Trent M changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #8 from Trent M --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 --- Comment #6 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 --- Comment #5 from Trent M --- (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." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 --- Comment #4 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 --- Comment #3 from Nate Graham --- Can you try on Wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 --- Comment #2 from Trent M --- (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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453345] Restarting or refreshing Plasma Shell causes launcher to be unopenable via keyboard shortcut or DBus command
https://bugs.kde.org/show_bug.cgi?id=453345 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Hmm, those exact steps work for me. Is this X11 or Wayland? -- You are receiving this mail because: You are watching all bug changes.
