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 362800 - crash in Evolution: Rolling up an expanded j...
crash in Evolution: Rolling up an expanded j...
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-17 07:59 UTC by alexphillips
Modified: 2006-10-24 14:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description alexphillips 2006-10-17 07:59:04 UTC 
What were you doing when the application crashed?
Rolling up an expanded jpeg attachment viewed inside an email.


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

Memory status: size: 112611328 vsize: 0 resident: 112611328 share: 0 rss: 32985088 rss_rlim: 0
CPU usage: start_time: 1161071761 rtime: 0 utime: 570 stime: 0 cutime:544 cstime: 0 timeout: 26 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 -1233307984 (LWP 6214)]
[New Thread -1299080288 (LWP 6230)]
[New Thread -1290687584 (LWP 6227)]
[New Thread -1268479072 (LWP 6226)]
[New Thread -1259689056 (LWP 6221)]
[New Thread -1251259488 (LWP 6219)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76748







Comment 1


Karsten Bräckelmann





          2006-10-17 08:56:51 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


Karsten Bräckelmann





          2006-10-24 14:53:42 UTC
        



Alex, 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 ***