Created attachment 88697 [details] short ms word .doc that crashes writer 4.1.3 but not 4.1.2 under win 7 64bit When I try to open .doc file created and used without problems by previous versions (lo writer 4.1.2 and earlier), the new 4.1.3 relead version crashes with message: loading component library failed: file:///C:/Program%20Files%20(x86)/LibreOffice%204/program/../program/vbaswobjlo.dll. I use a Swedish MS Windows 7 SP1, 64-bit and the "missing" dll resides under: C:\Program Files (x86)\LibreOffice 4\program This dll actually exists in what looks like the correct position C:\Program Files (x86)\LibreOffice 4\program\..\program\vbaswobjlo.dll The format of the .doc-file is MS Word/Office-2000 Writer is able to create and save this .doc format, but when I try to read the same file I just created using writer 4.1.3, I get the same crash and error message as when trying older files. Best Per
Thank you for your bug report, I CAN'T reproduce this bug running Version: 4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a OS: Mac osx 10.9. I will test this bug on Windows 7.
I have tested with an empty .doc-file (no chars entered, just save as .doc) - same result. Same files in .odt-format works fine. /Per
Hi Per, Like Thomas I fail to reproduce, tested using Windows 7 with LibreOffice 4.1.3. It might help to reset your user profile. Close down all libreoffice dialogs On a windows 7 it is located: <username>\%appdata%\libreoffice\4\user Just renaming the map '4' to '4old' is enough. Then restart LibreOffice and try again. (PS: appdata is a hidden folder, you have to make these hidden folder visible in the map-options) For detailed information about user profiles: https://wiki.documentfoundation.org/UserProfile Did this solve your issue? Kind regards, Joren
Thanks for your efforts! - But it didn't solve the issue. I will uninstall and reinstall to see if that helps. I will get back later tonight w a report. Best Per PS I tried to test 4.1.3 on my opensuse 12.3 but that was just too unstable (expected as it was factory stuff...)
A _complete_ re-install solved the problem. One thing I noticed _this_ time was that the install process may collide with w7 indexing (never happened before - and I've been using oo and lo since 1.0... I had to turn indexing off in order for the install to complete - but that was OK, I got fair notice ;-) Best Per
(In reply to comment #5) > A _complete_ re-install solved the problem. Good to hear :)! > One thing I noticed _this_ time was that the install process may collide > with w7 indexing (never happened before - and I've been using oo and lo > since 1.0... I don't use windows that much, but I never saw that collision too :). > I had to turn indexing off in order for the install to complete - but that > was OK, I got fair notice ;-) I'll try to be alert for more problems related to this topic. Thanks for your feedback! Lets mark this bug as RESOLVED WORKSFORME. Kind regards, Joren