Created attachment 56928 [details] odt-file which causes my LibreOffice to crash directly Whenever I try to open a file with footnotes, or several other features, such as images, some tables, pasted text from the internet, and basically anything that is not raw text, it crashes. I have tried with different files, I have tried different content, and I have even tried removing both LibreOffice writer and reinstalling it, and removing LibreOffice altogether and reinstalling that - unsuccessfully. It continues to crash after at most five seconds, and especially when I scroll down to a place in the document where a footnote, text area or other features are. This bug is a deal breaker for me. I cannot work in LibreOffice if it continues to crash before I even can start to work.
The attached document don't cause crash in 3.5 RC3. But at other hand, it contains no footnotes or pictures, just unformatted text with some yellow highlight.
(In reply to comment #1) > The attached document don't cause crash in 3.5 RC3. But at other hand, it contains no footnotes or pictures, just unformatted text with some yellow highlight. Thanks for the reply. Please note that the header and the text says that many different features causes LibreOffice to crash. One friend suggested that the problem may be a shortage of memory, but my computer's memory is fine and I have no other problems. I should also add that the problem occured quite suddenly, without me doing any changes, such as downloading new programs or deleting programs. As before, any ideas are most welcome.
On pc Debian x86-64 with 3.5 branch updated yesterday (so not exactly 3.5.0 rc3)I reproduced exactly what Urmas said. Noticed these messages on console, I don't know if there's a link : warn:sw.uno:9380:1:/home/julien/compile-libreoffice/libo_3_5/sw/source/ui/uno/SwXDocumentSettings.cxx:474: "CurrentDatabaseCommand" property possibly set before "CurrentDatabaseDataSource" warn:sw.uno:9380:1:/home/julien/compile-libreoffice/libo_3_5/sw/source/ui/uno/SwXDocumentSettings.cxx:483: "CurrentDatabaseCommandType" property possibly set before "CurrentDatabaseDataSource" warn:sw.uno:9380:1:/home/julien/compile-libreoffice/libo_3_5/sw/source/ui/uno/SwXDocumentSettings.cxx:485: "CurrentDatabaseCommandType" property possibly set before "CurrentDatabaseCommand" Lennart: - Have you got any error messages if LO launched from console ? - You said you uninstall but did you remove (or backup) your profile directory ? - Did you reproduce by creating a brand new document with footnotes ? - Did you try to reproduce with 3.4.5 (last stable version) ? - Which Linux distrib do you use ?
(In reply to comment #3) > On pc Debian x86-64 with 3.5 branch updated yesterday (so not exactly 3.5.0 rc3)I reproduced exactly what Urmas said. > Noticed these messages on console, I don't know if there's a link : > warn:sw.uno:9380:1:/home/julien/compile-libreoffice/libo_3_5/sw/source/ui/uno/SwXDocumentSettings.cxx:474: "CurrentDatabaseCommand" property possibly set > before "CurrentDatabaseDataSource" > warn:sw.uno:9380:1:/home/julien/compile-libreoffice/libo_3_5/sw/source/ui/uno/SwXDocumentSettings.cxx:483: "CurrentDatabaseCommandType" property possibly set > before "CurrentDatabaseDataSource" > warn:sw.uno:9380:1:/home/julien/compile-libreoffice/libo_3_5/sw/source/ui/uno/SwXDocumentSettings.cxx:485: "CurrentDatabaseCommandType" property possibly set > before "CurrentDatabaseCommand" > > Lennart: > - Have you got any error messages if LO launched from console ? > - You said you uninstall but did you remove (or backup) your profile directory ? > - Did you reproduce by creating a brand new document with footnotes ? > - Did you try to reproduce with 3.4.5 (last stable version) ? > - Which Linux distrib do you use ? Thanks for the reply, Julien. I have no idea what the first lines mean, since I am not a programmer (only moderately good with "behind-the-scenes" of computers). CurrentDatabaseDataSource does sound like it's a problem with the program rather than some setting that I've accidentally changed, but you probably have a better analysis. In response to your questions: - when I run LO from terminal, same thing happens. After I open a document with anything other than raw text, it crashes after about a few seconds. - I have tried removing the LO profile (as described here: http://askubuntu.com/a/41331), but this did not make LO cease crashing. Instead it made LO post 3 error messages ("Error when loading BASIC in the document [filepath] General error General input/output error" (my translation from original Swedish) - Yes, I have tried to create new documents with footnotes, and other features that have previously seemed to make LO crash. In some cases, the new documents have caused LO to crash. I cannot say for certain which things make it crash, but one thing that does is pasting things from the internet. Not always, but often. - I have not tried LO 3.4.5 yet, but I will today. - I use Ubuntu 11.10 Again, thanks in advance for any help.
I have now installed a fresh version of Ubuntu and have tried to replicate the situation but it appears that it has been resolved. Thanks for your help.
Whenever I insert footnotes, and sometimes headers or footers, LibreOffice crashes. Sometimes it's possible to reopen it, sometimes the file is completely corrupted... This usually happens within 30 minutes of having the file open with these 'extras' inserted, so I now save them for the end and do it fast! Inserting other elements, like photos or tables, does not seem to affect a document's stability. It seems that the earlier fix I read here should already be part of the version of Writer that I'm using (4.1.3.2)... yet I'm still having issues. I am a relatively new user to Linux -- only installed it 6 months ago. Please help!
Could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) and give a new try? Also try a recent LO version (last stable one is 4.4.1 or 4.3.6). Indeed, even if the original bug has been solved 2 years ago, I suppose root cause of your problem is different.
Please, do not change the version number, it shows the oldest version in which the bug has been found. Best regards. JBF
The original issue had been resolved and was most likely the result of a corrupted profile or a bug in an older version. This report was reopened three years later instead of a new report being filed. @laughin41 - If you are still experiencing crashes please feel free to open a new bug report with reproducible steps. Changed to RESOLVED WORKSFORME because RESOLVED FIXED is for specific commits.