GNOME Bugzilla – Bug 504312
crash in Open Folder:
Last modified: 2007-12-18 22:36:11 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-07 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.23-perf #5 SMP PREEMPT Wed Dec 5 20:50:28 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 231505920 vsize: 231505920 resident: 48377856 share: 23351296 rss: 48377856 rss_rlim: 18446744073709551615 CPU usage: start_time: 1198005805 rtime: 702 utime: 629 stime: 73 cutime:0 cstime: 1 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 47848929514400 (LWP 18118)] 0x00002b84b0062b0f in waitpid () from /lib/libpthread.so.0
+ Trace 182268
Thread 1 (Thread 47848929514400 (LWP 18118))
----------- .xsession-errors --------------------- (Banshee:6143): Gtk-CRITICAL **: gtk_box_pack_start: assertion `child->parent == NULL' failed Debug: [12/18/2007 19:28:47] (Ripping CD and Encoding with Pipeline) - audioconvert ! vorbisenc quality=0.5 ! oggmux gnome-mount 0.4 ** (gnome-mount:18311): WARNING **: Unmount failed for /org/freedesktop/Hal/devices/volume_part_1_size_714387456: org.freedesktop.DBus.Error.UnknownMethod : Method "Unmount" with signature "as" on int ** (gnome-cd:18354): WARNING **: Generic IO error ** 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... warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffff5fe000 --------------------------------------------------
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 ***