GNOME Bugzilla – Bug 501707
crash in Home Folder: browsing into a folder (...
Last modified: 2007-12-06 19:19:49 UTC
What were you doing when the application crashed? browsing into a folder (in Nautilus) with lots of documents (and thumbnails). Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-12 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.18-gentoo-r6 #2 SMP PREEMPT Mon Oct 22 15:54:34 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 287506432 vsize: 287506432 resident: 46010368 share: 20676608 rss: 46010368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1196850661 rtime: 444 utime: 392 stime: 52 cutime:0 cstime: 2 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) [Thread debugging using libthread_db enabled] [New Thread 47745499375632 (LWP 28817)] 0x00002b6c9c02db0f in waitpid () from /lib/libpthread.so.0
+ Trace 180803
Thread 1 (Thread 47745499375632 (LWP 28817))
----------- .xsession-errors --------------------- Initializing gnome-mount extension ** (nautilus:28817): WARNING **: Failed to initialize libhal context: (null) : (null) ** (nautilus:28817): WARNING **: Could not initialize hal context (nautilus:28817): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (nautilus:28817): GLib-GObject-CRITICAL **: g_object_weak_ref: assertion `G_IS_OBJECT (object)' failed Shutting down gnome-mount extension error: Could not find thumbnail in zip file ** 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 ***