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 355029 - crash in Evolution: clicking on attached jpg...
crash in Evolution: clicking on attached jpg...
Status: RESOLVED DUPLICATE of bug 355028
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-08 23:10 UTC by bob
Modified: 2006-09-11 05:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description bob 2006-09-08 23:10:55 UTC
What were you doing when the application crashed?
clicking on attached jpg attachment to view


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

Memory status: size: 113618944 vsize: 0 resident: 113618944 share: 0 rss: 27361280 rss_rlim: 0
CPU usage: start_time: 1157757014 rtime: 0 utime: 613 stime: 0 cutime:570 cstime: 0 timeout: 43 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 -1232247120 (LWP 7588)]
[New Thread -1312060512 (LWP 7604)]
[New Thread -1303258208 (LWP 7602)]
[New Thread -1294865504 (LWP 7601)]
[New Thread -1286472800 (LWP 7598)]
[New Thread -1266402400 (LWP 7597)]
[New Thread -1257612384 (LWP 7594)]
[New Thread -1249182816 (LWP 7592)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 Poornima 2006-09-11 05:54:09 UTC
Thanks for taking the time to report this bug. 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.
Comment 2 Poornima 2006-09-11 05:55:44 UTC

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