GNOME Bugzilla – Bug 537549
crash in Open Folder: Open Samba Share.
Last modified: 2008-06-10 10:30:41 UTC
Version: 2.20.0 What were you doing when the application crashed? Open Samba Share. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Alphacube GTK 0.5 Icon Theme: OSX Memory status: size: 90431488 vsize: 90431488 resident: 28626944 share: 17494016 rss: 28626944 rss_rlim: 4294967295 CPU usage: start_time: 1213025044 rtime: 1049 utime: 746 stime: 303 cutime:568 cstime: 96 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6bbb720 (LWP 3704)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200008
Thread 1 (Thread 0xb6bbb720 (LWP 3704))
----------- .xsession-errors (4540 sec old) --------------------- (evolution:20614): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:20614): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:20614): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:20614): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:20614): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:20614): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:20614): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' 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 522534 ***