FS#70337 - pipewire 0.3.24 and 0.3.25 don't work with integrated audiochip USB headset (Razer Electra V2)

Attached to Project: Arch Linux
Opened by Popolon (Popolon) - Wednesday, 07 April 2021, 20:55 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 06 May 2021, 20:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: No more sound with Pipewire 0.3.24 and 0.3.25.

Additional info:
* package version(s) 0.3.24, 0.3.25
* config and/or log files etc.
- Motherboard include (blacklisted) Intelaudio chipset, because of the lowquality snd_hda_intel + snd_hda_core
I use USB audio headset. After lsusb:

- Bus 002 Device 005: ID 1532:0514 Razer USA, Ltd Electra V2 USB is used for audio.

* link to upstream bug report, if any

Steps to reproduce:

plug the headset with pipewire 0.3.23, it works, upgrade to 0.3.24 or 0.3.25 restart pipewire daemon with "systemctl --user restart pipewire" (reload of systemd units with "systemctl --user daemon-reload" is needed) it doesn't work anymore. downgrade to 0.3.23, do the same, it works again.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 06 May 2021, 20:11 GMT
Reason for closing:  Works for me
Comment by Morten Linderud (Foxboron) - Wednesday, 07 April 2021, 21:01 GMT
Did you merge the pacnew files?
Comment by Popolon (Popolon) - Wednesday, 07 April 2021, 21:03 GMT
Upgrading alsa-card-profiles gst-plugin-pipewire pipewire-alsa pipewire-docs pipewire-jack pipewire-media-session pipewire-pulse doesn't break pipewire, only the uprade of pipewire package itself break the audio system.
Comment by Morten Linderud (Foxboron) - Wednesday, 07 April 2021, 21:05 GMT
ls /etc/pipewire/

