Bug 1223210

Summary: KDE6: Can not record screen on Wayland - Spectacle error
Product: [openSUSE] openSUSE Tumbleweed Reporter: Ferdinand Thiessen <rpm>
Component: KDE ApplicationsAssignee: E-Mail List <opensuse-kde-bugs>
Status: NEW --- QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: el
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Console output when running spectacle

Description Ferdinand Thiessen 2024-04-22 11:12:10 UTC
Created attachment 874413 [details]
Console output when running spectacle

On current Tumbleweed (KDE 6.0.4) Spectacle at least does not segfault anymore when trying to screen record (ref: boo#1222064).
But now after clicking "stop" Spectacle shows a failure and the recording fails:

"Failed to export video: Temporary file URL must be an existing local file"

I have attached the console output of Spectacle.
Comment 1 Ferdinand Thiessen 2024-04-22 11:14:50 UTC
Looks like this upstream issue: https://bugs.kde.org/show_bug.cgi?id=485733
Comment 2 Ferdinand Thiessen 2024-04-22 11:16:18 UTC
And to add more context: I think this might be related to the hardware I use:
I use a notebook with AMD APU (AMD Ryzen 5 5500U with Radeon Graphics)
Comment 3 ell1e 2024-04-26 20:52:50 UTC
I have possibly the same problem, Plasma 5 screen recording worked fine and Plasma 6 it's broken with both Spectacle and OBS:

$ spectacle 
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
qt.multimedia.ffmpeg.libsymbolsresolver: Couldn't load VAAPI library
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
Comment 4 ell1e 2024-05-06 01:55:36 UTC
For me, it's now working again. Maybe another update fixed it for me.
Comment 5 Ferdinand Thiessen 2024-05-06 15:42:07 UTC
Checked with todays version of Tumbleweed (2024-05-06) and it still fails with the same error.