Fluxer Direct Capture Audio pops up and becomes default silencing all apps on joining voice. Arch/PipeWire/KDE Wayland

Reproduction steps

Doesn't reproduce on my own machine. But here's what I did:

Join a voice channel (the bug might have occurred here)
Start a screen share (or here)
Chose my only screen

Observed behaviour

I just had a weird bug where I joined a voice channel and now I have a new mysterious audio device called Fluxer Direct Capture Audio and it's made default (as KDE shows), so apps output their sound to it. I had to reverse the setting back to Built-in Audio Analog Stereo to get my sound back. I didn't even get to hear people yet, but at least 1 person has heard what I said in the microphone, so voice calls are partially tested. I also have two of those "Fluxer Direct Capture Audio" devices right now, one with 95% volume and the other with 100% volume.

Build information

Stable Desktop 2026.1006.171735, Web 2026.1008.22643, Linux 7.2.9-arch1-1 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

Linux

Evidence

On screenshot, I already returned the default audio output choice back to normal. As for the transcript, I only launched with --ozone-platform=x11 to make user interface appear in the window, otherwise it's just the background color. And this isn't specific to Fluxer, I had to do the exact same thing for a Discord client when using the combination of KDE Wayland + nouveau (community driver for old NVidia graphics cards like mine that isn't known for its quality, though it's pretty cool and even supports Vulkan 1.2 on my GPU)

5 comments

FullestReviewer 1 vote 23d ago

I was able to reproduce it after all! The "Fluxer Direct Capture Audio" device only appears if you share "Entire system audio". My previous attempts had it only sharing a specific application's audio. Canary Desktop 2026.1009.45608, Web 2026.1011.125152, Linux 7.2.9-200.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Simon Elista OP1 vote 25d ago

Could reproduce after restarting the app. The bug happens on the actual start of a new screen share session.

Simon Elista OP1 vote 24d ago

At this point, I have tested all of listening, talking, screen share by me where others can hear my programs and screen share by others where I watch and listen to their programs. Everything seems to work, just that I have to set my normal actual headphones as the default audio output device, but, other than that, everything works.

FullestReviewer 1 vote 24d ago 1 reply

Hey there, if you are able to reproduce this again, could you also include your voice diagnostic info? To obtain it:

First enable Developer mode: fluxer://settings/user?tab=advanced_settings&section=advanced-settings-developer
Click on your user at the bottom left of the app
There will be a new option called "Copy voice diagnostics"

For screensharing and voice call issues specifically, this information is very helpful for troubleshooting. Ideally, you copy this info while in the voice call while this issue is happening. Unfortunately I tried following your steps and this did not happen for me. I tested with Stable Desktop 2026.1006.171735, Web 2026.1008.22643, Linux 7.2.9-200.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US and I'm on Fedora 44 with KDE Plasma.

Simon Elista OP1 vote 23d ago

The "trivial fix" in the name of the second file is indeed pretty trivial and refers to literally this: I open KDE sound settings and click the radio button for my headphones to make them the default audio output device. So that apps (including Fluxer) send their sound to my ears for me to hear again. Additional info: I asked a person if they could hear themself in my screenshare right after I started it and deliberately delayed fixing the bug, they said they could not hear themself (just like I couldn't hear them either). I figured that might be a useful test. Also, feel free to DM me on Fluxer to arrange a call where we could try to help fix the bug.