Bug 172431 - Impress crashes when changing view
Impress crashes when changing view
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Caolan McNamara
Depends On:
  Show dependency treegraph
Reported: 2005-11-04 06:35 EST by Ingo Schaefer
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-08 07:05:58 EST
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 Ingo Schaefer 2005-11-04 06:35:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
I have one big presentation (8MB), if I open it in OOo and select the Button "Foliensortierung" (Slide Sorter in English versions), it crashes down.

Started in gdb shows, that it exited with code 0116

I've installed the debuginfo package, but can't get stacktrace from it.
(Any help to get stacktrace is very welcome.)

This error was there in the 1.9.125 version, too - but it did not always crash. Version 2.0 crashed every time (today).

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

How reproducible:

Steps to Reproduce:
1. Open OOo Impress
2. Load this particular presentation (8 MB)
3. Klick on "Slide Sorter"

Additional info:
Comment 1 Caolan McNamara 2005-11-04 07:24:45 EST
can you attach the offending presentation, or send it to me if too large to attach
Comment 2 Caolan McNamara 2005-11-04 10:53:56 EST
reproducable, an XError is being thrown, try

> ooimpress troubledocument.sxi

and see if it worksaround for you
Comment 3 Ingo Schaefer 2005-11-04 11:26:02 EST
Thank you, Caolan - this worked around this.

FYI: OpenOffice.org 2.0 on Win32 seems not affected (or ignores these errors

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