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 373437 - crash in Evolution: Viewing a jpeg attachmen...
crash in Evolution: Viewing a jpeg attachmen...
Status: RESOLVED DUPLICATE of bug 340165
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-11-10 16:01 UTC by mpitman
Modified: 2006-11-10 19:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description mpitman 2006-11-10 16:01:13 UTC
What were you doing when the application crashed?
Viewing a jpeg attachment in email


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 263745536 vsize: 0 resident: 263745536 share: 0 rss: 44793856 rss_rlim: 0
CPU usage: start_time: 1163171610 rtime: 0 utime: 14456 stime: 0 cutime:13698 cstime: 0 timeout: 758 it_real_value: 0 frequency: 1

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 -1232484688 (LWP 15232)]
[New Thread -1377838176 (LWP 15376)]
[New Thread -1369445472 (LWP 15375)]
[New Thread -1361052768 (LWP 15374)]
[New Thread -1297720416 (LWP 15373)]
[New Thread -1348490336 (LWP 15247)]
[New Thread -1339700320 (LWP 15244)]
[New Thread -1289327712 (LWP 15239)]
[New Thread -1280214112 (LWP 15238)]
[New Thread -1271198816 (LWP 15237)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Comment 1 Diego Escalante Urrelo (not reading bugmail) 2006-11-10 19:29:48 UTC
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 340165 ***