Bug 80226 - FILESAVE: Shape disappears after saving it as pptx
Summary: FILESAVE: Shape disappears after saving it as pptx
Status: RESOLVED DUPLICATE of bug 92076
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-19 10:51 UTC by ravingdesi
Modified: 2016-11-28 09:51 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ravingdesi 2014-06-19 10:51:24 UTC
Problem description: 
A shape disappears when the file is saved as pptx. It cannot be seen when the newly saved pptx is opened in LO or microsoft office (used 2010)

Steps to reproduce:
1. Download https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug9.odp
2. Save as pptx
For me this resulted in 
https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug9.pptx
3. Open again in impress or MS powerpoint

Current behavior:
Shape in the middle is not present.
https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug9_1.png

Expected behavior:
Shape should not vanish and be present as in odp
https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug9_2.png

Thank you very much for all your efforts.
              
Operating System: Ubuntu
Version: 4.2.4.2 release
Comment 1 retired 2014-07-27 12:37:42 UTC
Confirmed OS X 10.9.4, LO 4.3.0.3 -> NEW, OS -> all.
Comment 2 tommy27 2015-08-19 16:02:19 UTC
bug present under Win8.1 x64 too using LibO 5.1.0.0.alpha1+
Build ID: 7d3fa6bae9f7a755eb2d0ca24bf1afd5f3646bb7
TinderBox: Win-x86@39, Branch:master, Time: 2015-08-09_08:38:08
Locale: it-IT (it_IT)
Comment 3 Timur 2016-11-28 09:51:15 UTC
Works for me. 
Tested with Version: 5.4.0.0.alpha0+, Build ID: 9691cea443a74885b3f81c602efdd3345de1e3f9, TinderBox: Win-x86@39, Branch:master, Time: 2016-11-24_14:26:28.
I guess we can mark as a duplicate of Bug 92076.

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