Bug 43914 - FILESAVE: Problem with Microsoft Office Power Point presentations open/save.
Summary: FILESAVE: Problem with Microsoft Office Power Point presentations open/save.
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.4.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-17 14:17 UTC by Ákos Melczer
Modified: 2013-05-29 13:57 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Slide 3 of Original (unsaved) file on v4.0.3 (49.69 KB, image/png)
2013-05-28 13:33 UTC, business.kid
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ákos Melczer 2011-12-17 14:17:37 UTC
Problem description: 

If i open or save  a .pptx from Libre Office presentation the result will be different from the original.
 
Steps to reproduce:
1. create a Libre office presentation.
2. save as .pptx
3. open this file or an already existing .pptx made in Power point.

Current behavior:

The opened file have problems with formating, fonts.  

Expected behavior:

the opened file have nothing problem in it. Looks same as the original.

Platform (if different from the browser): 
              
Browser: Opera/9.80 (X11; Linux i686; U; en) Presto/2.10.229 Version/11.60
Comment 1 business.kid 2012-03-01 00:55:46 UTC
I want to second this bug. I hung a ppt on
https://skydrive.live.com/?lc=6153#!/?cid=9936144096FF2C07

It's Public/gain_controlled_Systems.ppt, and just over 1 Meg

File/Open, File/Save, and it's only 260k! I can still see it, but it's not saved. Try to open it again with LibreOffice and it crashes & dies.

BTW, I never trust skydrive. If the link doesn't work, drop me a mail and I'll attach it, but I wanted to avoid a 1MB attachment.
Comment 2 sasha.libreoffice 2012-03-23 03:30:56 UTC
@ business.kid@gmail.com
Thanks for testcase presentation
Please, write: which CPU (32 or 64), Videocard vendor and OS used for crash
Comment 3 QA Administrators 2013-05-26 22:31:22 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 4 business.kid 2013-05-27 09:10:55 UTC
Sorry6 about delay. I never knew you needed stuff - I just seconded this bug and went away. I get spam from bugzillas and delete automatically if it doesn ring a bell. 

The bos: HP 6715S Turion twin core 64 bit 2Ghz; 3g ram; ATI/AMD RS690/SB600 chipset, using the RS690 GPU (aka X1250 series, aka RS600, aka r4xx type, aka ??). OSS drivers (Only choice). Running Slackware-13.37.
Comment 5 QA Administrators 2013-05-27 17:23:58 UTC
In the future please mark a bug as UNCONFIRMED once information has been attached, otherwise we never look at the bug again :)


