Bug 397876

Summary: Spectacle locks up after KAlarm notification
Product: [Applications] Spectacle Reporter: Kevin <kjslag>
Component: GeneralAssignee: Boudhayan Gupta <me>
Status: RESOLVED FIXED    
Severity: normal CC: kjslag, noahadvs, rapiteanu.catalin
Priority: NOR    
Version First Reported In: 18.08.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Kevin 2018-08-26 01:10:56 UTC
If a KAlarm goes off while trying to select a rectangular region of a screenshot for Spectacle, it becomes impossible to exist the rectangle selection screen. Pressing 'escape' or 'enter' does nothing. The interface isn't frozen; the user can keep selecting rectangles forever if desired. But to get out of the rectangle selection interface, I had to kill Spectacle from a different TTY.
Comment 1 Viorel-Cătălin Răpițeanu 2019-02-12 06:49:57 UTC
I tried this on the master branches of Spectacle / KDE Frameworks and I wasn't able to reproduce it.
Comment 2 Viorel-Cătălin Răpițeanu 2019-02-12 06:56:00 UTC
https://drive.google.com/open?id=108fY8_jTR69jk54zvBOSr74CbbwXf14L
Video of one of the reproduction attempts.
Comment 3 Viorel-Cătălin Răpițeanu 2019-02-12 19:25:16 UTC
Does this still issue still reproduces on your machine using the latest version of Spectacle and Frameworks?
Comment 4 Kevin 2019-02-12 19:44:38 UTC
You did the right things to try to reproduce it. I don't know why you didn't experience the same issue. I just reproduced the issue with my current configuration and a clean configuration from a new user using the latest Archlinux packages as of yesterday: Spectacle 18.12.2, Frameworks 5.55.0, and Qt 5.12.1
Comment 5 Viorel-Cătălin Răpițeanu 2019-02-12 20:30:47 UTC
After reading your comment, I tried to reproduce this on another machine and surprise, it reproduced. After rebooting my main PC, I was able to reproduce it as well using the master branch of Spectacle and Plasma 5.15...
At the moment of the writing, I'm not exactly sure why I'm seeing this behavior...
Comment 6 Noah Davis 2024-10-14 15:13:16 UTC
This appears to be fixed. Significant changes happened between now and version 18.08, so it's hard to say when it might have been fixed, but it could have been version 23.04 or earlier.