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 653059 - Crashes on entering calendar/tasks views
Crashes on entering calendar/tasks views
Status: RESOLVED DUPLICATE of bug 643526
Product: evolution
Classification: Applications
Component: Calendar
3.0.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-06-20 22:40 UTC by Charles
Modified: 2011-08-24 11:50 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Trace (902 bytes, text/x-log)
2011-06-21 22:41 UTC, Charles 		Details

Description Charles 2011-06-20 22:40:09 UTC 
Steps to Reproduce:
1) Install evolution
2) Configure for a primary e-mail account (used gmail)
3) Look at the mail being fetched normaly
4) Switch to the calendar or the task view 

Actual Results:
CRASH

Expected Results:
Have an empty calendar as it is the first time I run evolution on this computer

Build Date & Platform:
May 23, 2011, 5:43 p.m. UTC on Arch Linux 64bits
Comment 1 André Klapper 2011-06-21 13:17:30 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 Charles 2011-06-21 22:41:59 UTC 
Created attachment 190399 [details]
Trace

GDB Debug trace
Comment 3 Charles 2011-06-21 22:50:33 UTC 
Sorry, I've added the trace now.

When running it with gdb, it is the memo page wich showed up as it is the last one I've tried it with. Let me know if you think it would be relevant to have a trace with a different state as task or calendar.


(In reply to comment #1)
> 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 4 Milan Crha 2011-08-24 11:50:52 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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