Bug 477864 - Pressing the Print Screen button causes too many Spectacle windows, which eventually causes KWin to crash
Summary: Pressing the Print Screen button causes too many Spectacle windows, which eve...
Status: RESOLVED DUPLICATE of bug 141968
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: git-master
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-12-01 20:30 UTC by Жора Змейкин
Modified: 2023-12-05 16:53 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Dump (58.56 KB, text/plain)
2023-12-05 14:04 UTC, Жора Змейкин 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Жора Змейкин 2023-12-01 20:30:21 UTC 
Accidentally pressed the Print Screen button and it caused the system to crash.

STEPS TO REPRODUCE
1. Open Spectacle and set "Use last-user capture mode" when you start Spectacle. Also set "Take a new screenshot" when the Print Screen button is pressed.
2. Use "Active Window" as the last shooting mode.
3. In any program, just press Print Screen and depending on how lucky you are, you'll get a system crash.

OBSERVED RESULT
Shell crash 

EXPECTED RESULT
Normal screenshot processing

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon (Unstable), Wayland
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0

ADDITIONAL INFORMATION
The bug may seem insignificant, but you can lose important data because of it. If the bug persists, try holding down the Print Screen key for a longer time
Comment 1 Жора Змейкин 2023-12-05 14:04:43 UTC 
Created attachment 163904 [details]
Dump

If it helps, here's the dump file
Comment 2 Prajna Sariputra 2023-12-05 16:04:44 UTC 
After following the given reproduction steps I can also get KWin to crash if I hold down the print screen key for a bit.
Comment 3 Nate Graham 2023-12-05 16:53:13 UTC 

*** This bug has been marked as a duplicate of bug 141968 ***