Device randomly incorrectly identified
Hi, I don't know if this is the same issue than #1036 but I have randomly devices that are correctly identified and randomly incorrectly. In my case any port has a chance to do it: USB, Jack, etc. The only exception are NVIDIA HDMI which seem to always work properly and laptop integrated speakers.
On 3 different machines, the bug is similar but with some differences. OS wise all systems are running PopOS 20.10.
Machine 1: Custom hardware (ASUS P9X79, Intel® Core™ i7-4820K CPU @ 3.70GHz × 8, GTX 650 Ti DirectCU 2 2Gb VRAM (ASUS)).
- When you plug any jack you have a random chance pulseaudio does not see the proper "Line Out" but instead sees "Digital Output" or "Dummy Output" sometimes both. The device only works if detected as "Line Out".
- Unpluging and re-pluging does not fix anything you have to either reboot the entire system but most of the time
systemctl restart pulseaudio --user.
- Since latest update of PulseAudio (13.99.2 on my system) the problem is worse as the chances to have the system identify properly jack on the first boot is now like 1 over 5-6 boots while before it was 1 over 2-3 boots.
- USB not tested on this machine.
Machine 2: System76 Oryx Pro (oryp7 with RTX 3060)
- Jack seem to always work.
- Internal speakers seem to always work.
- When booting the system in full NVIDIA (not in hybrid and not in compute or integrated graphics) mode there's a very very small chance of getting Internal Speakers replaced by NVIDIA when no HDMI cable is plugged in (occured only once).
- USB wise, the device is randomly "Digital Output" and randomly "Analog Output" and randomly both. Sometimes one, the other or both modes work.
- Restarting PulseAudio does not fix anything, only rebooting or unplugging re-plugging many many times until it works properly (yesterday re-plugged it near 50 times before it worked).
- Usually when it defaults to "Analog Output", then "Analog Output" will work, when it defaults to "Digital Output" then its "Digital Output" that will work. However sometimes dispite the default none will work and sometimes both will work.
Machine 3: HP ElliteBook 840 G3
- Jack is combined mic + speakers, the combined port never ever worked properly on Linux. The laptop refuses to use a mic when plugged to this combined port. However long ago when it was running Windows it could do it fine.
- Before PulseAudio 13.99.2 bluetooth audio was very unstable: everytime you connected a BT headset you had a very high chance the headset would be connected according to bluetooth but would not be recognized at all by PulseAudio.
- With the latest PulseAudio updates on the system, bluetooth audio became much more stable, the recognize bug occured once since.
Both systems runs PulseAudio 13.99.2 and Pipewire 0.3.10. Only the first and third machine has ever ran on previous versions of PulseAudio which appeared more stable except for bluetooth.