LibreOffice 4 fails to open any of the .odt and .ods files I created with LibreOffice 3.4.x-3.6.x. I have used LibO 3.x for several years and have numerous documents I need to continue to have access to. "Upgrading" to the 4.0 release has removed my ability to do anything. When attempting to open any ODF document, I get an error stating that the file is corrupted. The option to attempt recovery is offered, but consistently fails. Documents in other formats, i.e. doc files, open fine. LibreOffice apparently lost all backwards compatibility with itself when gaining improvements in handling some obsolete proprietary formats. This state of affairs is completely unacceptable, forcing me to revery to 3.6.5 to get any work done.
Hi bugs@mailinator.com, I can open all my ODF files without any issue. No matter what was the version to save. Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) Have you tried to reset the user profile, sometimes solve strange issues. https://wiki.documentfoundation.org/UserProfile Please attach a sample file with the issue to verify. It is not right the reporter set the status NEW, this must be done by other person after confirm the bug.
Created attachment 74911 [details] non-sensitive file which exhibits the problem
I set status to NEW because that was the logical choice. If it should be set differently, then the bug reporting system should enforce that. Consider it a bug in the bug reporting system that it allowed me to set wrong status. The file I attached is one I tried to open as a test after others I actually needed failed. It has nothing important and is small so hopefully simple. It was created with LibO 3.6.x on OS X 10.6. The system I tried LibO 4 on is a fresh install on Windows7 which had no prior version so the LibO user profile should have been freshly created. No options were changed at install except removing the extra useless dictionaries and interface languages. No settings were changed in LibO. I tried to open the file I needed, it failed, and then I started testing many other to see they all failed, except for the .doc I tried which happens to have been saved by LibO exporting to .doc and not from MS Word.
Created attachment 74918 [details] Screnshot of sample file. Well, the sample file opens fine with: Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) see attached screenshot
Opens perfectly fine for me on OS X 10.8.2 with LO 4.0.0.3. So this must be related to problems specific to your machine.
on pc Debian x86-64 with 4.0 sources updated some days ago, I don't reproduce this. Could you try this: 1) - create a brand new Writer file on MacOs with LO 3.6. Just put "test" in it and save the file - try to open the file on Windows with LO 4.0 If you reproduce the problem, try this other test: 2) - create a brand new Writer file on Windows with LO 4.0. Just put "test" in it and save the file - retrieve the file on MacOs with 3.6 version, add some words in it and save again. - try to reopen the file on LO 4.0 on Windows Also: - did you install any specific fonts on MacOs? - did you install any LO extensions on MacOs?
I installed 4.0.0.3 again in an attempt to get a screenshot of the error. However, the error no longer happens and the documents open fine. What is different now is that 4.0 was installed alongside 3.6.5. Previously, I had installed 4.0 fresh with no prior version ever having been on the machine. So, the problem case seems to be fresh install of 4.0 on Windows 7. Anyone upgrading from a prior version will probably not see the error, but someone new to LibreOffice will have a rather bad experience. In my original report I said "upgrade" in quotes because I had 3.6 on XP64, then I formatted the drive, installed Windows 7 64bit and when reinstalling applications used the fresh released LibreOffice 4.0.0.3. At that point LibO was broken and could open no ODF files. Uninstalling 4.0, installing 3.6.5 and then installing 4.0 again without first removing 3.6.5 results in 4.0 installed and working (in that ODF files open) and 3.6.5 was silently removed (as I selected a separate directory for install, I had expected having both versions available for testing).
bugs: thank you for your feedback. Rainer: would you have some time to give it a try? If confirmed, it could be very serious.
I put a bug in see also, they may be related (perhaps dup)
I put another see also, it seems we have a real problem here. Mariosv: on which env did you make your test?
(In reply to comment #10) > I put another see also, it seems we have a real problem here. > > Mariosv: on which env did you make your test? Win7x64 Ultimate
mariosv: did you uninstall LO 3.6.5 or directly upgrade to 4.0.0.3?
(In reply to comment #12) > mariosv: did you uninstall LO 3.6.5 or directly upgrade to 4.0.0.3? I had previously installed 3.6.4/5, I am sure that there was a version 3 profile when I installed some of 4.0 versions. (4.0.0.3 LODev 4.0 LOdev 4.1)
mariosv: ok you had previously installed 3.6.4/5 but did you uninstall it and install LO 4.0.0.3 or just upgraded? I'm asking because I'm trying to find a common pattern on the 3 bugs (this one + both of "see also")
(In reply to comment #14) > mariosv: ok you had previously installed 3.6.4/5 but did you uninstall it > and install LO 4.0.0.3 or just upgraded? > I'm asking because I'm trying to find a common pattern on the 3 bugs (this > one + both of "see also") Just upgrade. And I have just uninstall 4.0.0.3, renaming the profiles for 3 and 4, and install again 4.0.0.3, and the sample file open right. I can not reproduce the issue
thank you mariosv for your feedback. It confirms what bugs said: someone who upgraded won't have this problem.
(In reply to comment #16) > thank you mariosv for your feedback. > > It confirms what bugs said: someone who upgraded won't have this problem. Sorry Julien What I want explain in my last post is: While I answer you last question (comment #14) about upgrade I did an uninstall of 4.0.0.3, renaming the profiles for 3 and 4, and install again 4.0.0.3, and the sample file open right. So in my understanding I can not reproduce the issue with a fresh installation.
mariosv: yep, you uninstalled 4.0.0.3 and renamed profile but you didn't uninstall 3.6/3.5 just upgraded. bfoman: could you give a try to this one? Important thing is to uninstall any previous version then install 4.0.0.3. (so no upgrade)
Hm, I never had such a problem, but it's strange that we have some similar reports. NOT reproducible with Server Installation of "LibO 4.0.0.3 - GERMAN UI / German Locale [Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89)]" {tinderbox: @6, pull time 2013-01-31 11:30(?)} on German WIN7 Home Premium (64bit) with separate new User Profile Reporter's sample is valid ODF due to <http://odf-validator2.rhcloud.com/odf-validator2/> so that it's improbable that it's a problem with document and / or old versions. Did I miss something? Currently I haven't a clue how to reproduce the bug, I only see some vague indications? @bugs@mailinator.com: In a bug report please tell the details required to reproduce the problem. In most cases a step by step instruction with all relevant details (reylly, every mouse click ...) is the best way. a) how did you try? Win explorer?, File dialog / Libo or OS? b) Where are the files? (Net drive ... )? c) exact wording of the error message? d) LibO Localization? e) Your OS localization And so on, currently there are 100000 possible reasons not directly related to the document, we need to narrow down the roots. Can you please contribute some more details? I hope with info from you and in the other bugs we will be able to clear up the puzzle If you want to report more bugs in future please use LibO menu 'Help -> Feedback/Bugreports'
Rainer: did you uninstall completely previous 4.0 version before installing last one? I suspect that some needed libs (in Windows directories for example) are still present after upgrading but no more present if you uninstall LO < 4.0 then install 4.0.0.3 Of course, it's just a guess, perhaps I'm completely wrong.
Rainer: localization is English for all. during LibO install I deselected the french and spanish dictionaries, leaving only english, and I deselected the English(UK) and English(south Africa) UI languages, leaving only English. My OS is of course English as well. I tried opening files from windows explorer and from the open dialog in LibO. The files are located on a local NTFS volume. The files I first tried were sitting on my desktop, the others are elsewhere on the same volume. No network drives involved. The exact wording of the error message is what I was after when I tried to do a parallel install of 4.0. Unfortunately, that both removed the 3.6 install and resulted in a working 4.0 install. Thus, the conclusion that an upgrade works but a fresh install doesn't. As it has been reported that an uninstall followed by install works, I must conclude that the uninstall leaves some remnants that are sufficient to make the 4.0 install work. I know that the uninstall leaves around a directory with a few files, so I can only imagine what magic might be left in the registry. I'm thinking that it will take a VM to efficiently debug this problem. I don't have the time to do so at the moment, but it would be good if someone who has a Windows VM that never had LibO installed in it could take a snapshot of said VM and then try the various install scenarios, each time recording the results and then rolling back to the snapshot before trying the next variation.
This problem is 100% reproducible! Today I remembered my laptop, which also runs Windows 7 Ultimate x64, has never had any Office-type programs installed on it. So, I decided to use it as a test case. I installed the exact same LibreOffice 4.0.0.3 build. I left in more dictionaries and interface languages rather than stripping it to pure English, and I installed the English help pack. After the installation was completed, I tried to open the same test file I uploaded and to no surprise I got the exact same errors. I took screenshots of the error dialogs in the order they appear and am attaching them as Error1.png, Eroor2.png and Error3.png. The funny thing I noticed is that the dialogs appear exactly the same regardless of whether I choose Yes or No in the first dialog. I then opened LO Writer, typed the word "test", and saved it as test.odt. That file will not open either, same exact errors. So, it has nothing to do with where the files came from. A fresh install of LO4 simple CANNOT OPEN ANY ODF FILES! I am leaving the LO4 install on the laptop as-is since I don't really need to use it there. I have a working install on my desktop accomplished by doing the upgrade install over 3.6.5. I will happily provide info from filesystem and registry to compare the two install situations to assist in debugging. This should be trivial to reproduce and I really don't understand how this could not be found in testing before declaring LO4 ready. Fresh install MUST be included in the test cases but it is abundantly clear all testing was done with upgrade installs only.
Created attachment 75358 [details] First error dialog selection here does not affect progression
Created attachment 75359 [details] Second error dialog
Created attachment 75360 [details] Third error dialog
Created attachment 75361 [details] simplest test file made by LO4 but not openable with LO4
Tor: would you have some time to take a look to this one? It seems that upgrading LO is ok but fresh 4.0.0 install or uninstall previous+install 4.0.0 is ko to open any file.
is anybody even looking into this serious problem, or does nobody care?
bugs@mailinator.com: is it better with recently released 4.0.1?
It's still happening with 4.0.1.2 on Arch Linux, even when resetting the user profile.
I found some time to test on Win7. I uninstalled 3.6.5 and removed LO directory profile. Then I installed 4.0.1.2 I gave a try with some existing files on my laptop, no problem. Then I gave a try to the 2 files attached to this bugtracker, no problem. So what I supposed in my comments 20 and 27 was wrong :-( bugs: did you try to reproduce after having let every option by default and without installing anything else? Did you install or uninstall anything on fresh after format Win7 before installing and testing LO?
Today I downloaded 4.0.1.2 and tested on both Win7 machines. Desktop: first failed with 4.0. Installed 3.6.5 then upgraded to 4.0 and it worked. Uninstalled 4.0 in order to change directory name to unversioned as it's clear I can't have parallel installs as planned. Installed 4.0.1.2 with same options as before. Opens test file just fine. So, either uninstall and reinstall works same as upgrade, or 4.0.1 fixes, but can't tell which. Laptop: Had a 4.0.0.3 install with no prior versions which failed to open all test files. Attempted upgrade to 4.0.1, result: couldn't open LibreOffice at all, long error that basically said 'go reinstall'. Uninstalled LO completely, installed 4.0.1.2 with same options and the the help pack. It can open the test files. Conclusion... I have no idea if 4.0.1 fixes it as both ended up being a uninstall/reinstall scenario and I have no more fresh Win7 boxes to install LO 4.0.1 on to test the totally fresh install scenario. JN: things installed on Win7 before LO4 were windows updates and drivers (AMD monster chipset and video package), ClamWin AV (set not to interfere, just log), ClassicShell, WinRAR, FAR, Firefox, Opera, SumatraPDF, VLC, XviD, AC3filter, FFDshow, etc.
bugs: Following your last comment, I put it WFM. Thank you for your feedback.