GNOME Bugzilla – Bug 498566
crash in Volume Control: I was just closing the a...
Last modified: 2007-11-20 19:42:37 UTC
Version: 2.18.0 What were you doing when the application crashed? I was just closing the application volume control 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37171200 vsize: 37171200 resident: 12615680 share: 9363456 rss: 12615680 rss_rlim: 4294967295 CPU usage: start_time: 1195582613 rtime: 66 utime: 59 stime: 7 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209042704 (LWP 2760)] (no debugging symbols found) 0x00f2a402 in __kernel_vsyscall ()
+ Trace 178972
Thread 1 (Thread -1209042704 (LWP 2760))
----------- .xsession-errors --------------------- alarm-queue.c:1998 (alarm_queue_add_async) - 0x96e4120 alarm-queue.c:585 (load_alarms_for_today) - From Tue Nov 20 19:05:30 2007 to Tue Nov 20 19:05:30 2007 alarm-queue.c:522 (load_alarms) alarm-queue.c:551 (load_alarms) - Setting Call b (nautilus:2511): Gtk-CRITICAL **: gtk_tree_view_set_cursor_on_cell: assertion `path != NULL' failed ** (nautilus:2511): WARNING **: Aucune description trouvée pour le type MIME « x-special/socket » (le fichier est « mapping-getty »), veuillez avertir la liste de diffusion de gnome-vfs. closing gnome-mount 0.6 closing gnome-mount 0.6 (gnome-volume-control:2760): 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 ***