Bug 503816 - DAC Sennheiser GSX-1000 loses audio output after suspend and resume (PipeWire)
Summary: DAC Sennheiser GSX-1000 loses audio output after suspend and resume (PipeWire)
Status: RESOLVED UPSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-05 23:48 UTC by 14.wood
Modified: 2025-05-06 16:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description 14.wood 2025-05-05 23:48:22 UTC
## Description

After resuming from suspend on a freshly installed **Kubuntu 25.04 (x86_64)** system with KDE Plasma (Wayland) and PipeWire, the **Sennheiser GSX 1000** USB DAC remains detected and is still listed as the default audio output device. However, **no sound is heard** through it until the device is physically unplugged or reset via software.

The device stays listed with a valid output sink (`analog-output-surround71`) and is shown as active in `wpctl status`, but does not produce audio unless reset.

## Workaround

To automate recovery, I added a systemd sleep hook to trigger a soft USB reset using `usb_modeswitch`:

**/lib/systemd/system-sleep/fix-gsx1000**

```bash
#!/bin/bash
[ "$1" == "post" ] && $(which usb_modeswitch) -v 1395 -p 00a0 -R
exit 0
```

This consistently restores audio after suspend/resume.

## System Information

* **OS:** Kubuntu 25.04 x86_64 (fresh install)
* **Kernel:** `6.14.0-15-generic`
* **PipeWire version:** 1.2.7
  (`pipewire --version`: Compiled and linked with libpipewire 1.2.7)
* **systemd version:** 257 (257.4-1ubuntu3)
* **Audio device:** Sennheiser GSX 1000 (USB ID: `1395:00a0`)
* **Desktop:** KDE Plasma (Wayland session)

Feel free to ask for more information if needed

Thanks in advance!
Comment 1 Nate Graham 2025-05-06 16:17:03 UTC
This is definitely an upstream issue, and I'd encourage you to report it at https://gitlab.freedesktop.org/pipewire/pipewire/-/issues