Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#73965 - [telegram-desktop] Telegram Desktop Audio Output limited to Jack in Arch's custom build

Attached to Project: Community Packages
Opened by Salvatore (salvaju29ro) - Saturday, 26 February 2022, 13:06 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 09 March 2022, 02:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Jiachen Yang (farseerfc)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I've recently updated telegram-desktop from the official Arch community repo and the audio output options seems to be limited to Jack only.
My audio setup is pipewire along with pipewire-pulse and pipewire-jack installed.
However, if I run the official telegram desktop application from desktop.telegram.org all the audio output options show properly.
There seem to be something in the custom Arch build that limits or doesn't see all audio devices.

Additional info:

Telegram version: 3.5.2-1

As you can see in the Attach File, I have an audio playing on both Chromium and Telegram, but Telegram is not shown in the reproductions on Pavucontrol. Also there is no KDE audio applet either (Chromium is there) and no audio is shown in the panel icon either
   Screenshot_20220226_124836.png (739 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 09 March 2022, 02:11 GMT
Reason for closing:  No response
Additional comments about closing:  Request to re-open if there's good evidence that this is a packaging bug.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 27 February 2022, 17:02 GMT
Frankly, no good idea what this might be. I'd like to think that none of the relevant components for this are significantly different but maybe they are.
Comment by Christian Hesse (eworm) - Monday, 07 March 2022, 07:47 GMT
I have issues as well, can not start voice calls. Not sure if it is the same or related.
I have this in my logs:

```
Mar 07 08:30:44 archlinux wireplumber[1503]: <WpSiAudioAdapter:0x55578b76c660> no usable format found for node 121
Mar 07 08:30:44 archlinux wireplumber[1503]: <WpSiAudioAdapter:0x55578b76c660> failed to configure item for node 121
```
Comment by Christian Hesse (eworm) - Monday, 07 March 2022, 08:05 GMT
My issue was in wireplumber and is fixed with wireplumber 0.4.8-2 which cherry-picks this:
https://gitlab.freedesktop.org/pipewire/wireplumber/-/commit/afbc0ce57aac7aee8dc1651de4620f15c73dbace

Are you using wireplumber? Is it fixed for you?
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 07 March 2022, 22:54 GMT
Thing is I'm running PipeWire and I can't repro this at all, sound works just fine for me.

Loading...