Bug 489633 - Spectacle freezing while using Screen Recording.
Summary: Spectacle freezing while using Screen Recording.
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-02 19:38 UTC by sig
Modified: 2024-07-05 05:57 UTC (History)
3 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 sig 2024-07-02 19:38:30 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

When selecting "Recording" in Spectacle this app freezes and crashes. When run in a terminal, this is what I get:
joe@venus:~$ spectacle 
kpipewire_vaapi_logging: VAAPI: Failed to initialize display
kpipewire_vaapi_logging: DRM device not found

Then when I select "Full Screen" I get this:


[libvpx-vp9 @ 0x74231826a040] v1.14.0
kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1
kpipewire_record_logging: Filter queue is full, dropping frame 3800
kpipewire_record_logging: Filter queue is full, dropping frame 3850
kpipewire_record_logging: Filter queue is full, dropping frame 3850
kpipewire_record_logging: Filter queue is full, dropping frame 3883


OS: EndeavourOS
Linux/KDE Plasma: 
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Graphics Platform: Wayland
Kernel Version: 6.6.36-1-lts (64bit)
Comment 1 Noah Davis 2024-07-03 23:07:36 UTC
Do you have pipewire 1.2 and do you have the following line in your terminal output?

> *** pw_stream_destroy called from wrong context, check thread and locking: Not in loop
Comment 2 sig 2024-07-04 18:48:29 UTC
(In reply to Noah Davis from comment #1)
> Do you have pipewire 1.2 and do you have the following line in your terminal
> output?
> 
> > *** pw_stream_destroy called from wrong context, check thread and locking: Not in loop

Yes, I have: extra/pipewire 1:1.2.0-2 [installed]

Output:
joe@venus:~$ spectacle 
kpipewire_vaapi_logging: VAAPI: Failed to initialize display
kpipewire_vaapi_logging: DRM device not found
[libvpx-vp9 @ 0x7da48418d300] v1.14.0
kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1
*** pw_stream_destroy called from wrong context, check thread and locking: Not in loop
Comment 3 Filip 2024-07-05 05:57:53 UTC

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