Bug 708606 - Evolution crashes on Fedora 15 when switching to calendar
Summary: Evolution crashes on Fedora 15 when switching to calendar
Keywords:
Status: CLOSED DUPLICATE of bug 704089
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 15
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL: http://forums.fedoraforum.org/showthr...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-28 10:27 UTC by Uri Barkan
Modified: 2011-05-31 06:17 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-05-31 04:16:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
ABRT report of the crash (123.31 KB, text/plain)
2011-05-28 10:29 UTC, Uri Barkan
no flags Details
backtrace of the crash (26.34 KB, text/plain)
2011-05-30 20:25 UTC, Uri Barkan
no flags Details

Description Uri Barkan 2011-05-28 10:27:11 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

I updated from F14 to F15 a few days ago. On F14 I didn't have evolution installed. I decided to give it a try with F15. I installed it with yum (yum install evolution), configured my email account, and used it once. When I clicked on the calendar button, Evolution crashed.

Reproducible: Always

Steps to Reproduce:
1.Install Fedora 15.
2.Remove Evolution.
3.Install Evolution.
4.Launch Evolution.
5. Switch to Calendar.
Actual Results:  
Evolution crashes.

Expected Results:  
Evolution should have switched to Calendar view.

See the thread I opened in Fedora forum:
http://forums.fedoraforum.org/showthread.php?t=263735

Comment 1 Uri Barkan 2011-05-28 10:29:16 UTC
Created attachment 501459 [details]
ABRT report of the crash

Comment 2 Uri Barkan 2011-05-30 20:25:50 UTC
Created attachment 501881 [details]
backtrace of the crash

Attaching also the backtrace of the crash.

Comment 3 Matthew Barnes 2011-05-30 20:41:10 UTC
Turn off accessibility features and the crash should go away.

Comment 4 Uri Barkan 2011-05-30 21:11:42 UTC
How do I turn off accessibility features in gnome 3? When I click the accessibility icon on the top panel, all features are set to off. Is that enough?

Comment 5 Milan Crha 2011-05-31 04:16:52 UTC
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

With respect of turning off accessibility, I'm not sure, but I would try to run gnome-session-properties and turn off services like AT SPI and Orca, if enabled. And then restart the machine.

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

Comment 6 Uri Barkan 2011-05-31 06:00:07 UTC
Are you sure it's a duplicate? The path leads to bug 649400 which describes a crash when trying to send an email. Mine occurs when switching to calendar view.

I disabled AT SPI and ORCA in my start up list, but I still get the accessibility icon in the top panel with its menu, and evolution still crashes. A workaround will be highly appreciated, as the bug in Gnome bugzilla (#330728) is open from 2006, and using Fedora (or any other OS for that matter) without a proper Email client is not an appealing idea.

Comment 7 Milan Crha 2011-05-31 06:17:38 UTC
(In reply to comment #6)
> Are you sure it's a duplicate? The path leads to bug 649400 which describes a
> crash when trying to send an email. Mine occurs when switching to calendar
> view.

Yes, it's a common code used on a custom widget which is reused in all views of evolution.

> I disabled AT SPI and ORCA in my start up list, but I still get the
> accessibility icon in the top panel with its menu, and evolution still crashes.
> A workaround will be highly appreciated, as the bug in Gnome bugzilla (#330728)
> is open from 2006, and using Fedora (or any other OS for that matter) without a
> proper Email client is not an appealing idea.

Hrm, I do not know why they hid it. And I'm unfortunately not aware of anything else. This might be a question for gtk3 or gnome-shell developers.


Note You need to log in before you can comment on or make changes to this bug.