GNOME Bugzilla – Bug 362435
crash in Evolution: Schließen einer eingebet...
Last modified: 2006-10-22 17:32:42 UTC
What were you doing when the application crashed? Schließen einer eingebettete Anzeige einer JPEG-Anlage in einer E-Mail-Nachricht führte zu Absturz. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 397213696 vsize: 397213696 resident: 83996672 share: 19968000 rss: 83996672 rss_rlim: -1 CPU usage: start_time: 1160937818 rtime: 1680 utime: 1536 stime: 144 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 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 47891744898368 (LWP 4942)] [New Thread 1115969872 (LWP 4982)] [New Thread 1115703632 (LWP 4961)] [New Thread 1107310928 (LWP 4960)] [New Thread 1098918224 (LWP 4953)] [New Thread 1090525520 (LWP 4949)] [New Thread 1082132816 (LWP 4948)] (no debugging symbols found) 0x00002b8ea62525cf in waitpid () from /lib/libc.so.6
+ Trace 76499
Thread 7 (Thread 1082132816 (LWP 4948))
Thread 6 (Thread 1090525520 (LWP 4949))
Thread 5 (Thread 1098918224 (LWP 4953))
Thread 4 (Thread 1107310928 (LWP 4960))
Thread 3 (Thread 1115703632 (LWP 4961))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Translation of the description: Crash closing an attached JPEG image.
According to the description, this is the very same issue as bug 333864. The crash has been fixed in Evolution 2.8.1.1. *** This bug has been marked as a duplicate of 333864 ***