GNOME Bugzilla – Bug 497975
crash in File Browser: I was just accesing my a...
Last modified: 2007-11-20 19:46:21 UTC
Version: 2.18.3 What were you doing when the application crashed? I was just accesing my a folder under my home directory ... Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-11 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.20-gentoo-r7 #19 Thu Jun 21 16:43:54 ART 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Aurora-looks Icon Theme: nuoveXT-1.6 Memory status: size: 95502336 vsize: 95502336 resident: 39215104 share: 20549632 rss: 39215104 rss_rlim: 4294967295 CPU usage: start_time: 1195413506 rtime: 254 utime: 234 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) 0xb7f5d410 in __kernel_vsyscall ()
+ Trace 178562
----------- .xsession-errors --------------------- aborting... Initializing gnome-mount extension ** (nautilus:12614): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket /var/run/dbus/system_bus_socket: No existe el fichero o el director ** (nautilus:12614): WARNING **: Could not initialize hal context (nautilus:12614): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (nautilus:12614): GLib-GObject-CRITICAL **: g_object_weak_ref: assertion `G_IS_OBJECT (object)' failed Shutting down gnome-mount extension ** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 459221 ***