Is there any pacnew files there?
Comment by Popolon (Popolon) - Thursday, 08 April 2021, 09:16 GMT
No pacnew file. I finally had to downgrade all *pipewire* to 0.3.23 (alsa-card-profiles must be the last one, not the 0.3.23 currently, perhaps I needed to reset something related to it?) to really resolve the issue, I had some strange issues else (that's not a suprise with mix of API versions)
Comment by Popolon (Popolon) - Thursday, 06 May 2021, 19:37 GMT
0.3.26 and 0.3.27 still have the same problem. I take the time search deeper.

I found some informations using with main user (used to listen sound) the command journalctl --user, ust after rebooting with new linux-5.12.1 and pipewire-0.3.27 packages installed.

I found those following lines: ("Opération non supportée" in french means "Operation Not supported")

<pre>
mai 06 21:30:20 poparch sudo[23940]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 06 21:30:20 poparch sudo[23940]: popolon : TTY=pts/3 ; PWD=/data/pacaur/ofono ; USER=root ; COMMAND=/usr/bin/pacman -U /home/popolon/.cache/pacaur/ofono/ofono-1.>
mai 06 21:30:20 poparch sudo[23940]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
mai 06 21:30:21 poparch sudo[23940]: pam_unix(sudo:session): session closed for user root
mai 06 21:30:37 poparch systemd[1191]: Stopping Multimedia Service...
mai 06 21:30:37 poparch xdg-desktop-por[1269]: Caught PipeWire error: connection error
mai 06 21:30:37 poparch systemd[1191]: pipewire.service: Deactivated successfully.
mai 06 21:30:37 poparch systemd[1191]: Stopped Multimedia Service.
mai 06 21:30:37 poparch systemd[1191]: Started Multimedia Service.
mai 06 21:30:37 poparch systemd[1191]: Started Multimedia Service Session Manager.
mai 06 21:30:37 poparch pipewire-media-session[24033]: core 0x55a949948e90: can't find protocol 'PipeWire:Protocol:Native': Opération non supportée
mai 06 21:30:37 poparch pipewire-media-session[24033]: can't start monitor: Opération non supportée
mai 06 21:30:37 poparch systemd[1191]: pipewire-media-session.service: Main process exited, code=exited, status=161/n/a
mai 06 21:30:37 poparch systemd[1191]: pipewire-media-session.service: Failed with result 'exit-code'.
mai 06 21:30:37 poparch systemd[1191]: pipewire-media-session.service: Scheduled restart job, restart counter is at 1.
mai 06 21:30:37 poparch systemd[1191]: Stopped Multimedia Service Session Manager.
mai 06 21:30:37 poparch systemd[1191]: Started Multimedia Service Session Manager.
mai 06 21:30:37 poparch pipewire-media-session[24040]: core 0x56172e9a6e90: can't find protocol 'PipeWire:Protocol:Native': Opération non supportée
mai 06 21:30:37 poparch pipewire-media-session[24040]: can't start monitor: Opération non supportée
mai 06 21:30:37 poparch systemd[1191]: pipewire-media-session.service: Main process exited, code=exited, status=161/n/a
mai 06 21:30:37 poparch systemd[1191]: pipewire-media-session.service: Failed with result 'exit-code'.
mai 06 21:30:37 poparch systemd[1191]: pipewire-media-session.service: Scheduled restart job, restart counter is at 2.
</pre>

After few loops, it end by:

<pre>
mai 06 21:30:38 poparch systemd[1191]: pipewire-media-session.service: Main process exited, code=exited, status=161/n/a
mai 06 21:30:38 poparch systemd[1191]: pipewire-media-session.service: Failed with result 'exit-code'.
mai 06 21:30:38 poparch systemd[1191]: pipewire-media-session.service: Scheduled restart job, restart counter is at 5.
mai 06 21:30:38 poparch systemd[1191]: Stopped Multimedia Service Session Manager.
mai 06 21:30:38 poparch systemd[1191]: pipewire-media-session.service: Start request repeated too quickly.
mai 06 21:30:38 poparch systemd[1191]: pipewire-media-session.service: Failed with result 'exit-code'.
mai 06 21:30:38 poparch systemd[1191]: Failed to start Multimedia Service Session Manager.
</pre>
Comment by Jan Alexander Steffens (heftig) - Thursday, 06 May 2021, 19:46 GMT
Does `pacman -Qkk pipewire pipewire-media-session` report anything?
Comment by Popolon (Popolon) - Thursday, 06 May 2021, 19:49 GMT
I followed this topic and found some similar errors : https://bbs.archlinux.org/viewtopic.php?id=264400

strace -f -o /tmp/pipe.txt pactl info

There are errors about libpulsecommon missing in /tmp/pipe.txt

25094 openat(AT_FDCWD, "/usr/lib/pulseaudio/glibc-hwcaps/x86-64-v2/libpulsecommon-14.2.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Aucun fichier ou dossier de ce type)
25094 newfstatat(AT_FDCWD, "/usr/lib/pulseaudio/glibc-hwcaps/x86-64-v2", 0x7ffcfac563b0, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type)

And I dont't have this lib at this place, instead:

$ pacman -Q -l libpulse | grep common
libpulse /usr/lib/pulseaudio/libpulsecommon-14.2.so

So I rm /etc/pulse/client.conf

Then forced reinstallation of libpulse : pacman -S libpulse

restarted pipewire, still have the same problem.

the lib path is /usr/lib/pulseaudio/libpulsecommon-14.2.so not /usr/lib/pulseaudio/x86_64/libpulsecommon-14.2.so
Comment by Popolon (Popolon) - Thursday, 06 May 2021, 19:57 GMT
Following then end of this bug, I backuped in /etc/pipewire/media-session.d/ alsa-monitor.conf and media-session.conf and replaced by the samefile.pacnew, restarted pipewire with:

pipewire --user restart

I have the following oerror in the (journalctl --user) log:

mai 06 21:51:56 poparch pipewire-media-session[27094]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit

but it works. Strangely still not volume in XFCE interface, but via pavucontrol, I can access to it, it works again in software :)

I see some errors about volume control:

mai 06 21:52:51 poparch pipewire-pulse[1413]: pulse-server 0x563f4cf883a0: [Contrôle du volume PulseAudio] ERROR command:87 (EXTENSION) tag:12 error:19 (Opération non supportée)
mai 06 21:52:51 poparch pipewire-pulse[1413]: pulse-server 0x563f4cf883a0: [Contrôle du volume PulseAudio] ERROR command:87 (EXTENSION) tag:13 error:19 (Opération non supportée)

I will see after restarting session, but the bug seems resolved.
Comment by Popolon (Popolon) - Thursday, 06 May 2021, 19:59 GMT
After restarting the session the volume control show again :). Problem solved.

Loading...