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 363881 - crash in Evolution: opening a jpeg attachmen...
crash in Evolution: opening a jpeg attachmen...
Status: RESOLVED DUPLICATE of bug 333864
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-10-21 10:22 UTC by lisa.ayotte
Modified: 2006-10-28 18:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lisa.ayotte 2006-10-21 10:22:50 UTC 
What were you doing when the application crashed?
opening a jpeg attachment


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

Memory status: size: 130064384 vsize: 0 resident: 130064384 share: 0 rss: 36028416 rss_rlim: 0
CPU usage: start_time: 1161425952 rtime: 0 utime: 784 stime: 0 cutime:724 cstime: 0 timeout: 60 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 -1209997648 (LWP 9851)]
[New Thread -1281360992 (LWP 9887)]
[New Thread -1279956064 (LWP 9886)]
[New Thread -1269421152 (LWP 9876)]
[New Thread -1246217312 (LWP 9870)]
[New Thread -1237693536 (LWP 9868)]
[New Thread -1229263968 (LWP 9864)]
(no debugging symbols found)
0xb7f7e410 in __kernel_vsyscall ()

+ Trace 77455







Comment 1


Karsten Bräckelmann





          2006-10-21 15:59:55 UTC
        



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







Comment 2


Karsten Bräckelmann





          2006-10-28 18:45:14 UTC
        



Lisa, unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue.

However, according to the description this is the same issue as bug 333864,
which is fixed in Evolution 2.8.1.1.


Just in case you can reproduce this crash later, please consider installing
debugging packages [1], which help a lot in tracking down the crash.  Thanks!

Also, please feel free to report any further bugs you find.  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


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