Bug 568387

Summary: [abrt] crash in orage-4.6.1-1.fc12: Process /usr/bin/orage was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: WaRL <leontjevski>
Component: orageAssignee: Kevin Fenzi <kevin>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:4aad90a254a5be6ad67bf325475721cdf02e9e90
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-04 19:24:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description WaRL 2010-02-25 15:49:01 UTC 
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: orage
component: orage
executable: /usr/bin/orage
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: orage-4.6.1-1.fc12
rating: 4
reason: Process /usr/bin/orage was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 WaRL 2010-02-25 15:49:05 UTC 
Created attachment 396307 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-02-28 05:46:40 UTC 
What were you doing when this crash happened? Can you duplicate it?

Is there anything out of the ordinary about your Orage setup? 

It looks like it may have been unarchiving an ical file?
"xfical_unarchive: archive file open error"
Comment 3 Kevin Fenzi 2010-03-21 02:48:10 UTC 
WaRL: Are you there? 

I will close this out in 1 week if I don't hear anything back.
Comment 4 Kevin Fenzi 2010-07-04 19:24:56 UTC 
Greetings.

This bug has been waiting for info for several months.
I am going to go ahead and close it now.

If you are able to provide information that will help me
track this issue down, please feel free to open a new bug
or just re-open this one with the new information.

Thanks for reporting this!