GNOME Bugzilla – Bug 498378
crash in Volume Control: clicked on audio control...
Last modified: 2007-11-20 19:42:32 UTC
Version: 2.18.0 What were you doing when the application crashed? clicked on audio control from gnome toolbar Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 26570752 vsize: 26570752 resident: 11636736 share: 8794112 rss: 11636736 rss_rlim: 4294967295 CPU usage: start_time: 1195526279 rtime: 26 utime: 21 stime: 5 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208899872 (LWP 22695)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178847
Thread 1 (Thread -1208899872 (LWP 22695))
----------- .xsession-errors (33818 sec old) --------------------- # exiting MAIN FRAME # JPWS-F TERMINATED, 1195319760 Window manager warning: Treating resize request of legacy application 0x4400003 (Austins Li) as a fullscreen request Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (process:21074): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was called, but the GLib threading system has not been initialised yet, something that must happen before any other GLib function is called. The application needs to be fixed so that it calls if (!g_thread_supported ()) g_thread_init(NULL); as very first thing in its main() function. Please file a bug against this application. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 441641 ***