Bug 84114 - FILESAVE: Error by saving a file
Summary: FILESAVE: Error by saving a file
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.2.6.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-20 02:19 UTC by Pantalaimon9469
Modified: 2015-07-18 17:27 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
The mistake is "hagh" but it should be "high", even though I edit that paragraph and save and close the application and then reopen the file, the same mistake is there. (402.90 KB, image/png)
2014-09-20 02:19 UTC, Pantalaimon9469
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pantalaimon9469 2014-09-20 02:19:05 UTC
Created attachment 106570 [details]
The mistake is "hagh" but it should be "high", even though I edit that paragraph and save and close the application and then reopen the file, the same mistake is there.

I edited a presentation correcting some mistakes in the ortography, I pressed the "Save" button and then closed LibreOffice Impress. Next, I reopen the file I've just edited and the same mistakes are in my presentation, as if it has not changed.
Operating System: Ubuntu
Version: 4.2.6.2 release
Comment 1 A (Andy) 2014-09-20 10:06:09 UTC
This is for me not reproducible with LO 4.3.1.2 (Win 8.1).

Steps Done:
1. Open IMPRESS
2. Write a wrong typed word in the slide text field
3. Go to TOOLS -> SPELLING and let correct this word
4. Go to FILE -> SAVE AS and save the file (as odp)
5. Reopen this saved file

Result: The correct word is shown.


Therefore, could you please give more information about the different single steps to reproduce it, if this is not the right procedure to try to reproduce it.
Otherwise, it could maybe be a Linux only problem?
Comment 2 Pantalaimon9469 2014-12-07 03:03:50 UTC
Hey there!

I was trying with the same file in LibreOffice 4.2.7.2 but I have the same problem, I think that this could not be a software bug, maybe is a file problem, I mean, perhaps my file is corrupted or something, though I do not uderstand why... :(

Could you give me your email address, I could send to you my file and you could check it.

The mistake is "hagh" in the fourth slide. Correct that word typing "high", save the file (.odp format), close Impress, reopen the file and check if the mistake was corrected. Please.
Comment 3 Pantalaimon9469 2014-12-07 03:08:05 UTC
(In reply to A (Andy) from comment #1)
> This is for me not reproducible with LO 4.3.1.2 (Win 8.1).
> 
> Steps Done:
> 1. Open IMPRESS
> 2. Write a wrong typed word in the slide text field
> 3. Go to TOOLS -> SPELLING and let correct this word
> 4. Go to FILE -> SAVE AS and save the file (as odp)
> 5. Reopen this saved file
> 
> Result: The correct word is shown.
> 
> 
> Therefore, could you please give more information about the different single
> steps to reproduce it, if this is not the right procedure to try to
> reproduce it.
> Otherwise, it could maybe be a Linux only problem?

Hey there!

I was trying with the same file in LibreOffice 4.2.7.2 but I have the same problem, I think that this could not be a software bug, maybe is a file problem, I mean, perhaps my file is corrupted or something, though I do not understand why... :(

I leave this dropbox link, download the file, please.

The mistake is "hagh" in the fourth slide. Correct that word typing "high", save the file (.odp format), close Impress, reopen the file and check if the mistake was corrected. Please.
Comment 4 Pantalaimon9469 2014-12-07 03:10:20 UTC
(In reply to A (Andy) from comment #1)
> This is for me not reproducible with LO 4.3.1.2 (Win 8.1).
> 
> Steps Done:
> 1. Open IMPRESS
> 2. Write a wrong typed word in the slide text field
> 3. Go to TOOLS -> SPELLING and let correct this word
> 4. Go to FILE -> SAVE AS and save the file (as odp)
> 5. Reopen this saved file
> 
> Result: The correct word is shown.
> 
> 
> Therefore, could you please give more information about the different single
> steps to reproduce it, if this is not the right procedure to try to
> reproduce it.
> Otherwise, it could maybe be a Linux only problem?

Sorry, I forgot the link. https://www.dropbox.com/s/shrdm38fco80d78/Graphene.odp?dl=0
Comment 5 QA Administrators 2015-06-08 14:29:10 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/Bugzilla/Fields/Status/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!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 6 QA Administrators 2015-07-18 17:27:43 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

Message generated on: 2015-07-18