GNOME Bugzilla – Bug 402003
gnome-volume-control crashed on closing
Last modified: 2007-07-27 09:56:27 UTC
That bug has been described on https://launchpad.net/ubuntu/+source/gnome-media/+bug/82077 "Binary package hint: gnome-media I have multi channel soundcard, ice1712 chipset based. 1) I opened Volume Control, 2) enabled all preferences (Edit => Preferences) aviable for sound card, 3) set them as I needed them, 4) and then closed Volume Control. It crashed, however it saved all changes I made. ProblemType: Crash Date: Mon Jan 29 09:09:24 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-volume-control Package: gnome-media 2.17.90-0ubuntu1 ProcCmdline: gnome-volume-control ..." Debug backtrace for the crash:
+ Trace 106215
crashed for me when closing a terminal (?) soundcard is some intel hda crap 2.17.90
+ Trace 118426
could just see that here, too
+ Trace 120135
The Ubuntu bug has 33 duplicates now, seems to happen to many users, do you need any extra information about it?
I can't reproduce the problem here. It looks like the problem is with the combo boxes used in the options tab (you might need to tweak the preferences to show a few of those). A reproducer, or the help of a person that can reproduce the problem at will would be useful.
distribution bug comment: "I think you can repro this crash only once in every install, so I did it using the Feisty LiveCD. Steps I did to reproduce this crash: 1. Open Volume Control (only Master and PCM are shown). 2. Go to Edit -> Preferences and enable all tracks (Master, PCM, LFE, IEC958, IEC958 Capture, Capture, Capture Mux, Input Source). 3. In Playback tab, change Master volume to max, PCM to near min, LFE to max and unmute LFE (using the toggle button). 4. In Recording tab, change Capture volume to some medium level and toggle audio recording to Mic. 5. Go to Switches tab (just look but don't touch anything), and do the same for Options tab. 6. Go back to Playback tab, change Capture Mux to some medium level and then mute it (using the toggle button). 7. Close Volume Control (using the X in the corner). That's all. I know these are a lot of steps, and I think the important one is step 6, but i did a LOT of reboots trying to isolate this problem. May be I'll keep trying later."
You can probably reproduce it everytime you re-load the driver? Could you attempt that?
what do you mean by "re-load the driver"? Is there an alsa command doing that?
modprobe -r $driver && modprobe $driver for the driver name, see lsmod.
not easy when the driver is being used
close the process that uses it lsof /dev/snd/pcmC0D0p or so to see which process uses it (probably esd/pulse/mixer-applet/*).
New comment: "Ok, I've been playing with gnome-volume-control. It always crashes (not only once in every install as I though), but apport is launched only the first 2 times in every install. So, the easy way to make it crash and get some advise: 1. In a terminal, load gnome-volume-control. 2. Be sure the Options tab is enabled. If it isn't, enable "Input Source" in Edit -> Preferences. 3. Go to the Options tab, and set the focus in the combobox. 4. Change to other tab (be sure the focus is not in the tab title). 5. Close the window. So, the terminal will show something like this: (gnome-volume-control:5906): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed Segmentation fault (core dumped) I hope this helps." The steps trigger the crash on my desktop
From the description, it looks like a gtk bug. Can you reproduce with gtk from dapper or whatever (same binary of g-v-c)? If not, I'll move this to gtk.
That happens on edgy with GTK 2.10.6, I'll try on dapper later
So what I mean is that I'd like it reproduced on a different gtk version. :-). Dapper is just an example, any version (!=2.10.x) will do.
Wasn't it fixed in bug #430746?
Seems to work fine now, that might be the GTK+ bug pointed which has been fixed, closing