search

GoXLR-on-Linux / goxlr-utility

An unofficial GoXLR App replacement for Linux, Windows and MacOS
MIT License
670 stars 37 forks source link

No audio profiles available and thus no outputs available #34

Closed RyderForReal closed 2 years ago

RyderForReal commented 2 years ago

Distro: Arch Linux, kernel 5.19.10-zen1-1-zen (so keep in mind that this could have nothing to do with the GoXLR daemon as Arch has a tendency of doing interesting things at interesting times) DE: KDE (X11) Full-size GoXLR (USB passthrough) Daemon v. 0.4.0 Audio control via KDE Settings

Everything worked perfectly until a system update about 3-4 days ago, at which point audio output completely stopped working. I checked KDE Settings and am unable to select any audio profiles (and thus none of the GoXLR outputs register). The daemon works fine in the sense that I can control the device without any issues.

Troubleshooting steps attempted: Pacman reinstall of pipewire, pipewire-pulse, wireplumber, pipewire-jack, pipewire-alsa, etc. - Didn't work, tried reinstall with -Rsc on second try, also didn't fix the issue Tried pipewire-media-session, didn't work Checked for updates and updated, didn't work Tried to build goxlr-utility from source, didn't fix the issue

This could be a PipeWire problem since I can control my device just fine. On the other hand, other audio outputs show up and have available profiles.

FrostyCoolSlug commented 2 years ago

This was a bug introduced with the latest kernel, and should be fixed with the next release, check out https://bugzilla.kernel.org/show_bug.cgi?id=216500 for details.

cmoro-deusto commented 2 years ago

Just in case helps somebody else, the bug was introduced in version 5.19.9. As of today, only workaround is to rollback to 5.19.8. I can also confirm it occurs in bare metal kernel, not only in -zen.

FrostyCoolSlug commented 2 years ago

I'm gonna reopen this, just so it's more visible until a kernel is released with the fix, as far as I've seen, 5.19.10 should have it fixed again.

FrostyCoolSlug commented 2 years ago

Currently not fixed in 5.19.10, looks like the fix will be going into 5.19.11 instead.

pwae commented 2 years ago

reports in upstream that this made it into 5.9.12 - this is available in unstable on Manjaro - waiting for it to reach unstable myself to test.

FrostyCoolSlug commented 2 years ago

I've had reports on discord that it's working again in 5.9.12, I'll await your confirmation though, and will double check the latest 5.15 release as well.

Edit: From the change log, it looks like the offending commit was reverted in 5.9.12, 5.15.71 and 6.0-rc7

cmoro-deusto commented 2 years ago

If it helps, I can confirm is working again in 5.19.12

FrostyCoolSlug commented 2 years ago

Lots of reports that everything is working again under 5.19.12 (thanks @cmoro-deusto and the various peoples on discord), so I'm going to close this as 'fixed'.