Thanks!
Comment 6 Jorendc 2013-05-27 18:51:04 UTC
(In reply to comment #4)
> Sorry6 about delay. I never knew you needed stuff - I just seconded this bug
> and went away. I get spam from bugzillas and delete automatically if it
> doesn ring a bell. 
> 
> The bos: HP 6715S Turion twin core 64 bit 2Ghz; 3g ram; ATI/AMD RS690/SB600
> chipset, using the RS690 GPU (aka X1250 series, aka RS600, aka r4xx type,
> aka ??). OSS drivers (Only choice). Running Slackware-13.37.

Sorry to bug you again, but I see your link in Comment 1 doesn't work anymore. Is it possible to upload a test file again?
Comment 7 business.kid 2013-05-28 09:28:11 UTC
That link works now. I still have the same box, using LibreOffice-3.4.4.

Up there are:
1. Gain_Controlled_Systems.ppt
2. Gain_Controlled_Systems_saved.ppt (Simply Open, File, Save As)
3. Gain_Controlled_Systems.pdf (From 2, File, Export as pdf).

I haven't run diff on them, but the differences in file size are pretty alarming!
Do you want me to add them as attachments?
Comment 8 sasha.libreoffice 2013-05-28 10:01:09 UTC
Thanks for documents.
What I can see in 4.0.3 on Fedora (RFR) 64 bit:
both ppt files opens almost immediatedly on my comp (1.8Ghz cpu). No crashes.

in msPP 2010 on XP both files open correctly. If smallest file save under another name as ppt then it restores it's initial size of about 1 Mb.

@ business.kid
If mentioned above ppt files have visual differences then, please, tell where exactly. 
What about changes in file size: IMHO it results in no problem.
Comment 9 business.kid 2013-05-28 11:38:20 UTC
The pdf looks OK. There is a slight shift in the shading on slide 4 (The coloured background on the very last formula), but that's absolutely trivial.

The saved ppt crashes LibreOffice. It closes every time. That's what brought me onto your bugzilla in the first place. I had saved it locally and couldn't read it. This (newer) laptop has LibreOffice Version 3.6.4.3 (Build ID: SlackBuild for 3.6.4 by Eric Hameleers), and Slackware-14.0. This from dmesg|tail seems relevant
[13828.031662] soffice.bin[1838]: segfault at 7ffa5d9d4d66 ip 00007ffa19eb1ba4 sp 00007fff1bdb6fa0 error 4 in libsmlo.so[7ffa19e39000+182000]
[13855.265414] soffice.bin[2718]: segfault at 7f457758ad66 ip 00007f4547411ba4 sp 00007fff1031cc30 error 4 in libsmlo.so[7f4547399000+182000]
[13879.694560] soffice.bin[2756]: segfault at 7f188cfe1d66 ip 00007f1861063ba4 sp 00007fffde8191e0 error 4 in libsmlo.so[7f1860feb000+182000]
[14150.251523] soffice.bin[2817]: segfault at 7f8a2b4f5d66 ip 00007f89f0a24ba4 sp 00007fff20b90120 error 4 in libsmlo.so[7f89f09ac000+182000]

I tried opening it a few times, so I presume that's the three segfaults. /var/log/messages has similar

May 28 12:10:35 RoseViolet kernel: [13828.031662] soffice.bin[1838]: segfault at 7ffa5d9d4d66 ip 00007ffa19eb1ba4 sp 00007fff1bdb6fa0 error 4 in libsmlo.so[7ffa19e39000+182000]
May 28 12:11:03 RoseViolet kernel: [13855.265414] soffice.bin[2718]: segfault at 7f457758ad66 ip 00007f4547411ba4 sp 00007fff1031cc30 error 4 in libsmlo.so[7f4547399000+182000]
May 28 12:11:27 RoseViolet kernel: [13879.694560] soffice.bin[2756]: segfault at 7f188cfe1d66 ip 00007f1861063ba4 sp 00007fffde8191e0 error 4 in libsmlo.so[7f1860feb000+182000]
May 28 12:15:58 RoseViolet kernel: [14150.251523] soffice.bin[2817]: segfault at 7f8a2b4f5d66 ip 00007f89f0a24ba4 sp 00007fff20b90120 error 4 in libsmlo.so[7f89f09ac000+182000]

error 4?
I can't attach ppt files - bugzilla complains. That Public Skydrive directory is my 'pastebin' so I like to keep it free of detritis. That's why the files vanished.

BTW the only libsmlo.so in the system is an LibreOffice file.
Comment 10 sasha.libreoffice 2013-05-28 12:29:37 UTC
crash reproduced in 3.5 and 3.6 on Fedora (RFR) 64 bit
but 4.0.3 works correctly
Comment 11 business.kid 2013-05-28 13:33:44 UTC
Created attachment 79895 [details]
Slide 3 of Original (unsaved) file on v4.0.3

I didn't hugely trust results from Fedora, which is heavily patched in places, and permanently in Alpha or Beta. I'm using the Electronic Spin ATM for a project. So I updated Slackware to 4.0.3 and the saved file is fine. Bug solved.


The unsaved(original) file threw up this on slide 3, which is an abberation. But I haven't the time or energy to file another bug. All the other similar boxes in the file are top class, and finish where expected. :-O?
Comment 12 sasha.libreoffice 2013-05-29 11:03:53 UTC
Done.
Bug 65123 - Presentation document (ppt) opens incorrectly, wrong hight of rectangle
Comment 13 Jorendc 2013-05-29 13:57:10 UTC
So as per Comment 11 and Comment 12, lets mark this bug as RESOLVED WORKSFORME then. Thanks for your feedback, and Sasha: thanks for creating a new bug report :)!

Kind regards,
Joren