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 364591 - crash in Evolution: trying to download my PO...
crash in Evolution: trying to download my PO...
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 00:53 UTC by kd7avw
Modified: 2007-09-26 18:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description kd7avw 2006-10-24 00:53:26 UTC
What were you doing when the application crashed?
trying to download my POP email


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

Memory status: size: 112619520 vsize: 0 resident: 112619520 share: 0 rss: 25952256 rss_rlim: 0
CPU usage: start_time: 1161651246 rtime: 0 utime: 156 stime: 0 cutime:146 cstime: 0 timeout: 10 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 -1233103184 (LWP 6073)]
[New Thread -1284486240 (LWP 6087)]
[New Thread -1276093536 (LWP 6086)]
[New Thread -1251796064 (LWP 6083)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Comment 1 Karsten Bräckelmann 2006-10-24 14:15:12 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:13 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:01:19 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 ***