Bug 429630 - Spectacle does not launch properly (old design, functionality lost)
Summary: Spectacle does not launch properly (old design, functionality lost)
Status: RESOLVED NOT A BUG
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: 20.08.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-25 10:20 UTC by Daniel Duris
Modified: 2020-12-01 15:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Duris 2020-11-25 10:20:19 UTC
SUMMARY


STEPS TO REPRODUCE
1. Press PrintSCreen to launch Spectacle


OBSERVED RESULT
Spectacle is launched in weird (outdated) design and does not work on clicking a button to take screenshot (just minimizes and maximizes again)
console log:
kdeinit5: Got EXEC_NEW '/usr/bin/spectacle' from launcher.
kdeinit5: preparing to launch '/usr/bin/spectacle'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
kdeinit5: PID 537624 terminated.

EXPECTED RESULT
Spectacle is launched properly. (It can be launched alright if I call it from a launcher directly, not via PrintScreen button)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
Comment 1 Daniel Duris 2020-11-25 10:22:12 UTC
It seems to be launching as root by some mistake and no settings are respected, e.g. minimize/maximize is due to fullscreen capture instead of previously set rectangular region
Comment 2 Nate Graham 2020-11-30 22:29:58 UTC
If XDG_RUNTIME_DIR is not set, you're going to have problems with more than just spectacle. :)

What OS are you using and how did you install Spectacle or anything else?
Comment 3 Daniel Duris 2020-12-01 08:42:36 UTC
This was some weird bug as it has disappeared after reboot. I suspect some upgrade cause this.
Comment 4 Nate Graham 2020-12-01 15:50:58 UTC
OK, thanks. :)