Fedora Sound issue

Ask Fedora
1

Fedora 43 Workstation, PipeWire 1.4.10, WirePlumber 0.5.13

USB Turtle Beach Stealth 600 G2 (wireless dongle) suspends after ~5-10 seconds of silence.
No sound until I manually switch output device (sink). But after switching, sound returns for only ~5 seconds, then suspends again – need to switch again.

Playing audio for ~10+ seconds keeps it active until reboot, but issue returns after reboot.

Tried:

  • session.suspend-timeout-seconds = 0 for exact node.name in ~/.config/wireplumber/wireplumber.conf.d/
  • restarted wireplumber & pipewire
  • full user config reset + package reinstall

No permanent fix. Config seems ignored or overridden.

Known bug in F43 with USB headsets? Any solution?

Thanks!

2

Ever made any changes to power profiles with powertop or something like it and maybe set the USB power timeout to 5 seconds?

If not, post the output from journalctl showing the dongle in use and stopping after 5 to 10 seconds.

I assume you’ve moved this dongle from port to port to see if the same issue is found on all usb ports and connections?

3

I think the problem is from autosuspend, because after wrestling with AI for 1 hour, it finally said ‘Now I’m almost sure the issue is from it suspending.’ But it couldn’t fix it. And yes, it behaves the same on all ports. I 100% believe this is a software issue.

I’ve never touched any power profile settings or anything similar before, and I didn’t even have powertop installed until now.

Also, honestly, if I play a YouTube video and let it run for 20 minutes, the sound doesn’t cut out at all. But as soon as I stop/pause the video, after about 5 seconds the sound cuts out / the device disappears, and I have to switch between audio devices (in the sound settings) to make it come back

and journalctl resault :

Dec 19 01:19:48 fedora kernel: Linux version 6.17.1-300.fc43.x86_64 (mockbuild@5381c258a4b3436489a448ea66bda8ce) (gcc (GCC) 15.2.1 20250924 (Red >
Dec 19 01:19:48 fedora kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.17.1-300.fc43.x86_64 root=UUID=8df4954f-cb2e-4dd4-b612-bd1a34052f07 >
Dec 19 01:19:48 fedora kernel: BIOS-provided physical RAM map:
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000005efff] usable
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x000000000005f000-0x000000000005ffff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x0000000000060000-0x000000000009ffff] usable
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x000000008caf3fff] usable
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x000000008caf4000-0x000000008e6f7fff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x000000008e6f8000-0x000000008e775fff] ACPI data
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x000000008e776000-0x000000008ebfbfff] ACPI NVS
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x000000008ebfc000-0x000000008f40dfff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x000000008f40e000-0x000000008f40efff] usable
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x000000008f40f000-0x000000008fffffff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Dec 19 01:19:48 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x000000046dffffff] usable
Dec 19 01:19:48 fedora kernel: NX (Execute Disable) protection: active
Dec 19 01:19:48 fedora kernel: APIC: Static calls initialized
Dec 19 01:19:48 fedora kernel: efi: EFI v2.7 by American Megatrends
Dec 19 01:19:48 fedora kernel: efi: ACPI 2.0=0x8e712000 ACPI=0x8e712000 TPMFinalLog=0x8eb96000 SMBIOS=0x8f1a8000 SMBIOS 3.0=0x8f1a7000 MEMATTR=0x>
Dec 19 01:19:48 fedora kernel: random: crng init done
Dec 19 01:19:48 fedora kernel: efi: Remove mem48: MMIO range=[0xe0000000-0xefffffff] (256MB) from e820 map
Dec 19 01:19:48 fedora kernel: e820: remove [mem 0xe0000000-0xefffffff] reserved
Dec 19 01:19:48 fedora kernel: efi: Not removing mem49: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
Dec 19 01:19:48 fedora kernel: efi: Not removing mem50: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
Dec 19 01:19:48 fedora kernel: efi: Not removing mem51: MMIO range=[0xfed00000-0xfed03fff] (16KB) from e820 map
Dec 19 01:19:48 fedora kernel: efi: Not removing mem52: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
Dec 19 01:19:48 fedora kernel: efi: Remove mem53: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Dec 19 01:19:48 fedora kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
Dec 19 01:19:48 fedora kernel: secureboot: Secure boot enabled
Dec 19 01:19:48 fedora kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
Dec 19 01:19:48 fedora kernel: SMBIOS 3.2.1 present.
Dec 19 01:19:48 fedora kernel: DMI: ASUS System Product Name/PRIME B360-PLUS, BIOS 3101 09/10/2021
4

That is just the first page of the journal output.

You might find it easier to run journalctl -f in a terminal window, which will show you the last few lines of journal log constantly. it “follows” the end of the log.

Play some music through the device - you should see stuff happen in the log. Stop the music, let the issue occur, and you should see some more stuff appear - Cut and Paste that screenful or so of data - it should be quite obvious where to start copying from and go to the end. I’m interested in seeing what happens your issue takes place and the dongle suspends or vanishes.

In addition, you’re running a kernel which is quite old - you might find that things are fixed in the 6.18.

On top of that, your BIOS is from 2021, so a BIOS update, assuming something newer is available, would also be recommended given the symptoms you’re experiencing… edit - seems that’s the newest available BIOS that ASUS bother to make.

5

I waited several minutes, but honestly, this was pretty much the maximum that showed up. And basically, after playing music or stopping it, not much gets logged at all.

vixland@fedora:~/Documents/games$ journalctl -f 
Feb 03 04:30:01 fedora systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Feb 03 04:30:01 fedora systemd[1]: user-0.slice: Consumed 1.826s CPU time, 237.6M memory peak.
Feb 03 04:33:30 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Feb 03 04:33:34 fedora rtkit-daemon[842]: Successfully made thread 7984 of process 2864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Feb 03 04:33:34 fedora gsd-media-keys[2573]: Unable to get default sink
Feb 03 04:33:34 fedora wireplumber[2391]: GLib-GIO: Unexpected reply 3 when releasing name org.freedesktop.ReserveDevice1.Audio1
Feb 03 04:33:39 fedora rtkit-daemon[842]: Successfully made thread 8048 of process 2864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Feb 03 04:33:46 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Feb 03 04:33:48 fedora rtkit-daemon[842]: Successfully made thread 8106 of process 2864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Feb 03 04:33:48 fedora gsd-media-keys[2573]: Unable to get default sink
Feb 03 04:39:22 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Feb 03 04:39:24 fedora rtkit-daemon[842]: Successfully made thread 8533 of process 2864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Feb 03 04:39:24 fedora gsd-media-keys[2573]: Unable to get default sink
Feb 03 04:39:53 fedora ptyxis[6960]: void vte_terminal_set_size(VteTerminal*, long int, long int): assertion 'columns >= 1' failed
Feb 03 04:40:20 fedora NetworkManager[977]: <info>  [1770129620.7423] dhcp4 (enp0s20f0u1): state changed new lease, address=10.222.196.47
Feb 03 04:40:20 fedora systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Feb 03 04:40:20 fedora systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Feb 03 04:40:20 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 04:40:30 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Feb 03 04:40:30 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 04:40:44 fedora rtkit-daemon[842]: Successfully made thread 9236 of process 8117 (/usr/lib64/firefox/firefox) owned by '1000' RT at priority 10.
Feb 03 04:40:46 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Feb 03 04:40:48 fedora rtkit-daemon[842]: Successfully made thread 9256 of process 2864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Feb 03 04:40:48 fedora gsd-media-keys[2573]: Unable to get default sink
6

Any difference on the most recent kernel, rather than the 6.17 one you’re currently running?

7

My kernel version is completely up to date and it’s exactly the 6.18 that you mentioned

