Screen share: system audio does not reach viewers on Linux (PipeWire errors, nothing logged, no notice) #751

Closed
opened 2026-11-16 06:21:42 +00:00 by charles · 1 comment
Owner

Reported by Charles, 2026-11-16 (Linux, AppImage nightly 2026.1116.341, PipeWire 1.6.11 with pipewire-pulse): "Sound from applications does not make it through the stream even when selecting Entire system audio."

Evidence from that machine's log (three shares in a row, all with audio requested):

screen share: capture start requested source=SystemPicker max_width=1920 max_height=1080 fps=60 audio=true
screen share: capture started width=1920 height=1080
voice: screen share published took_ms=6 codec=H264 … (the video track)
… 5 to 38 s later …
WARN fluxer_capture::pipewire_audio: stream audio: PipeWire error id=0 res=-2 unknown resource 14 op:7
WARN fluxer_capture::pipewire_audio: stream audio: PipeWire error id=0 res=-2 unknown resource 14 op:7
WARN fluxer_capture::pipewire_audio: stream audio: PipeWire error id=0 res=-2 unknown resource 15 op:7
  • The only stream audio lines in the whole log are these warnings: there is no line saying stream audio capture started, which nodes were linked, or that a screen-share audio track was published. So either the capture never starts, or it starts and logs nothing, or the track is never published.
  • res=-2 is ENOENT; op:7 on "unknown resource 14/15" means the client called a method on a proxy the server no longer knows (a destroyed node/link/port, e.g. a link created to a port that went away, or objects destroyed twice).
  • Default sink at the time: a USB headset's iec958-stereo output (an S/PDIF-profile sink). Worth checking whether the monitor of that sink, or its port layout, is what the capture fails to link to.

To find out (do not assume): how "Entire system audio" is captured (monitor of the default sink? a null sink plus links from every application stream? excluding the client's own playback so viewers do not hear the call twice?); where it fails on this setup; whether the failure is reported to the user (it is silent today: the share starts without audio and nothing says so); whether the audio track is published at all and what the viewer side receives.

Wanted. System audio reaches viewers on PipeWire setups like this one; every step logs at INFO (capture started with the target, links made, track published, first audio frame) and a failure is shown to the sharer (the original shows a notice when stream audio is unavailable — check) instead of a silent share.

**Reported by Charles, 2026-11-16 (Linux, AppImage nightly 2026.1116.341, PipeWire 1.6.11 with pipewire-pulse):** "Sound from applications does not make it through the stream even when selecting Entire system audio." **Evidence from that machine's log (three shares in a row, all with audio requested):** ``` screen share: capture start requested source=SystemPicker max_width=1920 max_height=1080 fps=60 audio=true screen share: capture started width=1920 height=1080 voice: screen share published took_ms=6 codec=H264 … (the video track) … 5 to 38 s later … WARN fluxer_capture::pipewire_audio: stream audio: PipeWire error id=0 res=-2 unknown resource 14 op:7 WARN fluxer_capture::pipewire_audio: stream audio: PipeWire error id=0 res=-2 unknown resource 14 op:7 WARN fluxer_capture::pipewire_audio: stream audio: PipeWire error id=0 res=-2 unknown resource 15 op:7 ``` - The only `stream audio` lines in the whole log are these warnings: there is **no line saying stream audio capture started, which nodes were linked, or that a screen-share audio track was published**. So either the capture never starts, or it starts and logs nothing, or the track is never published. - `res=-2` is ENOENT; `op:7` on "unknown resource 14/15" means the client called a method on a proxy the server no longer knows (a destroyed node/link/port, e.g. a link created to a port that went away, or objects destroyed twice). - Default sink at the time: a USB headset's `iec958-stereo` output (an S/PDIF-profile sink). Worth checking whether the monitor of that sink, or its port layout, is what the capture fails to link to. **To find out (do not assume):** how "Entire system audio" is captured (monitor of the default sink? a null sink plus links from every application stream? excluding the client's own playback so viewers do not hear the call twice?); where it fails on this setup; whether the failure is reported to the user (it is silent today: the share starts without audio and nothing says so); whether the audio track is published at all and what the viewer side receives. **Wanted.** System audio reaches viewers on PipeWire setups like this one; every step logs at INFO (capture started with the target, links made, track published, first audio frame) and a failure is shown to the sharer (the original shows a notice when stream audio is unavailable — check) instead of a silent share.
Author
Owner

Fixed in nightly 2026.1116.347. Not yet confirmed by the reporter in real use.

Fixed in nightly 2026.1116.347. Not yet confirmed by the reporter in real use.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#751
No description provided.