Bug 612223 - [abrt] crash in openoffice.org-writer-1:3.2.0-12.25.fc13: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
[abrt] crash in openoffice.org-writer-1:3.2.0-12.25.fc13: Process /usr/lib64/...
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-07 11:40 EDT by Maxim Bagrov
Modified: 2010-07-19 11:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-19 11:22:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (82.93 KB, text/plain)
2010-07-07 11:41 EDT, Maxim Bagrov
no flags Details

  None (edit)
Description Maxim Bagrov 2010-07-07 11:40:16 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/max/%D0%A0%D0%B0%D0%B1%D0%BE%D1%87%D0%B8%D0%B9%20%D1%81%D1%82%D0%BE%D0%BB/%D0%BF/%D0%9C%D0%B0%D0%B9%202010.doc
component: openoffice.org
crash_function: framework::LayoutManager::implts_showProgressBar
executable: /usr/lib64/openoffice.org3/program/swriter.bin
global_uuid: 0c40c41f42d8cadb82f24034583f6245702ecbbd
package: openoffice.org-writer-1:3.2.0-12.25.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Maxim Bagrov 2010-07-07 11:41:06 EDT
Created attachment 430096 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-07-07 12:13:38 EDT
This suggests that you opened a .doc and it crashed in showing the progress bar. I think there was a report like this before but we couldn't reproduce it. Showing the progress bar on document loading is a fairly common thing, to say the least, so this is a weird bug.

Can you reproduce this ?, does it always happen on opening a specific .doc, or did it just happen the once and never again ?
Comment 3 Caolan McNamara 2010-07-19 11:22:22 EDT
Very odd, can't reproduce it, just looks like drawing a progress bar on loading a .doc. which isn't a particularly uncommon thing. Giving up on this one :-(

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