GNOME Bugzilla – Bug 488136
crash in Volume Control: Only open the browser :s
Last modified: 2007-10-20 23:14:49 UTC
Version: 2.18.0 What were you doing when the application crashed? Only open the browser :s 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 42033152 vsize: 42033152 resident: 13688832 share: 10301440 rss: 13688832 rss_rlim: 4294967295 CPU usage: start_time: 1192763737 rtime: 123 utime: 109 stime: 14 cutime:6 cstime: 1 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 -1208297232 (LWP 4805)] (no debugging symbols found) 0x00ba2402 in __kernel_vsyscall ()
+ Trace 171313
Thread 1 (Thread -1208297232 (LWP 4805))
----------- .xsession-errors --------------------- QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver --- Hash table keys for warning below: --> file:///home/t00nny (nautilus:4808): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (gnome-volume-control:4805): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver --------------------------------------------------
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 ***