Bug 574636 - [abrt] crash in openoffice.org-writer-1:3.1.1-19.26.fc12: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in openoffice.org-writer-1:3.1.1-19.26.fc12: Process /usr/lib/op...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2b16541adfd7d4bd62f83b0de00...
: 576682 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-18 02:11 UTC by robert fairb
Modified: 2010-03-25 16:12 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-25 06:45:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (45.76 KB, text/plain)
2010-03-18 02:11 UTC, robert fairb
no flags Details

Description robert fairb 2010-03-18 02:11:29 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
comment: i dont really remember what i was doing at the time
component: openoffice.org
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.32.9-70.fc12.i686
package: openoffice.org-writer-1:3.1.1-19.26.fc12
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.i just suspended my computer
2.
3.

Comment 1 robert fairb 2010-03-18 02:11:31 UTC
Created attachment 400936 [details]
File: backtrace

Comment 2 David Tardon 2010-03-18 12:50:34 UTC
I suppose it's not reproducible, is it? I tried to suspend my machine several times while various OO.o apps were running and got no crash. And just to be sure: do we speak about suspend or hibernate?

Comment 3 David Tardon 2010-03-25 06:45:33 UTC
I cannot reproduce this crash. Feel free to reopen if you can supply us with additional informations.

Comment 4 David Tardon 2010-03-25 13:10:48 UTC
*** Bug 576682 has been marked as a duplicate of this bug. ***

Comment 5 David Tardon 2010-03-25 13:11:56 UTC
dtardon->jyoerger: What were you doing when it crashed? Can you reproduce the crash?

Comment 6 jyoerger 2010-03-25 16:12:04 UTC
I actually found this alert languishing below a bunch of kernel crashes in abrt. It had apparently been there awhile and I can't recollect what I was doing at the time. I have thus far been unable to reproduce it but I'll certainly post it if and when I do.


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