Bug 245235 - OpenOffice.org crashes at inopportune times
OpenOffice.org crashes at inopportune times
Status: CLOSED DUPLICATE of bug 243811
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-06-21 15:54 EDT by Jonathan Corbet
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-21 16:51:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Corbet 2007-06-21 15:54:50 EDT
Description of problem:

OpenOffice.org will crash at seemingly random times - usually when it can manage
to lose the most unsaved work.  This happens with the writer component, not sure
if the others are equally vulnerable.

Version-Release number of selected component (if applicable):


How reproducible:

Very - just use the tool for long enough and it will happen.  It is worth noting
that, once a crash has happened, an attempt to recover the file will *always*
cause another crash.  The only way to get a semi-working ooffice running is to
"cancel" the recovery.

Steps to Reproduce:
1. Start openoffice.org
2. Type some important stuff from inspiration which will never come again and
which you cannot possibly afford to lose.
3. Stare in horror as the openoffice window vanishes.
Actual results:

Crash.  Lost work.  High blood pressure.

Oh, also, it prints:

X-Error: RenderBadPicture (invalid Picture parameter)
        Major opcode: 155
        Minor opcode: 7
        Resource ID:  0x280090f
        Serial No:    35321 (35321)

Expected results:

No more buggy than usual.

Additional info:

This is on current x86-64 rawhide as of 6/21.
Comment 1 Caolan McNamara 2007-06-21 16:51:38 EDT

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

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