Bug 585280 - [abrt] crash in SalGraphics::CopyBits
[abrt] crash in SalGraphics::CopyBits
Status: CLOSED DUPLICATE of bug 695582
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-04-23 11:24 EDT by Brandon Gardner
Modified: 2011-04-17 17:46 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-28 09:53:52 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 (32.84 KB, text/plain)
2010-04-23 11:24 EDT, Brandon Gardner
no flags Details

  None (edit)
Description Brandon Gardner 2010-04-23 11:24:37 EDT
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/brandon.gardner/Link%20to%20My%20Documents/Unix%20Server%20Security%20Baseline%20012009.doc
component: openoffice.org
executable: /usr/lib64/openoffice.org3/program/swriter.bin
package: openoffice.org-writer-1:3.1.1-19.28.fc12
rating: 3
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Brandon Gardner 2010-04-23 11:24:39 EDT
Created attachment 408647 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-04-23 15:34:20 EDT
Is this reproducible ? e.g. opening and viewing a particular document. Its a pretty unusual looking crash.
Comment 3 Caolan McNamara 2010-04-28 09:53:52 EDT
If you know how to reproduce this, feel free to reopen it. I suspect something to do with the theme in use, but I can't reproduce it to be sure.
Comment 4 Caolan McNamara 2011-04-17 17:46:47 EDT

*** This bug has been marked as a duplicate of bug 695582 ***

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