GNOME Bugzilla – Bug 497817
crash in Volume Control:
Last modified: 2007-11-24 16:56:25 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 41218048 vsize: 41218048 resident: 13430784 share: 10043392 rss: 13430784 rss_rlim: 4294967295 CPU usage: start_time: 1195389899 rtime: 1676 utime: 1461 stime: 215 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208719120 (LWP 3880)] (no debugging symbols found) 0x00f86402 in __kernel_vsyscall ()
+ Trace 178457
Thread 1 (Thread -1208719120 (LWP 3880))
----------- .xsession-errors (7 sec old) --------------------- SESSION_MANAGER=local/unknown0000212b975d:/tmp/.ICE-unix/3424 (process:3648): 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. closing closing closing closing Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3000003 (1); these messages lack timestamps and therefore suck. gnome-mount 0.6 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 471133 ***