GNOME Bugzilla – Bug 484026
crash in Open Folder: browsing directories
Last modified: 2007-10-10 22:56:01 UTC
Version: 2.18.3 What were you doing when the application crashed? browsing directories Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2008-09-30 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r5 #4 SMP Sat Sep 29 15:20:56 BST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 296951808 vsize: 296951808 resident: 33415168 share: 19951616 rss: 33415168 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191606791 rtime: 312 utime: 269 stime: 43 cutime:2 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 47859653468144 (LWP 7145)] 0x00002b872f78eaef in waitpid () from /lib/libpthread.so.0
+ Trace 168240
Thread 1 (Thread 47859653468144 (LWP 7145))
----------- .xsession-errors (52084 sec old) --------------------- SESSION_MANAGER=local/lignonberry:/tmp/.ICE-unix/7179 (gnome-panel:7255): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x5bcc60 (gnome-panel:7255): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x5bcc60 Initializing gnome-mount extension mail-notification-Message: Mail Notification is already running (gnome-panel:7255): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -13 and height 25 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
I've re-emerged packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui with the debug useflag. (USE="$USE debug" emerge glib gtk+ pango gnome-vfs libgnome libgnomeui) I hope this helps: Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2008-09-30 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r5 #4 SMP Sat Sep 29 15:20:56 BST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 303177728 vsize: 303177728 resident: 37523456 share: 19804160 rss: 37523456 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192055913 rtime: 94 utime: 75 stime: 19 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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46960520693120 (LWP 11515)] [New Thread 1132505408 (LWP 11569)] 0x00002ab5d6fb7aef in waitpid () from /lib/libpthread.so.0
+ Trace 169359
Thread 1 (Thread 46960520693120 (LWP 11515))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** 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 ***