GNOME Bugzilla – Bug 540358
crash in Open Folder: opening a folder in the ...
Last modified: 2008-06-26 21:32:59 UTC
Version: 2.20.0 What were you doing when the application crashed? opening a folder in the filebrowser Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.18-6-powerpc #1 Thu May 8 07:21:23 UTC 2008 ppc X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crystal-Green Memory status: size: 113926144 vsize: 113926144 resident: 27807744 share: 16502784 rss: 27807744 rss_rlim: 4294967295 CPU usage: start_time: 1214333952 rtime: 44770 utime: 39211 stime: 5559 cutime:61777 cstime: 49762 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x30055bd0 (LWP 5269)] [New Thread 0x329c5470 (LWP 21961)] 0x0ec51290 in waitpid () from /lib/libpthread.so.0
+ Trace 201466
Thread 1 (Thread 0x30055bd0 (LWP 5269))
----------- .xsession-errors (83400 sec old) --------------------- (evolution:14898): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:14898): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:14898): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:14898): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:14898): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:14898): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed (evolution:14898): evolution-shell-CRITICAL **: e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed ...Too much output, ignoring rest... --------------------------------------------------
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 512040 ***