Created attachment 102962 [details] Attached is an image of the Text Import window. Problem description: I have two different Linuxes installed on my desktop machine. One of them has LO 4.2.5.2, and the other has LO 3.5.4.2. I normally use the newer version. Occasionally, after editing an LO Calc file, with 4.2.5.2, the next time I go back to open it, Calc (4.2.5.2) presents me with the Text Import pop up window. Every time that happens, I go to LO 3.5.4.2, open that same file, and 3.5.4.2 presents me with a pop up, but this time it tells me the file needs repair. I tell it 'Yes" repair the file. It does so and I go ahead, edit the spreadsheet, and re-save the file under a new name. I go back to LO 4.2.5.2 and it opens the new file just fine. And I'm happy until the next time it corrupts the file, and I repeat the process. I cannot predict when its going to happen, it's random. As far as I can remember this has been going on since the release of the 4.x series. Sorry, I do not remember just when this problem appeared. Steps to reproduce: 1. Open a Calc .ods file 2. Edit and save the file 3. Reopen the file Current behavior: Sometimes, after editing and saving a .ods file with LO 4.2.5.2, upon reopening the file it will be corrupt and present the Text Import window. Expected behavior: I expect to be able to reopen an edited .ods file without being presented with a Text Import window. Operating System: Linux (Other) Version: 4.1.0.4 release
Hmmm, never had that problem with any LO version. Some questions to try to bound the problem: 1/ Where is stored your file? On your hard disk or on an external drive like usb key? 2/ Do you observe this problem with a particular file or with whatever .ods file? 3/ Is your file password protected? Set status to NEEDINFO. Please set it back to UNCONFIRMED when you will have provided the requested informations. Thank you for your understanding. Best regards. JBF
[quote] Hmmm, never had that problem with any LO version. Some questions to try to bound the problem: 1/ Where is stored your file? On your hard disk or on an external drive like usb key? 2/ Do you observe this problem with a particular file or with whatever .ods file? 3/ Is your file password protected? Set status to NEEDINFO. Please set it back to UNCONFIRMED when you will have provided the requested informations. Thank you for your understanding. Best regards. JBF [/quote] 1 - The files are kept on an external flash drive 2 - I have observed this problem on two different .ods files. 3 - Files are not password protected. Status set back to UNCONFIRMED. Jerry PS: What happened to my comments I added yesterday?
Sorry, I'm getting confused. My comments yesterday were on the Chromium Issues site.
This info might be helpful. These are my comments on the Chromium site yesterday: I can confirm that I do still see the issue on this version of Chromium: Info from chrome://version: Chromium 34.0.1847.116 (Developer Build 260972) Built on Ubuntu 14.04, running on Ubuntu-LXLE 14.04 aura As you can see, I am running LXLE Linux, which is based on Lubuntu. Chromium was installed from the repos using Synaptic. LXLE is completely updated. As a comparison, I also installed Google Chrome (Stable) by first downloading the 64bit deb file from here: https://www.google.com/chrome/browser/#eula Then I installed the deb file using Gdebi. Google Chrome version info: Google Chrome 35.0.1916.153 (Official Build 274914) OS Linux Google Chrome does NOT exhibit the same behavior as Chromium. All I can do is install the latest Chromium from the repos. Maybe this issue will evaporate when Chromium catches up to Chrome. Or, I could just use Chrome. I just thought I would report the issue.
(In reply to comment #4) > This info might be helpful. These are my comments on the Chromium site > yesterday: > > I can confirm that I do still see the issue on this version of Chromium: What is the link between LibreOffice and Chromium here ? Best regards. JBF
(In reply to comment #5) > (In reply to comment #4) > > This info might be helpful. These are my comments on the Chromium site > > yesterday: > > > > I can confirm that I do still see the issue on this version of Chromium: > > What is the link between LibreOffice and Chromium here ? > > Best regards. JBF Absolutely none! Sorry, I posted the wrong information.
Sorry there just isn't enough information here for us to accurately reproduce the problem. Please provide steps that we can consistently reproduce the problem and if possible attach a document that is corrupted by 4.2.5.2. Until then we'll have to leave this in NEEDINFO - once you provide these things mark as UNCONFIRMED.
(In reply to comment #2) [...] > 1 - The files are kept on an external flash drive Are you sure that you unmount the external flash drive before removing it? You should see a message box saying something like "Now you can safely remove the external device". If you do not wait that, you can't be sure that all data have been written on the external device. Best regards. JBF
(In reply to comment #7) > Sorry there just isn't enough information here for us to accurately > reproduce the problem. Please provide steps that we can consistently > reproduce the problem and if possible attach a document that is corrupted by > 4.2.5.2. > > Until then we'll have to leave this in NEEDINFO - once you provide these > things mark as UNCONFIRMED. "Please provide steps that we can consistently reproduce the problem" Well, that's a problem, because I can't consistently reproduce the problem, yet. "if possible attach a document that is corrupted by 4.2.5.2." Well, they contain financial information. So, I can't even open a corrupt file to conceal personal information. I realize it's hard to fix a problem you can't reproduce. Maybe we'll just have to leave this issue as NEEDINFO for now until I can purposefully reproduce it.
(In reply to comment #8) > (In reply to comment #2) > [...] > > 1 - The files are kept on an external flash drive > > Are you sure that you unmount the external flash drive before removing it? > You should see a message box saying something like "Now you can safely > remove the external device". If you do not wait that, you can't be sure that > all data have been written on the external device. > > Best regards. JBF Yes, I always Save file, Unmount drive, and then remove drive from computer.
Just as a test, I made copies of the two files that have been corrupted in the past and saved them in a "Test Files" folder. I then unmounted the drive. I then booted into the system with LO 3.5.4.2, edited both files, adding some numerical data and even creating a new chart. These are the typical operations that I perform in these files. I saved both files, then unmounted the flash drive. Then, I rebooted back into the system with LO 4.2.5.2 and opened both files. Both files opened without any errors or displaying the Text Import dialog. I was just wondering if I had done that in the past, and that's what was creating the problem. Well, all I can say is that it didn't corrupt either file this time. LO 3.5.4.2 .ods files should be compatible with 4.2.5.2, right? And 4.2.5.2 .ods files compatible with 3.5.4.2? Regards, jv
So 4.2.5.2 will be compatible with every other release (or should be) but the opposite might not be 100% true - depends on what features you are using. If you're using features that were brought in in 4.x and trying to use them in 3.x, well, that might create some problems.
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 Message generated on: 2015-02-18
I have no new information, and I cannot consistently reproduce this bug, so I'll mark it UNCONFIRMED.
Ok, closing as WorksForMe for now. Please, feel free to reopen if you can reproduce the problem with a clear step by step scenario. Best regards. JBF