Bug 568387 - [abrt] crash in orage-4.6.1-1.fc12: Process /usr/bin/orage was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in orage-4.6.1-1.fc12: Process /usr/bin/orage was killed by sign...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: orage
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4aad90a254a5be6ad67bf325475...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-25 15:49 UTC by WaRL
Modified: 2010-07-04 19:24 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-07-04 19:24:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (18.46 KB, text/plain)
2010-02-25 15:49 UTC, WaRL 		no flags Details
View All

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!
Note You need to log in before you can comment on or make changes to this bug.