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 359823 - crash in Evolution: checking different mail ...
crash in Evolution: checking different mail ...
Status: RESOLVED DUPLICATE of bug 360097
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-05 08:41 UTC by marco
Modified: 2006-10-06 20:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description marco 2006-10-05 08:41:30 UTC 
What were you doing when the application crashed?
checking different mail folders on evolution


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

Memory status: size: 120119296 vsize: 0 resident: 120119296 share: 0 rss: 32251904 rss_rlim: 0
CPU usage: start_time: 1160037458 rtime: 0 utime: 1689 stime: 0 cutime:1596 cstime: 0 timeout: 93 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 -1232517456 (LWP 5936)]
[New Thread -1301181536 (LWP 6066)]
[New Thread -1298928736 (LWP 6004)]
[New Thread -1290536032 (LWP 6002)]
[New Thread -1280463968 (LWP 5946)]
[New Thread -1272071264 (LWP 5943)]
[New Thread -1251271776 (LWP 5939)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74641







Comment 1


Elijah Newren





          2006-10-05 10:41:31 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


Elijah Newren





          2006-10-06 20:51:03 UTC
        



User has submitted more stack traces without getting debugging information, so I'll mark this as a duplicate of one of the other ones.

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