Bug 483668 - Screen recording not working anywhere
Summary: Screen recording not working anywhere
Status: RESOLVED DUPLICATE of bug 483137
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-15 13:34 UTC by thomas.garnier
Modified: 2024-04-11 03:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thomas.garnier 2024-03-15 13:34:36 UTC
SUMMARY
In any software, be it OBS or WebRTC (Brave/Chrome) or even Spectacle, I just cannot get a video capture of any screen or window. When Pipewire's selection appears, all I see are icons instead of the contents.

STEPS TO REPRODUCE
1. Open a software, any that can watch the screen (let's say OBS)
2. Screencast either an app or a screen
3. Select one, and wait...

OBSERVED RESULT
Nothing happens. No capture performed.
On OBS, not even a pixel appears, and the box stays 0x0.
On Brave, the cast just stops.
On Spectacle, the capture border remains, with the darker background around and all, and I have to kill Spectacle's process to take it out.

EXPECTED RESULT
A screen capture.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.7.8-arch1-1.1-g14
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Here are the terminal outputs in OBS, Brave, and Spectacle:

OBS:
...
info: ------------------------------------------------
info: [pipewire] Screencast session created
info: [pipewire] Asking for desktop
warning: [pipewire] Failed to start screencast, denied or cancelled by user

Brave (Chrome):
...
[6525:6525:0315/141916.271709:ERROR:screencast_portal.cc(367)] Failed to start the screen cast session.
[6525:6525:0315/141916.271747:ERROR:base_capturer_pipewire.cc(81)] ScreenCastPortal failed: 3

Spectacle, trying to screen record:
kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found
kpipewire_record_logging: VAAPI: Failed to initialize display
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"
kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found
kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found
Comment 1 thomas.garnier 2024-03-19 17:33:36 UTC
Update: 
I tried to create a new user to see if the problem still occured, and... It didn't.

That would mean there's a broken compatibility between KDE 5 and KDE 6, and my config files are still akin to KDE 5.

What config files should I delete?
Comment 2 thomas.garnier 2024-03-19 17:46:30 UTC
So, I could isolate and fix the issue:
I have made an autoscript to restart pipewire, which was for me a hotfix for the volume control only showing "100%".

But apparently, in plasma 6, that caused pipewire's screen recording to break.


Might there be a deeper issue to this?
Comment 3 Nicolas Fella 2024-03-19 22:40:01 UTC
Sounds related to https://bugs.kde.org/show_bug.cgi?id=483137
Comment 4 Nate Graham 2024-04-11 03:31:29 UTC
In fact it sounds like exactly the same thing! A classic case of the workaround for a minor bug causing a much bigger bug.

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