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 363546 - crash in Evolution: Close an attachment 1 [details] of...
crash in Evolution: Close an attachment 1 of...
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-20 00:39 UTC by smartin
Modified: 2007-08-08 20:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description smartin 2006-10-20 00:39:47 UTC
What were you doing when the application crashed?
Close an attachment 1 [details] of 4 (all jpegs).


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

Memory status: size: 144490496 vsize: 0 resident: 144490496 share: 0 rss: 32927744 rss_rlim: 0
CPU usage: start_time: 1161299329 rtime: 0 utime: 2032 stime: 0 cutime:1748 cstime: 0 timeout: 284 it_real_value: 0 frequency: 320

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 -1232820560 (LWP 5454)]
[New Thread -1297089632 (LWP 5508)]
[New Thread -1286542432 (LWP 5488)]
[New Thread -1266476128 (LWP 5487)]
[New Thread -1286251616 (LWP 5477)]
[New Thread -1258046560 (LWP 5469)]
[New Thread -1249653856 (LWP 5465)]
(no debugging symbols found)
0xb7f84410 in ?? ()

Comment 1 ebbywiselyn 2006-10-20 05:55:25 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 ebbywiselyn 2006-10-20 05:56:15 UTC
sorry

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 3 Karsten Bräckelmann 2006-10-20 09:37:34 UTC
What's the exact Evolution Ubuntu package version?


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 4 smartin 2006-10-20 12:15:28 UTC
Hi,

Thanks for the response. The package is evolution-2.8.1-0ubuntu4. I installed the debug symbols and tried to reproduce this error, unfortunately it didn't fail.

The only real difference between last night when the error occurred and today is that I was using a remote (LAN) XWin session, and today I am using the local X connection. I just installed the latest software updates for edgy and gnome-settings-daemon seems to crash when I connect via XWin. When I have sorted this out I'll try again.

If I manage to reproduce this, I will add the requested data.

TIA

Simon Martin.
Comment 5 Karsten Bräckelmann 2006-10-20 14:23:55 UTC
Since you just updated... What's the exact Evolution Ubuntu package version *before* this update, at the time of the crash?

Thanks for installing debugging packages and trying. Much appreciated. :)
Comment 6 smartin 2006-10-20 15:04:41 UTC
Hi,

Evolution did not upgrade today, so the version is correct.
Comment 7 Karsten Bräckelmann 2006-10-27 19:57:46 UTC
Simon, 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 ***
Comment 8 smartin 2006-11-06 12:31:48 UTC
Hi,

I've just managed to reproduce this. I also have a method to make it happen!

I received 3 large mails (about 3 MB each) with 5-6 JPEG pictures (I can forward them to you if you need it). I just go down the list of JPEGs viewing them in line. Sometimes I have to check 2 mails like this, but of the 4 times I have done this, Evolution has crashed 4 times.

I do not include the bug buddy stack trace because despite having installed the debug symbols, the stack trace still comes up with very few tags.

Let me know if I can help in any other way.

TIA

Simon Martin
Comment 9 Karsten Bräckelmann 2007-08-08 20:25:37 UTC
So this still is the same issue as bug 333864...


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