Bug 61107 - SLIDESHOW: Elements within a slide advance in a wrong order
Summary: SLIDESHOW: Elements within a slide advance in a wrong order
Status: RESOLVED DUPLICATE of bug 59629
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-02-19 09:32 UTC by Niko Z.
Modified: 2013-02-19 23:54 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
One of the presentations that results in this behavior (1.98 MB, application/vnd.ms-powerpoint)
2013-02-19 09:32 UTC, Niko Z. 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Niko Z. 2013-02-19 09:32:23 UTC 
Created attachment 75100 [details]
One of the presentations that results in this behavior

Problem description: I have many .ppt and .pptx presentations that used to work perfectly with LO 3.6. However, in LO 4.0 the order of elements appearing on a given slide is messed up. For example, the lines that should be the last to appear on a given slide are visible by default, the next click will bring the title, then the first line of text, etc. The problem is 100% reproducible across 2 Linux distros.I have installed LO 4.0 on Ubuntu Pangolin manually and on Bodhi Linux 2.2 it was installed through regular update process. Presentations display correctly in Powerpoint and Impress 3.6.

Steps to reproduce:
1. Switch to full screen and begin clicking.
2. ....
3. ....

Current behavior: Elements in a given slide appear out of sequence. Last two lines of text are always visible by default.

Expected behavior: First line should appear first, last line last.

              
Operating System: Ubuntu
Version: 4.0.0.3 release
Last worked in: 3.6.0.4 release
Comment 1 Jorendc 2013-02-19 23:54:13 UTC 

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