https://bugs.kde.org/show_bug.cgi?id=519916
Petr N. <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Petr N. <[email protected]> --- Yes, that journal command still shows these log lines under latest 7.0.0-28-generic and Plasma 6.7.3. Jul 22 06:23:28 plasmashell[2249]: PipeWire remote error: -2 unknown resource 3 op:7 Jul 22 06:23:28 plasmashell[2249]: PipeWire remote error: -2 unknown resource 3 op:4 Jul 22 06:23:28 plasmashell[2249]: PipeWire remote error: -2 target not found Jul 22 06:21:56 plasmashell[2249]: PipeWire remote error: -2 unknown resource 5 op:7 Jul 22 06:21:56 plasmashell[2249]: PipeWire remote error: -2 unknown resource 5 op:4 Jul 22 06:21:56 plasmashell[2249]: PipeWire remote error: -2 target not found it happens also after closing Strawberry audio player and running commands: systemctl --user stop pipewire pipewire-pulse pipewire-pulse.socket wireplumber wireplumber.socket pipewire.socket sleep 2 systemctl --user start pipewire sleep 2 systemctl --user start wireplumber sleep 1 systemctl --user start pipewire-pulse it appears in output of a "sudo journalctl -xefg pipewire --since today" command and then moving mouse cursor quickly between the opened app windows buttons in the task bar adds the log lines. AI hallucinates: "Plasmashell (pid 2249) is holding stale deleted PipeWire memfd buffers — these are leftover from a previous client (Strawberry) that disconnected. When you hover over taskbar buttons, plasmashell tries to use these dead references, triggering "unknown resource" and "target not found" errors. PipeWire 1.2.6 has a known issue with memfd cleanup on client disconnect. Let me search for the specific bug report." -- You are receiving this mail because: You are watching all bug changes.
