Problem description: I have prepared a test specification with lot of data. I have a table to enter each test case. Some times when I try to insert a new row, libre office crashes. Even the data in the table is lost. This is so irritating. With out this kind of basic thing not working, this is completely useless product. Opensource community needs a product which can substitute MS Office and that's the reason Sun started this project. And now this has become a joke. Basic table functionality not working is acceptable at all. Steps to reproduce: 1. Create a text document 2. Insert table into it 3. Add data to the table. 4. Now try to insert some more rows at different places. 5. Observe that the open office crashes 6. If you really out of your luck, even the data will be lost. Current behavior: 1. Application crashes when a row is inserted. This is most common bug I see when I google. Expected behavior: 1. The application shouldn't crash like this. Operating System: Debian Version: 4.1.2.3 release
Hi Sreekanth, thanks for reporting. Have you tried resetting the user profile?, sometimes solves strange issues. https://wiki.documentfoundation.org/UserProfile. If this not solve the issue, please can you attach a sample file.
Yes. I tried that. It didn't work for me
Are there any log files which I can upload here?
Is there a way data can be recovered. It actually destroyed a whole weeks effort just like that.
Looking in LibreOffice backup or temporary folder if there are some recoverable file, to know the paths Menu/Tools/Options/LibreOffice/Paths.
Nothing there. An empty folder :( sreekanth@spidy:~/.config/libreoffice/4/user/backup$ ls -al total 8 drwxr-xr-x 2 sreekanth sreekanth 4096 Nov 7 14:53 . drwxr-xr-x 13 sreekanth sreekanth 4096 Nov 8 11:31 ..
Unfortunately with the given information we can't do much. We need you to make a test document for us as: 2. Insert table into it 3. Add data to the table. Are not enough for us to do anything - we might spend hours "adding data" and testing based on this and get nowhere. Please provide us with a test document that we can just insert rows and see a crash. Once you do so, mark the bug as UNCONFIRMED and we'll try to help
Hi Joel, I completely agree with you. I could have given you the same document I was using. But its a private document. I will try to give you a document where I can reproduce. Here are some questions for the team. 1) Is there any specific requirement for Java version? 2) Is there any way I can enable logging? 3) When the office suite crashes, is there any crash dump that gets created? 4) I see a lot of people reporting the same issue in google. Were they resolved?
One way to deal with confidential information is to do a find/replace and just do a ton of replaces (replace all a's with o's for instance) and then do it a few times to make the document illegible. 1) Is there any specific requirement for Java version? no there shouldn't be 2) Is there any way I can enable logging? http://ask.libreoffice.org/en/question/2044/libreoffice-logging-options/ might help 3) When the office suite crashes, is there any crash dump that gets created? see above :) 4) I see a lot of people reporting the same issue in google. Were they resolved? links?
Sreekanth: you can also use this link https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace to provide more information. Also, could you provide details about jre installed? (1.6, 1.7, 32 or 64 bits) Please, read this Wikipedia page before telling Sun started this project: http://en.wikipedia.org/wiki/StarOffice Anyway, let's focus on the bug.
(This is an automated message.) This bug is not a MAB and in NEEDINFO, thus gradually adjusting priority to high. Please see the QA mailing list or the ESC call minutes for details.
Hi @Sreekanth, any news about this issue, has been solved in some way?
Likely a dupe of fdo#75898, can you retest with a daily build from: http://dev-builds.libreoffice.org/daily/ To see if its still there?
I couldn't reproduce it again and Open office seemed no so usable for me. So I moved to MS-Word as my current project at that time needs those documents to be ready.
Since we do not have a test file, nor is the user willing to test newer version, plus Björn assumes this might be fixed already and be a dupe, and reproducing on Ubuntu 13.10 LO 4.2 did not trigger any crash: setting to WORKSFORME.