Bug 469459 - Spectacle doesn't quit correctly in a rather specific case, causing an issue with the toolbar (qdbus issue)
Summary: Spectacle doesn't quit correctly in a rather specific case, causing an issue ...
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 23.04.0
Platform: Manjaro Linux
: NOR wishlist
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-07 22:09 UTC by abbb56722
Modified: 2025-03-03 19:28 UTC (History)
2 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 abbb56722 2023-05-07 22:09:04 UTC
SUMMARY
Spectacle doesn't quit correctly in a rather specific case, causing an issue with the toolbar


STEPS TO REPRODUCE
1. Set the following checkboxes:
- Quit after manual Save or Copy
- Accept on click and release
2. Use the Shortcut for Capture rectangular region and do it
3.  Use the Shortcut for Capture rectangular region again

OBSERVED RESULT
The draggable toolbar doesnt open the second time, because Spectacle never closed to begin with after the first time.

EXPECTED RESULT
Spectacle closes after the first capture and reopens when the Shortcut is called again, making it possible to use the toolbar the second time the Shortcut is invoked.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma
KDE Plasma Version:  5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
The other settings I have, if relevant, are
-No delay
When launching Spectacle
    -Do not take a screenshot automatically
After taking a screenshot
    -Copy image to clipboard
Remember selected area
    -Never
No other checkboxes are selected
Comment 1 abbb56722 2023-05-09 19:05:10 UTC
UPDATE:
Every time I try to capture an image, I get this error on journalctl:
systemd[686]: Failed to start /usr/bin/qdbus
I don't know if this is just on my end, if it is Manjaro KDE related or if it is a common issue, but I guess mentioning it is the best thing to do.
Comment 2 Noah Davis 2025-03-03 19:28:26 UTC
This seems to have been fixed at some point between 23.04 and 24.12