-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pulseaudio bails out on 1.2.13 (SIGSEGV), with MOTU Ultralite mk5 #483
Comments
Show ouput from |
Hey, Upon running
|
Ah, this was while having the downgraded package. Using 1.2.13 has this output:
|
It looks fine. You should work with pulseaudio developers to fix their code. |
I'm experiencing the exact same issue with my MOTU 828 (2024 version). It seems like PulseAudio no longer handles certain configurations well, even though it used to work fine. Version 1.2.13 makes it crash with a segmentation fault, but reverting to 1.2.12 resolves the problem. I'm on Manjaro Linux. Interestingly, I can still run alsaucm -c 2 dump text with version 1.2.13 installed. Here is the dump if this can help (1.2.13):
|
@Tomtomcapo I'm just preparing a bugreport in arch linux, which Manjaro builds from (most probably, because I couldn't find their sources for pulseaudio). |
The related fix is at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/838 |
Thanks. Closing. |
Hey,
I have this sound card and with the latest update (1.2.13), pulseaudio started to SIGSEGV and I have no sound.
Upon going to the pulseaudio IRC channel and talking to the devs, we've managed to point out that it's the UCM configuration that makes pulseaudio crash. Reverting to 1.2.12 made the crash cease.
It seems that the newly added configuration for the Ultralite makes pulseaudio crash. According to the below gdb traces, it seems the configuration drives pulseaudio into an infinite loop.
Beginning of the trace:
Inbetween there's just a lot of recursive calls. End of the trace:
Requested debug output from the pulseaudio project: https://termbin.com/n04r
Please investigate.
The text was updated successfully, but these errors were encountered: