Bug 1108977 - Evolution segfaults on startup
Summary: Evolution segfaults on startup
Keywords:
Status: CLOSED DUPLICATE of bug 1083306
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-13 03:42 UTC by Aaron Luchko
Modified: 2014-06-13 09:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:51:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
GDB backtrace (8.22 KB, text/plain)
2014-06-13 03:45 UTC, Aaron Luchko
no flags Details

Description Aaron Luchko 2014-06-13 03:42:40 UTC
Description of problem:
After an upgrade from FC18 starting evolution will result in a segmentation fault every time. In case a botched upgrade was the issue I reinstalled all the dependencies but that did not change anything
yum reinstall $(repoquery --requires --recursive --resolve evolution)

Although the main app never starts the evolution-source-registry, evolution-alarm-notify, and evolution-calendar-factory processes are left running

Version-Release number of selected component (if applicable):
evolution-3.10.4-2.fc20.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Start evolution

Expected results:
It starts

Actual results:
An earth shattering KABOOM

Additional info:
Post-upgrade skype also crashes on startup, this may or may not be related.

Comment 1 Aaron Luchko 2014-06-13 03:45:40 UTC
Created attachment 908371 [details]
GDB backtrace

Comment 2 Milan Crha 2014-06-13 09:51:45 UTC
Thanks for a bug report. This is crashing due to some of web-browser plugin(s). Please see bug 1083306, maybe you have also installed the mozplugger, which is causing trouble (according to backtrace, the problem is with something handling applciation/photoshot mime type, if I read it correctly).

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


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