GNOME Bugzilla – Bug 355926
crash in Evolution: I was trying to display ...
Last modified: 2006-10-07 23:03:15 UTC
What were you doing when the application crashed? I was trying to display an image attached to an email. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 75427840 vsize: 0 resident: 293986304 share: 0 rss: 293986304 rss_rlim: 0 CPU usage: start_time: 8469 rtime: 0 utime: 1158217841 stime: 0 cutime:20124 cstime: 0 timeout: 18466 it_real_value: 0 frequency: 1658 Backtrace was generated from '/usr/bin/evolution-2.8' (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 805642464 (LWP 29271)] [New Thread 881128688 (LWP 2603)] [New Thread 948221168 (LWP 31616)] [New Thread 949490928 (LWP 31061)] [New Thread 939832560 (LWP 29292)] [New Thread 891286768 (LWP 29286)] [New Thread 872740080 (LWP 29284)] [New Thread 863937776 (LWP 29283)] [New Thread 855545072 (LWP 29281)] 0x0ea10220 in __waitpid_nocancel () from /lib/libc.so.6
+ Trace 72323
Thread 9 (Thread 855545072 (LWP 29281))
Thread 8 (Thread 863937776 (LWP 29283))
Thread 7 (Thread 872740080 (LWP 29284))
Thread 6 (Thread 891286768 (LWP 29286))
Thread 5 (Thread 939832560 (LWP 29292))
Thread 3 (Thread 948221168 (LWP 31616))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. For some yet unknown reason, such stacktraces are pretty common currently on certain distros. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Closing this bug report as no further information has been provided. Also, please feel free to report any further bugs you find. Thanks! [1] debugging packages for evolution and evolution-data-server, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions