GNOME Bugzilla – Bug 484119
crash in Open Folder: opening a folder
Last modified: 2007-11-24 19:11:29 UTC
Version: 2.18.3 What were you doing when the application crashed? opening a folder Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-04 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.21-gentoo-r4 #2 SMP Tue Jul 24 16:47:18 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: graphite Memory status: size: 88264704 vsize: 88264704 resident: 26841088 share: 14372864 rss: 26841088 rss_rlim: 4294967295 CPU usage: start_time: 1191684872 rtime: 207 utime: 189 stime: 18 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227724320 (LWP 5030)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 168314
Thread 1 (Thread -1227724320 (LWP 5030))
----------- .xsession-errors --------------------- ** (nautilus:5030): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory ** (nautilus:5030): WARNING **: Could not initialize hal context (nautilus:5030): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (nautilus:5030): GLib-GObject-CRITICAL **: g_object_weak_ref: assertion `G_IS_OBJECT (object)' failed Shutting down gnome-mount extension (gnome-panel:5029): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 41 ** 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... --------------------------------------------------
*** Bug 484355 has been marked as a duplicate of this bug. ***
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 ***
*** Bug 497691 has been marked as a duplicate of this bug. ***
*** Bug 498808 has been marked as a duplicate of this bug. ***