So far I have been using tumbleweed for years as a dev environment and had no problems. But, after yesterdays update 20210817 I lost headphones sound. Also microphone does not work. I have dual boot with elementary os and there the sound works just fine, so the hardware is not the issue. Any idea what caused this and how to fix it?
Create bug report.
Here audio works on 20210817, is there anything special with your setup? Bluetooth audio?
Can you post the output of “/usr/sbin/hwinfo --sound”?
See Getting debug output from pulseaudio, is pulseaudio verbose output giving any clues?
No nothing out of the most ordinary. Just headphones and mic
As for pulseaudio check, I think now pipewire is installed
And, here is the output:
[FONT=lucida console]13: PCI 1b.0: 0403 Audio device
[Created at pci.386]
Unique ID: u1Nb.sBVE6oKNP3F
SysFS ID: /devices/pci0000:00/0000:00:1b.0
SysFS BusID: 0000:00:1b.0
Hardware Class: sound
Model: "Intel 8 Series/C220 Series Chipset High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x8c20 "8 Series/C220 Series Chipset High Definition Audio Controller"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x1967
Revision: 0x05
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xd3714000-0xd3717fff (rw,non-prefetchable)
IRQ: 36 (564 events)
Module Alias: "pci:v00008086d00008C20sv0000103Csd00001967bc04sc03i00"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=yes, avail=yes, need=no, active=unknown
19: PCI 03.0: 0403 Audio device
[Created at pci.386]
Unique ID: 3hqH.3SDGXsiZ4YD
SysFS ID: /devices/pci0000:00/0000:00:03.0
SysFS BusID: 0000:00:03.0
Hardware Class: sound
Model: "Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x0c0c "Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x1967
Revision: 0x06
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xd3710000-0xd3713fff (rw,non-prefetchable)
IRQ: 35 (522 events)
Module Alias: "pci:v00008086d00000C0Csv0000103Csd00001967bc04sc03i00"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=yes, avail=yes, need=no, active=unknown
[/FONT]
Update:
I installed pulseaudio instead of pipewire-pulseaudio and now everything works fine. So, this is most probably a pipeweire bug
Okay, good to hear that switching to pulseaudio did solve the problem.
I am a bit confused about pulseaudio versus pipewire and *pipewire-pulseaudio *adds to that confusion.
I was pointed to this topic in this topic of mine:
https://forums.opensuse.org/showthread.php/558725-MAME-sound-stopped-working?p=3059924#post3059924
I am confused too, the way I understand pipe wire, this should not happen.
If a program wants something, pipe wire should provide it, it being puleaudio alsa or what ever.
Maybe we found a pipewire bug ?
My headset however still is working.
pipewire-pulseaudio
PulseAudio client library for PipeWire
As usual, developers are forcing pipewire, but it behaves badly.
If you want pipewire - install its latest code.
I had this same problem starting the same time you did.
I found that if I restarted Pipewire while I had my USB headset plugged in, Pipewire would detect it, but I’d have to manually switch audio output to the headset.
systemctl --user restart pipewire pipewire-pulse
[FONT=monospace]systemctl --user daemon-reload[/FONT]
I didn’t even notice when Pipewire replaced PulseAudio. But I’m glad to know that switching back to Pulse should fix it. So I just wanted to add my name to the list of people who experienced this issue. It’s not isolated.