Bug 69553 - FILESAVE: Presentation crashes when saving files
Summary: FILESAVE: Presentation crashes when saving files
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.1.1.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-09-19 03:51 UTC by Josh Rose
Modified: 2014-06-01 20:29 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Link to Problematic Presentation file (.odp) on Google Drive (76 bytes, text/plain)
2013-09-27 03:40 UTC, Josh Rose
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Rose 2013-09-19 03:51:59 UTC
Problem description: When modifying and saving some (but not all) presentation files in native .odp format, LibreOffice 4.1.1.2 has been consistently crashing at the *end* of the file save procedure.  This has been particularly affecting presentations I made within the past several months, on V. 4.* versions of LibreOffice.

Moreover, the problem is particularly prominent if I am using the "Notes" tab to input lecture notes and information for during the presentation.

Steps to reproduce:
1. Open a saved (and previously fine) .odp presentation file.
2. Modify slides and copy-and-paste or type text into the "Notes" function for each slide.
3. "Save" or "Save As..." the presentation (occurs on both functions).  The file save meter will progress until the very end, and then LibreOffice will lock up, greying out, and generating a Windows "Not Responding" message. 
4. If I force close LibreOffice and re-open, initiating the Recovery procedure for the affected file only causes LibreOffice to lock up again and become unresponsive.  I can only get LibreOffice to reopen by skipping the recovery.

Current behavior:  LibreOffice seems to work okay on new files or with other file types in Writer, for examples.

Expected behavior:  Ideally the .odp presentation files would save without incident.

              
Operating System: Windows 7
Version: 4.1.1.2 release
Last worked in: 4.1.0.4 release
Comment 1 tommy27 2013-09-25 03:28:31 UTC
please, upload a test file where you consistently reproduce the crash.
otherwise it will be impossible to debug
Comment 2 Josh Rose 2013-09-27 03:40:37 UTC
Created attachment 86704 [details]
Link to Problematic Presentation file (.odp) on Google Drive

I am the person who originally posted this bug, and have encountered it on multiple Presentation files this week (in .odp and .ppt formats), this being one of them.  At first I thought it might be corrupt files, but even after recreating them from scratch, I still encountered the error while saving.  Even uninstalling and reinstalling LibreOffice (including creating a new profile) has not helped.  Any help would be appreciated if others are encountering the same bug.

I have attached a link to the file on Google Drive (it is too large to attach directly here).
Comment 3 tommy27 2013-09-27 05:57:02 UTC
not reproducible on my Windows 7 64bit (is yours 32bit?) using 4.1.1.2 release

I edited each slide in note view mode, adding or copying and pasting random text.
I was able to save it with no issue.

I ask you some more tests:

1- download the portable version of LibO and see if it suffers the same saving crash on your PC (link: http://sourceforge.net/projects/winpenpack/files/X-LibreOffice/releases/X-LibreOffice_4.1.1_rev16.zip/download )

2- if it crash on your PC, test it on another PC with an USB key. maybe there's a problem in your PC which impairs LibO.

3- try uploading here a single slide .odp file where you still reproduce the crash. as a general rule a minimal test case is much better since it will be easier to debug (remmeber "less is more")

let me know your results.
Comment 4 Thomas van der Meulen [retired] 2013-09-28 07:24:06 UTC
Thank you for your bug report, 
I cannot reproduce this bug running libreoffice: 
Version: 4.1.1.2
Build ID: Build ID: 410m0(Build:2)
OS: Ubuntu 13.04 64-bits

I will test this bug on Windows shortly.
Comment 5 Thomas van der Meulen [retired] 2013-09-28 08:38:37 UTC
I cannot reproduce this bug running libreoffice: 
Versie: 4.1.2.2 
Build ID: 281b75f427729060b6446ddb3777b32f957a8fb
OS: Windows 7 64-bits
Comment 6 Josh Rose 2013-09-28 20:35:12 UTC
Thanks to both of you, Thomas and tommy27, for your help with this.  Perhaps I just have a set of presentations that are corrupted (all produced around the same time initially about a year and a half ago).  So, perhaps the problem is specific to my computer.  However, I do find it weird that the problem occurs even with a new version of the file made with the same images imported from my local drive.

I'll test it out using the portable version and on another computer and see what happens.
Comment 7 tommy27 2013-10-05 14:37:50 UTC
@Josh Rose  
any news?
Comment 8 QA Administrators 2014-05-17 00:33:47 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

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 9 QA Administrators 2014-06-01 20:29:44 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO