Microphone stops working after waking up computer from sleep

My headset microphone stops working after waking computer up from sleep.

Basic info:

  • Motherboard: Asus tuf b650 plus wifi
  • Headset: Kingston HyperX Cloud 2
  • OS: Fedora 41 KDE spin
  • Audio server: PulseAudio

I can fix the issue by switching the device profile either by the kde audio widget or via pactl. I do not see any audio related errors in the journal, and the output of wpctl looks the same before and after as well.

I have tried different USB ports (back and front panel), interacting with the headset controls, plugging the jack in/out of the headset control, all of which does nothing. I have also gone through my BIOS settings in case there are some sleep related USB settings, but I only found an option to enable/disable USB ports in general.

I would love some guidance what to try or what commands to run to point me in the right direction.

Why would you use pulseaudio? Did you configure that manually?

pactl info | grep "Server"

No, I have not touched anything related to audio as I’m aware. Does Fedora normally not ship with PulseAudio? Because my laptop running the same spin also has PulseAudio.

Command output:

Server String: /run/user/1000/pulse/native
Server Protocol Version: 35
Server Name: PulseAudio (on PipeWire 1.2.7)
Server Version: 15.0.0

Yeah you run Pipewire. For backwards compatibility, Pulseaudio runs as a part of pipewire

Please report this issue in the fedora bug tracker under the pipewire project, they might be able to help you.

bugzilla.redhat.com

Also use journalctl -g pipewire -p warning to get good logs for them

1 Like

I see, thanks for the explanation. TIL!

I’ll report the bug, thank you.

You may also want to look at:

  1. alsamixer when the problem is occuring to see if it’s automuted for some reason. You may need to install alsa-utils for this.
  2. systemctl --user --no-pager status wireplumber\* pipewire\* | sed "s/$(hostname)/ahost/"

Thank you for the advice.

  1. It’s not muted after waking up. I think I’d see that via the sound device widget, because I can see the values change there when I play with the volumes in alsamixer.
  2. I don’t see any logging for the time I put the computer to sleep and woke it back up (around 22:15)
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2025-03-01 18:03:16 CET; 1 day 4h ago
 Invocation: 234e5336295840cab6a2b256de9c2778
   Main PID: 1987 (wireplumber)
      Tasks: 9 (limit: 37250)
     Memory: 10.4M (peak: 11.1M)
        CPU: 37.622s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─1987 /usr/bin/wireplumber

bře 02 16:52:15 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce4fee30> link failed: some node was destroyed before the link was created
bře 02 16:52:16 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce84d060> link failed: some node was destroyed before the link was created
bře 02 18:23:39 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce961640> link failed: some node was destroyed before the link was created
bře 02 21:16:16 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce6004a0> link failed: some node was destroyed before the link was created
bře 02 21:16:16 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce8953a0> link failed: some node was destroyed before the link was created
bře 02 21:16:16 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce6004a0> link failed: some node was destroyed before the link was created
bře 02 21:16:51 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce3ad670> link failed: some node was destroyed before the link was created
bře 02 21:16:51 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce97cef0> link failed: some node was destroyed before the link was created
bře 02 21:16:51 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce3d3960> link failed: some node was destroyed before the link was created
bře 02 22:11:30 ahost wireplumber[1987]: wp-event-dispatcher: <WpAsyncEventHook:0x55f9ce486b70> failed: <WpSiStandardLink:0x55f9ce806200> link failed: 1 of 1 PipeWire links failed to activate

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2025-03-01 18:03:16 CET; 1 day 4h ago
 Invocation: 545e185cd6e3424dae248201daecaae1
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 1989 (pipewire-pulse)
      Tasks: 3 (limit: 37250)
     Memory: 91.8M (peak: 127.4M)
        CPU: 6min 14.016s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─1989 /usr/bin/pipewire-pulse

bře 01 18:03:16 ahost systemd[1709]: Started pipewire-pulse.service - PipeWire PulseAudio.

● pipewire.socket - PipeWire Multimedia System Sockets
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
     Active: active (running) since Sat 2025-03-01 18:03:16 CET; 1 day 4h ago
 Invocation: 7a1288ec175d49f48a3855ae67437bf4
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
             /run/user/1000/pipewire-0-manager (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

bře 01 18:03:16 ahost systemd[1709]: Listening on pipewire.socket - PipeWire Multimedia System Sockets.

● pipewire-pulse.socket - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
     Active: active (running) since Sat 2025-03-01 18:03:16 CET; 1 day 4h ago
 Invocation: e8f6677bc04c4b8f9cf6d19c15c02f45
   Triggers: ● pipewire-pulse.service
     Listen: /run/user/1000/pulse/native (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket

bře 01 18:03:16 ahost systemd[1709]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.

● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/pipewire.service.d
             └─00-uresourced.conf
             /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2025-03-01 18:03:16 CET; 1 day 4h ago
 Invocation: ab49a0b863cb49c4b2421ae4470fbbbb
TriggeredBy: ● pipewire.socket
   Main PID: 1986 (pipewire)
      Tasks: 3 (limit: 37250)
     Memory: 37.9M (peak: 51M)
        CPU: 5min 29.647s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─1986 /usr/bin/pipewire

bře 01 18:26:41 ahost pipewire[1986]: spa.alsa: front:0p: snd_pcm_drop: No such device
bře 01 18:26:41 ahost pipewire[1986]: spa.alsa: front:0p: close failed: No such device
bře 01 18:27:10 ahost pipewire[1986]: pw.node: (alsa_output.usb-Kingston_HyperX_7.1_Audio_00000000-00.analog-stereo-210) graph xrun not-triggered (0 suppressed)
bře 01 18:27:10 ahost pipewire[1986]: pw.node: (alsa_output.usb-Kingston_HyperX_7.1_Audio_00000000-00.analog-stereo-210) xrun state:0x7fced404f008 pending:1/2 s:1411862291511 a:1411862306037 f:1411862312527 waiting:14526 process:6490 status:triggered
bře 01 19:28:31 ahost pipewire[1986]: pw.node: (alsa_output.usb-Kingston_HyperX_7.1_Audio_00000000-00.analog-stereo-210) graph xrun not-triggered (0 suppressed)
bře 01 19:28:31 ahost pipewire[1986]: pw.node: (alsa_output.usb-Kingston_HyperX_7.1_Audio_00000000-00.analog-stereo-210) xrun state:0x7fced404f008 pending:1/3 s:5088386472056 a:5088386497186 f:5088386505025 waiting:25130 process:7839 status:triggered
bře 02 18:36:07 ahost pipewire[1986]: pw.node: (alsa_output.pci-0000_0e_00.6.analog-stereo-46) graph xrun not-triggered (0 suppressed)
bře 02 18:36:07 ahost pipewire[1986]: pw.node: (alsa_output.pci-0000_0e_00.6.analog-stereo-46) xrun state:0x7fced42ff008 pending:1/5 s:44278260329935 a:44278260409324 f:44278260444184 waiting:79389 process:34860 status:triggered
bře 02 20:25:05 ahost pipewire[1986]: pw.node: (alsa_output.usb-Kingston_HyperX_7.1_Audio_00000000-00.analog-stereo-210) graph xrun not-triggered (0 suppressed)
bře 02 20:25:05 ahost pipewire[1986]: pw.node: (alsa_output.usb-Kingston_HyperX_7.1_Audio_00000000-00.analog-stereo-210) xrun state:0x7fced404f008 pending:2/3 s:50815829292263 a:50815829326173 f:50815829333463 waiting:33910 process:7290 status:triggered
1 Like

Do you have pavucontrol or pavucontrol-qt installed?
If so could you try removing it and see if the same issue occurs?
It may also be worth trying on a new user or clearing out the wireplumber state.
mv ~/.local/state/wireplumber ~/.local/state/wireplumber.old
and then log out and log back in.

1 Like

Hi Joe, thank you for the suggestions. I have neither pavucontrol or pavucontrol-qt. Clearing out the wireplumber state also didn’t work.

However, this issue does not happen with a new user account. What could be causing this? Could this be a KDE setting or something running on login that makes this issue happen later on?

It’s possible but I’m not super familar with the KDE configuration files. I did some poking around in a VM and most of the changes I made ended up in ~/.local/state/wireplumber

You could compare anything in ~/.config and see if something jumps out at you that’s different.

1 Like

Finally figured you the root cause. It was a combination of my headset and having the audio volume widget (both on desktop and a panel, but either one is enough to cause the issue).

I was able to reproduce this issue on a fresh user account and on another device with the same headset. I’m not sure if it’s a headset issue in general or just my specific model, I don’t have another headset on hand to test.

However, I raised a bug on the KDE bugtracker here in order to get some resolution.

1 Like