Bug 172431

Summary:	Impress crashes when changing view
Product:	[Fedora] Fedora	Reporter:	Ingo Schaefer <ingo>
Component:	openoffice.org	Assignee:	Caolan McNamara <caolanm>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	4
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-11-08 12:05:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ingo Schaefer 2005-11-04 11:35:45 UTC

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):
openoffice.org-impress-2.0.0-3.2.1

How reproducible:
Always

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 12:24:45 UTC

can you attach the offending presentation, or send it to me if too large to attach

Comment 2 Caolan McNamara 2005-11-04 15:53:56 UTC

reproducable, an XError is being thrown, try

> export SAL_IGNOREXERRORS=true
> ooimpress troubledocument.sxi

and see if it worksaround for you

Comment 3 Ingo Schaefer 2005-11-04 16:26:02 UTC

Thank you, Caolan - this worked around this.

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