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 364595 - crash in Evolution: checking email
crash in Evolution: checking email
Status: RESOLVED DUPLICATE of bug 364700
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-24 01:33 UTC by nickbeason
Modified: 2007-09-26 18:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description nickbeason 2006-10-24 01:33:10 UTC
What were you doing when the application crashed?
checking email


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

Memory status: size: 109842432 vsize: 0 resident: 109842432 share: 0 rss: 28241920 rss_rlim: 0
CPU usage: start_time: 1161653321 rtime: 0 utime: 403 stime: 0 cutime:377 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 -1232734544 (LWP 5059)]
[New Thread -1305482336 (LWP 5150)]
[New Thread -1285678176 (LWP 5086)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Comment 1 Karsten Bräckelmann 2006-10-24 14:15: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!
Comment 2 Karsten Bräckelmann 2006-10-31 20:51:15 UTC
Unfortunately the stacktrace does not have any hints about the real cause of
the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on
certain distros. However, almost all of them do turn out to be filed already,
once we managed to gather a useful stacktrace. To do so, simply install the
corresponding debugging packages and reproduce the issue, if possible. The
resulting stacktrace (see bug-buddy details) will help us to identify and fix
the issue.


Just in case you ever can reproduce this crash later, please consider
installing debugging packages [1] and either reopen this bug report or simply
file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.


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
Comment 3 Tobias Mueller 2007-09-26 18:00:34 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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