GNOME Bugzilla – Bug 481330
crash in Volume Control:
Last modified: 2007-09-28 20:24:20 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.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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 27017216 vsize: 27017216 resident: 12599296 share: 9760768 rss: 12599296 rss_rlim: 4294967295 CPU usage: start_time: 1190982550 rtime: 3652 utime: 3580 stime: 72 cutime:1 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 -1208604432 (LWP 9368)] (no debugging symbols found) 0x00411402 in __kernel_vsyscall ()
+ Trace 166203
Thread 1 (Thread -1208604432 (LWP 9368))
----------- .xsession-errors (3336 sec old) --------------------- (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:11493): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' 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 ***