vixland@fedora:~/Documents/games$ uname -r
6.18.7-200.fc43.x86_64
8

Ah - my bad. I read the last line of the first log you posted, which was from Dec 19th.

Dec 19 01:19:48 fedora kernel: DMI: ASUS System Product Name/PRIME B360-PLUS, BIOS 3101 09/10/2021
9

I’m now 100% sure that my device is suspending. What should I do?

vixland@fedora:~/Documents/games$ journalctl -b -f
Feb 03 05:03:21 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 05:03:21 fedora audit: BPF prog-id=124 op=UNLOAD
Feb 03 05:03:21 fedora audit: BPF prog-id=123 op=UNLOAD
Feb 03 05:03:21 fedora audit: BPF prog-id=122 op=UNLOAD
Feb 03 05:03:21 fedora audit: BPF prog-id=125 op=LOAD
Feb 03 05:03:21 fedora audit: BPF prog-id=126 op=LOAD
Feb 03 05:03:21 fedora audit: BPF prog-id=127 op=LOAD
Feb 03 05:03:21 fedora systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Feb 03 05:03:21 fedora systemd[1]: Started systemd-timedated.service - Time & Date Service.
Feb 03 05:03:21 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 05:03:51 fedora systemd[1]: systemd-timedated.service: Deactivated successfully.
Feb 03 05:03:51 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 05:03:51 fedora audit: BPF prog-id=128 op=LOAD
Feb 03 05:03:51 fedora audit: BPF prog-id=129 op=LOAD
Feb 03 05:03:51 fedora audit: BPF prog-id=130 op=LOAD
Feb 03 05:03:51 fedora audit: BPF prog-id=127 op=UNLOAD
Feb 03 05:03:51 fedora audit: BPF prog-id=126 op=UNLOAD
Feb 03 05:03:51 fedora audit: BPF prog-id=125 op=UNLOAD
Feb 03 05:03:51 fedora systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Feb 03 05:03:51 fedora systemd[1]: Started systemd-timedated.service - Time & Date Service.
Feb 03 05:03:51 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 05:04:01 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Feb 03 05:04:10 fedora audit: BPF prog-id=131 op=LOAD
Feb 03 05:04:10 fedora systemd[1]: Starting logrotate.service - Rotate log files...
Feb 03 05:04:10 fedora systemd[2192]: Started app-gnome-gnome\x2dsound\x2dpanel-12060.scope - Application launched by gnome-shell.
Feb 03 05:04:10 fedora systemd[1]: logrotate.service: Deactivated successfully.
Feb 03 05:04:10 fedora systemd[1]: Finished logrotate.service - Rotate log files.
Feb 03 05:04:10 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 05:04:10 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 05:04:10 fedora audit: BPF prog-id=131 op=UNLOAD
Feb 03 05:04:19 fedora pulseaudio[2864]: Failed to create sink input: sink is suspended.
Feb 03 05:04:19 fedora pulseaudio[2864]: Failed to create sink input: sink is suspended.
Feb 03 05:04:19 fedora pulseaudio[2864]: Failed to create sink input: sink is suspended.
Feb 03 05:04:19 fedora gnome-control-center[10778]: Failed to play sound: Invalid state
Feb 03 05:04:21 fedora systemd[1]: systemd-timedated.service: Deactivated successfully.
Feb 03 05:04:21 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 05:04:21 fedora audit: BPF prog-id=130 op=UNLOAD
Feb 03 05:04:21 fedora audit: BPF prog-id=129 op=UNLOAD
Feb 03 05:04:21 fedora audit: BPF prog-id=128 op=UNLOAD
10

Disable the pulseaudio suspend on idle; comment this line out from your default.pa file, by adding a # in front of it:

### Automatically suspend sinks/sources that become idle for too long
load-module module-suspend-on-idle

Restart PA, or reboot to make sure it’s disabled. Still doing it?

1 Like
11

Thank you for helping me, it’s solved :heart:

2 Likes