Bug 679950 - Crash on Launch
Summary: Crash on Launch
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 15
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: 2011-02-23 22:59 UTC by David Le Sage
Modified: 2011-02-24 07:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-24 07:12:08 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Le Sage 2011-02-23 22:59:15 UTC 
Description of problem:
Evolution crashed on launch.

Version-Release number of selected component (if applicable):
Fedora 15 Live CD Nightly Build 23/2/2011 (http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/)

How reproducible:
Only happened once.

Steps to Reproduce:
1. Boot the live CD and Log into the GNOME Shell.
2. Go into the overlay's Applications tab and launch Evolution.
3. The warning that it is not production ready appears as the first screen of the wizard. 
4. Click to go forward to next screen of wizard.
  
Actual results:
Crashes.

Expected results:
Should guide user through wizard to configure Evolution.

Additional info:
It generated a SYSEGV error in abrt but I could not produce a report from this as I was only running from the Live CD.  I then tried to reproduce the bug by launching Evolution again but the problem did not occur the second time.
Comment 1 David Le Sage 2011-02-24 04:54:55 UTC 
I tried this again later in the day and I was not able to reproduce it, even though the environment was obviously the same, being the live CD...
Comment 2 Milan Crha 2011-02-24 07:12:08 UTC 
Thanks for a bug report. Without a reproducer, and at least backtrace (with debug info packages installed), there is not much we can do, I'm sorry.
Note You need to log in before you can comment on or make changes to this bug.