After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358594 - crash in Evolution: Opening an inline image ...
crash in Evolution: Opening an inline image ...
Status: RESOLVED DUPLICATE of bug 351374
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-30 19:08 UTC by paulojjs
Modified: 2006-09-30 20:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
Backtrace with debugging symbols (17.16 KB, application/x-bzip)
2006-09-30 20:15 UTC, paulojjs 		Details

Description paulojjs 2006-09-30 19:08:21 UTC 
What were you doing when the application crashed?
Opening an inline image attached with an email.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 140980224 vsize: 0 resident: 140980224 share: 0 rss: 37326848 rss_rlim: 0
CPU usage: start_time: 1159642832 rtime: 0 utime: 1873 stime: 0 cutime:1724 cstime: 0 timeout: 149 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233389904 (LWP 6542)]
[New Thread -1311294560 (LWP 6594)]
[New Thread -1289749600 (LWP 6559)]
[New Thread -1279312992 (LWP 6554)]
[New Thread -1270920288 (LWP 6553)]
[New Thread -1262527584 (LWP 6552)]
[New Thread -1252942944 (LWP 6551)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 73780







Comment 1


Elijah Newren





          2006-09-30 19:09:36 UTC
        



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.  Also, could you attach the email that causes this crash to this bug?






Comment 2


paulojjs





          2006-09-30 20:15:11 UTC
        



Created attachment 73712 [details]
Backtrace with debugging symbols






Comment 3


paulojjs





          2006-09-30 20:17:20 UTC
        



I've attached a backtrace after installing evolution and some other packages with debugging symbols.

Please note that this could be a problem in my distribution (Ubuntu Edgy) since it isn't a final release.






Comment 4


Elijah Newren





          2006-09-30 20:22:54 UTC
        



Thanks for the extra info.  The stack trace matches the ones in bug 355188 and bug 358333, both of which have been marked as duplicates of bug 351374

*** This bug has been marked as a duplicate of 351374 ***