Bug 489656 - Spectacle hangs, forcing to kill the process
Summary: Spectacle hangs, forcing to kill the process
Status: RESOLVED DUPLICATE of bug 489434
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 24.05.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-03 07:53 UTC by Andrea Ippolito
Modified: 2024-07-03 23:08 UTC (History)
2 users (show)

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

Attachments
spectacle hangs (11.16 KB, text/plain)
2024-07-03 07:53 UTC, Andrea Ippolito 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Ippolito 2024-07-03 07:53:13 UTC 
Created attachment 171320 [details]
spectacle hangs

"Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. "

I see plenty of these notifications whenever I try to activate spectacle to quickly capture a screenshot or recording

Eventually I'm forced to kill the app from System Monitor

journalctl logs attached
Comment 1 Andrea Ippolito 2024-07-03 07:56:47 UTC 
To reproduce: associate Meta + Shift + R to spectacle's "active window RECORDING"

Start a screen recording using that shortcut, select the window to capture. Tray icon with red full circle appears indicating recording in progress.

Click that icon to stop recording after a few seconds.

Expected: recording is stopped, spectacle main window appears or a notification appears informing the recording has been saved somewhere.

Actual: timer on tray icon stops progressing, but tray icon stays there. An error notification appears a while after. Trying to open spectacle again also does not work, only work to open it again is by killing the running instance first
Comment 2 Andrea Ippolito 2024-07-03 07:57:49 UTC 
Operating System: openSUSE Tumbleweed 20240701
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7
Comment 3 Vinícius 2024-07-03 17:50:35 UTC 
i can reproduce this too 
Operating System: Fedora Linux 41
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.10.0-0.rc6.50.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 7,6 GB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82MF
System Version: IdeaPad 3 15ALC6
Comment 4 Noah Davis 2024-07-03 23:08:37 UTC 
I see "*** pw_stream_destroy called from wrong context, check thread and locking: Not in loop" in the output, so this must be bug 489434

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