*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When the plasmashell crashed or restarted, Spectacle does not run anymore. Pressing the hotkeys or launching Spectacle directly does not do anything. STEPS TO REPRODUCE 1. Let plasmashell crash or restart 2. Run Spectacle after the crash or restart 3. Nothing will happen. Neither when pressing any hotkeys nor when launching Spectacle directly. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasmarch Linux x86_64 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0
How are you crashing or restarting plasmashell? I cannot reproduce this with `systemctl --user restart plasma-plasmashell.service` or `plasmashell --replace`.
(In reply to Noah Davis from comment #1) > How are you crashing or restarting plasmashell? I cannot reproduce this with > `systemctl --user restart plasma-plasmashell.service` or `plasmashell > --replace`. The crash is related to the Bug #487076 where I sent a full log using DrKonqi. On my Arch Linux installation "plasmashell" sometimes just crashes after the system rebooted. After plasmashell crashed and restarted itself I noticed that I couldn't make any screenshots anymore. As if Spectacle has completely locked up. I tried to kill Spectacle using "sudo pkill spectacle" and made sure no processes are running anymore. Either when I press the "PrntScr" key or launch Spectacle directly, nothing happens. I see the process running in "htop" but it doesn't do anything. I have to completely reboot my Arch Linux to make Spectacle work again.
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!
Perhaps this is actually a symptom of bug 483137?
(In reply to Noah Davis from comment #4) > Perhaps this is actually a symptom of bug 483137? Perhaps, I'm using Pipewire. So that would make sense. I have no idea how to confirm this bug is related though.