GNOME Bugzilla – Bug 477944
crash in Volume Control: Adjusting sound preferen...
Last modified: 2007-09-18 10:05:01 UTC
Version: 2.18.0 What were you doing when the application crashed? Adjusting sound preferences 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 41476096 vsize: 41476096 resident: 13357056 share: 10006528 rss: 13357056 rss_rlim: 4294967295 CPU usage: start_time: 1190092531 rtime: 136 utime: 115 stime: 21 cutime:3 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 -1208235792 (LWP 4650)] (no debugging symbols found) 0x00b41402 in __kernel_vsyscall ()
+ Trace 163679
Thread 1 (Thread -1208235792 (LWP 4650))
----------- .xsession-errors (8 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/Sombra:/tmp/.ICE-unix/3821 Loading "installonlyn" plugin Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne Loading "installonlyn" plugin Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00003 (Virtual Ma) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (gnome-volume-control:4650): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed --------------------------------------------------
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 471133 ***