GNOME Bugzilla – Bug 485983
crash in Volume Control: Exiting
Last modified: 2007-10-14 19:16:37 UTC
Version: 2.18.0 What were you doing when the application crashed? Exiting 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: 41639936 vsize: 41639936 resident: 11948032 share: 9031680 rss: 11948032 rss_rlim: 4294967295 CPU usage: start_time: 1192172057 rtime: 42 utime: 30 stime: 12 cutime:2 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 -1208567568 (LWP 13196)] (no debugging symbols found) 0x005ab402 in __kernel_vsyscall ()
+ Trace 169701
Thread 1 (Thread -1208567568 (LWP 13196))
----------- .xsession-errors (6 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/12870 Loading "installonlyn" plugin compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 Window manager warning: Invalid WM_TRANSIENT_FOR window 0x320000c specified for 0x320ecbe (Downloadin). (gnome-volume-control:13196): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed --------------------------------------------------
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 ***