Bug 245235 - OpenOffice.org crashes at inopportune times
Summary: OpenOffice.org crashes at inopportune times
Keywords:
Status: CLOSED DUPLICATE of bug 243811
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: rawhide
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-21 19:54 UTC by Jonathan Corbet
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-21 20:51:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Corbet 2007-06-21 19:54:50 UTC
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):

openoffice.org-writer-2.2.1-18.3.fc8

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 20:51:38 UTC

*** 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.