Summary: | Pipewire error log flood under Wayland | ||
---|---|---|---|
Product: | [Frameworks and Libraries] KPipeWire | Reporter: | alerikaisattera |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | aleixpol, kdedev, nate |
Priority: | NOR | Keywords: | efficiency-and-performance, regression |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=478309 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
alerikaisattera
2025-08-29 10:42:52 UTC
Might be related or not, but at some point Pipewire started using 100% of 1 CPU core This looks a lot like bug 478309, which had a fix merged in 6.0 Are you seeing any symptoms in the UI, aside from the high CPU usage? In the previous report, content preview windows from the task manager were empty Sending to KPipeWire There are no obvious problem in UI, but screen recording software, which supposedly requires Pipewire under Wayland, does not work Thanks, that's helpful information. I'll let those more familiar with the pipewire integration take it from here. |