OpenGL (Compiz or 3D transitions) cause OpenOffice impress slide show to crach if displayed on a second screen

Bug #238593 reported by Florian Wiesweg
4
Affects Status Importance Assigned to Milestone
OpenOffice
Invalid
Unknown
openoffice.org (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org-impress

Ubuntu 8.04 Hardy Heron Desktop
OpenOffice 2.4.0-3ubuntu6

If I start a presentation using OpenOffice.org Impress' feature of displaying the slide show on another screen (e.g. if the window is on X screen 1 and the presentation should be displayed on screen 2) any use of OpenGL (either Compiz on that screen or the 3D transitions from package openoffice.org-ogltrans) makes OpenOffice crash and exit with the following error:

X-Error: BadMatch (invalid parameter attributes)
 Major opcode: 128
 Minor opcode: 5
 Resource ID: 0x4a01566
 Serial No: 29576 (29576)
These errors are reported asynchronously,
set environment variable SAL_SYNCHRONIZE to 1 to help debugging

I'm running an NVidia 8600M GS with the nvdia binary driver, if helpful.

ProblemType: Bug
Architecture: i386
Date: Mon Jun 9 17:35:10 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
Package: openoffice.org-core 1:2.4.0-3ubuntu6
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: openoffice.org
Uname: Linux 2.6.24-18-generic i686

Revision history for this message
Florian Wiesweg (flow) wrote :
Revision history for this message
Florian Wiesweg (flow) wrote :

just realized: even opening a normal context menu managed by metacity is enough to kill the app

Revision history for this message
Florian Wiesweg (flow) wrote :

This is for OpenOffice.org 3 Beta, same problem.

Chris Cheney (ccheney)
Changed in openoffice.org:
status: New → Triaged
Revision history for this message
Mark Waite (markwaite) wrote :

It seems like there might be some relationship between some of the conditions around this bug and bug 430449 submitted to the OpenSUSE team that maintains their branch of OpenOffice (see https://bugzilla.novell.com/show_bug.cgi?id=430449). There is a stack trace attached to that bug report which might be useful to compare with the base bug report.

The OpenSUSE bug report was also seen when using Vista, but was not seen when using Windows XP. Thorsten Behrens described the issue as a 3d transition apparently not being initialized properly, and the "Random Transition" crashed because of it.

The Vista failure is also reported to the OpenOffice.org team as bug 94389 *http://www.openoffice.org/issues/show_bug.cgi?id=94389).

Thorsten and Radek committed a change to the OpenSUSE code which is intended to fix issue 430449 on their system. They didn't say if their fix was being pushed back to the OpenOffice team, or if it would remain forever on only the OpenSUSE code line.

My failure case was using an OpenSUSE 11.0 machine with the open source video drivers over an NVidia GEForce4 440 Go. The computer has 512 MB of memory and is relatively slow.

When I wanted to test dual head mode, I had to install the NVidia binary driver. Once I installed that binary driver, my crash stopped happening. I ran in multiple different configurations with multiple tests (multi-head, and Xinerama) and saw no failures in all my test runs.

I also saw the same failure on an OpenSUSE 11.0 computer at work with a different video card and 1 GB of memory. It might be worth your while to check with Thorsten to see if he can offer insights about the likely use of this case.

Changed in openoffice:
status: Unknown → New
Changed in openoffice:
status: New → Invalid
Chris Cheney (ccheney)
tags: added: hardy
Revision history for this message
penalvch (penalvch) wrote :

Florian Wiesweg, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in openoffice.org (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.