GNOME Bugzilla – Bug 512519
crash in Open Folder: Just opening a folder by...
Last modified: 2008-01-28 11:14:11 UTC
Version: 2.18.3 What were you doing when the application crashed? Just opening a folder by clicking on the folder in the left hand pane. 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.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Clearlooks Memory status: size: 127455232 vsize: 127455232 resident: 45264896 share: 22233088 rss: 45264896 rss_rlim: 4294967295 CPU usage: start_time: 1201504398 rtime: 882 utime: 815 stime: 67 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) [Thread debugging using libthread_db enabled] [New Thread -1208703264 (LWP 30563)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187031
Thread 1 (Thread -1208703264 (LWP 30563))
----------- .xsession-errors --------------------- localuser:sidk being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/30446 Window manager warning: Invalid WM_TRANSIENT_FOR window 0x45 specified for 0xe005ca (). Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a0006b (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --- Hash table keys for warning below: --> file:///home/sidk (nautilus:1216): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** 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 ***