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 640312 - Evolution: Evolution crashes someti...
Evolution: Evolution crashes someti...
Status: RESOLVED DUPLICATE of bug 330728
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.30.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-01-23 11:28 UTC by lanchardan
Modified: 2011-01-24 15:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30

Attachments
Crash report (94.10 KB, text/plain)
2011-01-24 13:18 UTC, lanchardan 		Details

Description lanchardan 2011-01-23 11:28:47 UTC 
Evolution crashes sometimes without any reason and without error messages. I cant find, where Evolution stores logs. How I can provide more information?


Distribution: openSUSE 11.3 (x86_64)
Gnome Release: 2.30.0 (null) (SUSE)
BugBuddy Version: 2.30.0
Comment 1 André Klapper 2011-01-23 15:56:40 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 lanchardan 2011-01-24 13:18:01 UTC 
Created attachment 179162 [details]
Crash report
Comment 3 lanchardan 2011-01-24 13:19:44 UTC 
Trace in attachment. But I dont sure its what i report. Now Evolution crashes when I switched to tasks tab and when I clicked Mail, its crashed.
Before I installed debug packets, Evolution crashes for 2 or 3 times without any interactions from my side. Will try to catch that now, with debug packets.
Comment 4 André Klapper 2011-01-24 15:52:08 UTC 
Thanks - that's the same trace as in bug 330728, hence marking as duplicate.

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