Bug 42283 - SLIDESHOW: OpenGL transitions not working in Libreoffice 3.4.3 Release.
Summary: SLIDESHOW: OpenGL transitions not working in Libreoffice 3.4.3 Release.
Status: RESOLVED DUPLICATE of bug 42338
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-26 09:09 UTC by Gamaliel
Modified: 2012-01-02 06:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
The logfile from the strace libreoffice command, applying an OpenGL transition. (681.10 KB, application/x-bzip)
2011-12-16 11:03 UTC, Gamaliel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gamaliel 2011-10-26 09:09:17 UTC
Problem description: 

Using the latest AMD catalyst driver, I am unable to reproduce any opengl transitions. I am using the libreoffice rpm, however, the problem is also persistent on Mandriva's older version: libreoffice-3.4.2-2.1 rpm. The output is basically the same as https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/243617. The problem also persisted with Mandriva's native 11.8 catalyst drivers (fglrx), as well as the open-source one.

Steps to reproduce:
1. Open Libreoffice3.4 Impress.
2. Select an OpenGL transition. 

Current behavior:

It does not work, even in the "preview animation" screen. It only fades to black and in the slideshow it acts as if there was no transition. From the ubuntu bug, this seems to be a conflict with 64-bit versions.

Expected behavior:
Working OpenGL transitions.

Platform (if different from the browser): 
Mandriva 2011 64-bits, using ATI Catalyst Driver 11.9 (installed from AMD site).

Thanks in advance.
Comment 1 Gamaliel 2011-12-16 11:03:03 UTC
Created attachment 54510 [details]
The logfile from the strace libreoffice command, applying an OpenGL transition.
Comment 2 David Tardon 2012-01-02 05:05:29 UTC

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