Pulseaudio segfaults when pavucontrol is open for a few seconds

dg10050 · 2009-07-23 02:59:01

Well, I'm a bit of a new Arch user (I used it for a couple of months about a year ago and now I'm trying it again).
Anyway, I just trying installing PulseAudio and pavucontrol seems to be causing PulseAudio to segfault.

Here's my /etc/asound.conf

pcm.!default {
    type pulse
}
ctl.!default {
    type pulse
}

I also set PA to use the combined sink so that the audio will come out of both my Creative SoundBlaster Live! 24-bit PCI and my Microsoft LifeChat LX-3000 USB headphones.
PulseAudio for the most part works great. My problem, though, is that whenever I open pavucontrol and leave it open for a few seconds, the message "Connection failed: Connection Terminated" appears and PulseAudio segfaults. If I don't open pavucontrol, everything works fine.
dmesg:

pulseaudio[26919]: segfault at 7fdceb0fb010 ip 00007fdceb0fb010 sp 00007fffee42af58 error 14 in pulse-shm-3705512939[7fdceb71a000+4001000]

This is obviously kind of annoying since the main reason I installed PulseAudio was for all of the nice volume controls in pavucontrol. If anyone knows what's happening please let me know.
Also, if you need any more info, just ask.

PS: I can control overall volume just fine with gnome-volume-control, but it obviously doesn't give me the same kind of control pavucontrol does.
I'm also having some problems with padevchooser. It runs fine, but it doesn't display any servers, sinks, or sources. Instead it just says "No Network Devices Found" in each menu. This doesn't seem to be related to the segfault issue, but it would be nice if someone knows how to fix it.

EDIT: Forgot to mention, using Arch64 2.6.30, PulseAudio 0.9.15-1, pavucontrol 0.9.8-1, latest updates.

I was also getting some messages like this in /var/log/messages.log, but they've since stopped. Not sure if it's related...

Jul 22 21:41:14 myhost pulseaudio[18265]: alsa-source.c: Increasing minimal latency to 316.00 ms
Jul 22 21:41:14 myhost pulseaudio[18265]: alsa-source.c: Increasing minimal latency to 326.00 ms
Jul 22 21:41:14 myhost pulseaudio[18265]: alsa-source.c: Increasing minimal latency to 336.00 ms
Jul 22 21:41:14 myhost pulseaudio[18265]: alsa-source.c: Increasing minimal latency to 341.33 ms
Jul 22 21:41:15 myhost kernel: 4:2:1: cannot get freq at ep 0x84
Jul 22 21:41:15 myhost kernel: 4:2:1: cannot get freq at ep 0x84
Jul 22 21:41:19 myhost pulseaudio[18265]: ratelimit.c: 19510 events suppressed
Jul 22 21:41:32 myhost pulseaudio[18265]: ratelimit.c: 1222 events suppressed
Jul 22 21:41:32 myhost kernel: 4:2:1: cannot get freq at ep 0x84
Jul 22 21:41:37 myhost pulseaudio[18265]: ratelimit.c: 18753 events suppressed
Jul 22 21:41:42 myhost pulseaudio[18265]: ratelimit.c: 18349 events suppressed
Jul 22 21:41:45 myhost kernel: pulseaudio[18265]: segfault at 7f757535d0a0 ip 00007f757535d0a0 sp 00007fffde7490c8 error 14 in pulse-shm-912049074[7f757597c000+4001000]

Last edited by dg10050 (2009-07-23 03:07:08)

djszapi · 2009-07-23 22:54:06

Jul 22 21:41:45 myhost kernel: pulseaudio[18265]: segfault at 7f757535d0a0 ip 00007f757535d0a0 sp 00007fffde7490c8 error 14 in pulse-shm-912049074[7f757597c000+4001000]

This is the point.

You can start to debug it with gdb, and run it, and when the segmentation fault occurs, with bt (backtrace) you can see the stack and the function callings, and you can see where is the problem, and report it.

Maybe this link helps, or not.
http://bbs.archlinux.org/viewtopic.php?pid=536741

dg10050 · 2009-07-24 02:39:37

Well, It seems like the problem was the fault of the snd_ca0106 driver for my Creative sound card. What tipped me off was when I tried to run pulseaudio through gdb and after a few steps gdb segfaulted. Then the following messages showed up on my terminal:

Segmentation fault
[dg10050@myhost ~]$ E: alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read!
E: alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_ca0106'. Please report this issue to the ALSA developers.
E: alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
E: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.ServiceUnknown

I solved the bluetooth error by just removing the bluetooth check from my /etc/pulse/default.pa since I don't have any bluetooth devices. (This only solved the bluetooth message, nothing else)
Then I blacklisted snd_ca0106 in my /etc/rc.conf, rebooted, and everything worked, but only on my USB headphones. So now I have headphones but no surround sound. :\
Pavucontrol works fine now, and pulseaudio is stable.

Does anyone have any info on debugging drivers or what I should do to report this bug?

ngoonee · 2009-07-24 02:52:23

In my experience the PA crew is pretty responsive, just give their bug-report system a crack. Or their ML.

gobeav3rs297 · 2009-10-14 21:02:14

I'm getting segmetation faults, I believe due to the new libgnome 2.28 package.

padevchooser[2073]: segfault at 4cfa ip b7029232 sp bf936f80 error 4 in libgobject-2.0.so.0.2200.2[b7002000+39000]
padevchooser[2579]: segfault at 10 ip b70ea232 sp bfebc5e0 error 4 in libgobject-2.0.so.0.2200.2[b70c3000+39000]

any chances that the maintainer will update the pulseaudio and said tools version? Pulseaudio is at 9.19 I believe and pavucontrol was just released last month

Arch Linux

#1 2009-07-23 02:59:01

Pulseaudio segfaults when pavucontrol is open for a few seconds

#2 2009-07-23 22:54:06

Re: Pulseaudio segfaults when pavucontrol is open for a few seconds

#3 2009-07-24 02:39:37

Re: Pulseaudio segfaults when pavucontrol is open for a few seconds

#4 2009-07-24 02:52:23

Re: Pulseaudio segfaults when pavucontrol is open for a few seconds

#5 2009-10-14 21:02:14

Re: Pulseaudio segfaults when pavucontrol is open for a few seconds

Board footer