GNOME Bugzilla – Bug 460336
crash in Open Folder: opening a folder
Last modified: 2007-07-26 13:05:43 UTC
Version: 2.19.6 What were you doing when the application crashed? opening a folder Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.19.5 2007-07-18 (JHBuild) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Gummy Icon Theme: gnome Memory status: size: 299778048 vsize: 299778048 resident: 22728704 share: 13950976 rss: 22728704 rss_rlim: 18446744073709551615 CPU usage: start_time: 1185379282 rtime: 207 utime: 180 stime: 27 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47087868131744 (LWP 22028)] 0x00002ad37ca6fd4f in waitpid () from /lib/libpthread.so.0
+ Trace 150515
Thread 1 (Thread 47087868131744 (LWP 22028))
----------- .xsession-errors (15 sec old) --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** 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... GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized warning: .dynamic section for "/opt/gnome/bin/nautilus" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/opt/gnome/lib64/libgnomevfs-2.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***