Bug 500434 - KPipeWire hardware accelerated H.264 encoding doesn't work: "Failed to create DRM device. Error Cannot allocate memory"
Summary: KPipeWire hardware accelerated H.264 encoding doesn't work: "Failed to create...
Status: RESOLVED FIXED
Alias: None
Product: KPipeWire
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.3.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-19 21:45 UTC by Avraham Hollander
Modified: 2025-12-24 11:35 UTC (History)
3 users (show)

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

Attachments
Spectacle stdout/stderr (3.43 KB, text/x-log)
2025-02-19 21:45 UTC, Avraham Hollander 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Avraham Hollander 2025-02-19 21:45:15 UTC 
Created attachment 178612 [details]
Spectacle stdout/stderr

SUMMARY
Hardware accelerated H.264 encoding with KPipeWire does not work at all

STEPS TO REPRODUCE
1. Run spectacle from the command line
2. Make sure the video file format is set to MP4/H.264
3. Start a recording

OBSERVED RESULT
Hardware accelerated encoding fails with "kpipewire_record_logging: Failed to create DRM device. Error Cannot allocate memory", and it switches to software-based libx264

EXPECTED RESULT
Hardware accelerated encoding works

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-20R5-sched-ext (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-10310U CPU @ 1.70GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Intel® UHD Graphics
Comment 1 Avraham Hollander 2025-02-19 21:47:45 UTC 
I'm using KPipeWire 6.3.1, by the way. Not sure why I can't set that.
Comment 2 Nate Graham 2025-12-09 19:35:34 UTC 
Sorry this happened. I've just corrected the version number, so at least that's fixed now! Are you still seeing this issue happen in Plasma 6.5.4 or later?
Comment 3 Bug Janitor Service 2025-12-24 03:46:27 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Avraham Hollander 2025-12-24 11:35:32 UTC 
(In reply to Nate Graham from comment #2)
> Sorry this happened. I've just corrected the version number, so at least
> that's fixed now! Are you still seeing this issue happen in Plasma 6.5.4 or
> later?

No I am not. Sorry for thr late reply.