GNOME Bugzilla – Bug 386778
crash in Evolution: trying to get my mail
Last modified: 2007-09-09 17:55:02 UTC
What were you doing when the application crashed? trying to get my mail Distribution: openSUSE 10.2 (X86-64) Gnome Release: 2.16.1 2006-11-28 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 467927040 vsize: 467927040 resident: 8765440 share: 19701760 rss: 28467200 rss_rlim: 894684160 CPU usage: start_time: 1166447205 rtime: 134 utime: 126 stime: 8 cutime:21 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47768854633680 (LWP 7173)] [New Thread 1107577152 (LWP 7186)] [New Thread 1098918208 (LWP 7185)] [New Thread 1099184448 (LWP 7184)] [New Thread 1090525504 (LWP 7182)] [New Thread 1082132800 (LWP 7179)] (no debugging symbols found) 0x00002b720b270c5f in waitpid () from /lib64/libpthread.so.0
+ Trace 94837
Thread 1 (Thread 47768854633680 (LWP 7173))
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 334966 ***
*** Bug 388409 has been marked as a duplicate of this bug. ***
*** Bug 387266 has been marked as a duplicate of this bug. ***
*** Bug 388907 has been marked as a duplicate of this bug. ***
*** Bug 389523 has been marked as a duplicate of this bug. ***
*** Bug 404238 has been marked as a duplicate of this bug. ***
*** Bug 413334 has been marked as a duplicate of this bug. ***
*** Bug 413381 has been marked as a duplicate of this bug. ***
*** Bug 413829 has been marked as a duplicate of this bug. ***
*** Bug 414153 has been marked as a duplicate of this bug. ***
*** Bug 443671 has been marked as a duplicate of this bug. ***
*** Bug 474833 has been marked as a duplicate of this bug. ***
*** Bug 474894 has been marked as a duplicate of this bug. ***