The writer 7.2.3.2 crashes on openSUSE Linux on opening an odt document that was written with an older version and has been saved without changes. Removing the profile, reinstallation didn’t help, I see nothing in /var/log.
Calc documents (ods) behave normally.
Any ideas? Thanks!
Where did you save your ODT document?
Is this only the case with one ODT document, or does the problem occur with all others as well?
Do you have a backup copy of your ODT document?
Hi! Thanks for the quick answer!
I saved the document locally, in the same folder. I attach the document that can be opened (.odt) as well as the document that crashes the writer (.2.odt). The problem appears for all odt documents.
With both documents I did not get a crash.
However, what is noticeable, and unfortunately you did not mention, is that the documents contain macros.
Macros are basically disabled for me, hence this message.
Note: you should remove personal data from uploaded files.
I know that I should remove PII, but I don’t have (old) sample documents without at hand. So I took the risk - which is limited in this case
Attached find one document that should not contain macros. I still can’t open it.
I am afraid it has something to with the interaction with the OS and the graphics subsystem.
Leer.odt (13.9 KB)
The message regarding macros still comes up.
No Crash.
With me:
Version: 7.3.1.3 (x64) / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL
I opened the original document again, and somehow I can’t remove the macros. See the attached screenshot.
My version is
Version: 7.2.3.2 / LibreOffice Community
Build ID: 20(Build:2)
CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded
I also see this, which is really startling:
I’m sorry, I generally don’t work with macros and I don’t know anything about them. That’s why I’m out at this point.
I think there will be someone else who is familiar with this problem.
Good luck.
As suspected, the issue was not caused by the macros. I pinned it down by successively building a new document by copying blocks from the old one. At some point I got a “format error in style.xml”. I replaced that part, and now everything is up and running again.
The complete absence of log and error messages is somewhat annoying. If this would have popped up when opening the document, I would have saved a lot of time and energy. I will file a bug report about this as soon as I have some time.
A big “thank you” to @Hrbrgr for his efforts!
