GNOME Bugzilla – Bug 522992
crash in Document Viewer:
Last modified: 2008-03-18 12:03:18 UTC
Version: 2.20.2 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.18-5-amd64 #1 SMP Thu Aug 30 01:14:54 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 696057856 vsize: 696057856 resident: 451239936 share: 14458880 rss: 451239936 rss_rlim: 18446744073709551615 CPU usage: start_time: 1205758247 rtime: 11090 utime: 9413 stime: 1677 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (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 0x2b89fb8d6760 (LWP 22517)] [New Thread 0x40800950 (LWP 22518)] (no debugging symbols found) 0x00002b89f66cf34f in waitpid () from /lib/libpthread.so.0
+ Trace 192698
Thread 1 (Thread 0x2b89fb8d6760 (LWP 22517))
----------- .xsession-errors (25354 sec old) --------------------- (evolution:3801): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:3801): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:3801): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:3801): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:3801): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:3801): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:3801): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 316907 ***