GNOME Bugzilla – Bug 171645
starting ogg123 makes gnome-volume-control crash
Last modified: 2007-06-21 16:15:51 UTC
Distribution: Fedora Core release Rawhide (Rawhide) Package: gnome-media Severity: normal Version: GNOME2.10.0 2.10.x Gnome-Distributor: Red Hat, Inc Synopsis: starting ogg123 makes gnome-volume-control crash Bugzilla-Product: gnome-media Bugzilla-Component: gnome-volume-control [was: gmix] Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: starting ogg123 makes gnome-volume-control crash Steps to reproduce the crash: 1. start gnome-volume-control, set the volume to a level you want 2. start music playback with ogg123 3. watch error window pop up, informing that gnome-volume-control has crashed Expected Results: gnome-volume-control should stay around, in case I want to adjust the volume during music playback How often does this happen? every time Additional Information: running on Fedora Rawhide of march 23: vorbis-tools-1.0.1-5 kernel-2.6.11-1.1191_FC4 Debugging Information: Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208408384 (LWP 22076)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x001207e2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 57336
Thread 1 (Thread -1208408384 (LWP 22076))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-25 16:46 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-media". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Please update gst-plugins to 0.8.8 and try again.
*** Bug 332259 has been marked as a duplicate of this bug. ***
*** Bug 335384 has been marked as a duplicate of this bug. ***
Hm, the duplicates that are reproducable with FC5 have a bit different backtrace. Here we have assertion failture, while, for example, 335384 has segfault. Probably they aren't dups?
+ Trace 69023
Thread 1 (Thread -1208952640 (LWP 6008))
And FC5 has 0.10, which I suppose even better than Ronald advised in comment #1
From https://launchpad.net/distros/ubuntu/+source/gnome-media/+bug/34514: "... (gnome-volume-control:9804): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GnomeVolumeControlVolume' Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1224403264 (LWP 9804)] 0x08051d9e in gnome_volume_control_volume_ask (vol=0x80ed9b0, real_zero=0xbf9ab614, slider_zero=0xbf9ab610) at volume.c:544 544 volumes = g_new (gint, vol->track->num_channels); (gdb) thread apply all bt
+ Trace 71564
Thread 1 (Thread -1224403264 (LWP 9804))
from the ubuntu bug: "I got this by enabling/disabling two separate PCM controls."
seems to work fine with GNOME 2.16 according to the ubuntu bug
Then let's leave it closed. I'm assuming it's all fixed. Reopen if not. This has been in the "is his reproduceable with a later version" (0.8.8) for ages now.
So, #357382 has a 0.10-specific backtrace, which makes this a gstreamer bug again (I'm assuming they didn't backport the relevant patches for 0.8). Either way, this is a gstreamer bug.
Whatever it was, it hasn't happened with edgy/feisty/FC6/FC7 yet as far as I can see, so let's close it for now. Please re-open if this still happens with recent versions of things. FWIW, fixes from the 0.8 were backported to 0.10, but I'm not sure when that was exactly (could have been after 2.14, too lazy to check now).