Telegram not detected on PipeWire
Goosegit11 opened this issue · comments
✍️ Bug Description
#478
I use Arch Linux with Pipewire as audio backend
I have pipewire-pulse installed as well.
Soundux show no output applications.
I can't switch audio backend to PulseAudio, it instanly reverts back to Pipewire. In console it says:
Detected PipeWire-Pulse, please use the native pipewire backend
🔁 Steps to reproduce
Install flatpak by sudo pacman -S flatpak
Install Soundux by flatpak install soundux
open it
it shows "no output applications"
🖥️ Console Output
[21:49:50] [success] Config read
[21:49:50] [success] LibWnck found - Icon support is enabled
[21:49:50] [message] Connected to PipeWire ("pipewire-0") on version "0.3.66"
[21:49:50] [message] Found default device: "alsa_input.pci-0000_0b_00.4.analog-stereo"
Gtk-Message: 00:49:52.052: Failed to load module "xapp-gtk3-module"
Gtk-Message: 00:49:52.052: Failed to load module "canberra-gtk-module"
raw_alsa_helpers::enumerator::enumerate_devices: cannot determine device number: Inappropriate ioctl for device
[21:49:52] [failure] Failed to initialize libremidi: "raw_alsa_helpers::enumerator::enumerate_devices: cannot
determine device number: Inappropriate ioctl for device"
[21:49:52] [message] Using DISPLAY :0
Gtk-Message: 00:49:52.112: Failed to load module "xapp-gtk3-module"
Gtk-Message: 00:49:52.112: Failed to load module "canberra-gtk-module"
[21:49:52] [warning] Failed to find ppid of 87740, process does not exist
[21:49:52] [warning] Could not find proccess with id 87740
(soundux:2): Gdk-CRITICAL **: 00:49:52.745: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
❔ Expected behaviour
Show output applications such as Telegram Desktop
👀 Screenshots
🖥️ Operating System
Linux
🖥️ Distribution
Arch Linux
✅ I confirm that...
- I have collected all the required information and read all the comments in this document
- I searched for an existing bug report for this issue
- the problem does occur with the reproduction steps I provided
- what I described is indeed a problem
Are you in a call on Telegram Desktop and refreshed after the call has started?
I can't switch audio backend to PulseAudio, it instanly reverts back to Pipewire. In console it says:
Detected PipeWire-Pulse, please use the native pipewire backend
This is by design.
The pipewire backend will also pick up all applications that run through pipewire pulse.
The same thing is happening to me
Are you in a call on Telegram Desktop and refreshed after the call has started?
I was recording voice message, still no devices
Are you in a call on Telegram Desktop and refreshed after the call has started?
I was recording voice message, still no devices
Have you tried it with other applications?
Maybe Telegram is the culprit here.
All applications I've tried got picked up fine
well, yeah, discord works... but it's strange that telegram voice messages don't
well, yeah, discord works... but it's strange that telegram voice messages don't
Well now we know that telegram specifically is causing the issue and can investigate that.
It's probably caused by telegram not always pulling audio, this might already be resolved in the next update
sorry for incovenience and misunderstanding. hope that issue will be solved in the next updates!
afaik Telegram uses OpenAL for audio
afaik Telegram uses OpenAL for audio
Can you try this workaround from our FAQ?
That should only apply to pulse audio, not pipewire
Could be that pipewire-pulse has this also implemented
Could be that pipewire-pulse has this also implemented
PipeWire doesn't have facilities to restrict link creation, so highly unlikely
Edit: Also said setting prevents changing of the sink, which is not what happens when using the PipeWire backend