Crashes without warning or error messages. This happens on Linux Mint 15 and Ubuntu Studio 13.10.
Steps to reproduce:
1. Have Writer open.
2. Watch it crash as it runs.
I don't expect it to crash.
Please, give me the knowledge to obtain the correct information from my system regarding the crash. I would love to give you guys information about the problem. I just need to know where to get the information that you need. This error has been happening on all the versions of Writer for Linux Mint 15 and Ubuntu Studio 13.10 in the last year. Help me, help you.
Basically the crash happens randomly and display no error message. I want to use your product but it is becoming too difficult due to data loss to continue.
Operating System: Ubuntu
Version: 126.96.36.199 release
(In reply to comment #0)
> Problem description:
> Crashes without warning or error messages. This happens on Linux Mint 15 and
> Ubuntu Studio 13.10.
> Steps to reproduce:
> 1. Have Writer open.
> 2. Watch it crash as it runs.
crashes while typing or even being inactive?
- did you install any LO extensions?
- could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and give it a new try?
If you still reproduce this, could you try to retrieve a backtrace by following this?
(In reply to comment #0)
I have this problem as well. Writer crashes at random times, losing any unsaved data. The crash only seems to occur if I am in the process of working within the Writer window - if I am not typing or otherwise performing actions, it will not crash. The window will gray out, becoming unresponsive, and close. I cannot find any common repeatable process that causes the crash. The first time it crashes, Apport will launch ("Ubuntu 13.10 has experienced an internal error") and send an error report, but subsequent crashes do not do that. The next time I get the Apport error reporting, I will copy and paste the information here.
Operating System: Ubuntu 13.10 64-bit
Note: I also had this problem prior to upgrading to LibreOffice 4.2. It began when I did a fresh install of Ubuntu 13.10.
ianthealy: could you apply what I indicated at comment 2?
From what I can see about Backtrace, I need to be able to reproduce the crash. It happens at random times. Should I just enable backtrace and keep working until I get a crash?
If the pb happens about every 10 or 20 mins, it could worth it.
You could try the LO directory reset part first.
I tried resetting the LO directory profile as indicated in Comment 2. At first I thought that had resolved the problem, as it didn't return for several sessions (including one with the backtrace running). Then it happened again tonight. I'm including some of the info from the crash report (which I can't seem to copy and paste so I'm typing it out)
Sorry, Ubuntu 13.10 has experienced an internal error.
libreoffice-core 1:4.2.1-0ubuntu1~saucy [origin: LP-PPA-libreoffice-libreoffice-4-2]
soffice.bin crashed with SIGSEGV in Window::Flush()
Mon Mar 3 22:09:37 2014
Installed on 2014-02-13 (19 days ago)
Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
/usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5
PATH=(custom, no user)
Ubuntu 3.11.0-17.31-generic 188.8.131.52
Segfault happened at: 0x7f6d454bbae32 <Window::Flush()+99>: mov 0x18(%rax),%rdi
PC (0x7f6d454bbae3) ok
source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
reading NULL VMA
Linux 3.11.0-17-generic x86_64
This is not an official Ubuntu package. Please remove any third party package and try again.
No upgrade log present (probably fresh install)
adm cdrom dip lpadmin plugdev sambashare sudo
Does this mean anything to anyone?
Created attachment 95065 [details]
Backtrace log of crash related to Bug 74305
ianthealy: thank you for your feedback and your bt
Caolán: I don't know if the original reporter of the bug and ianthealy encounter the same bug, but could http://cgit.freedesktop.org/libreoffice/core/commit/?id=1ec2880679d88c89901ce00fe30dd78e584f6960 may help for ianthealy's case (considering the bt he managed to retrieve) ?
caolanm->Julien: Yeah, that bt is the same problem that that commit fixes. Given that's the concrete piece of info here I'll claim this is fixed by that.
Thank you Caolán for your feedback.
I put the targets:
- 4.2.3 (since http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-4-2&id=1ec2880679d88c89901ce00fe30dd78e584f6960)
Last question: never having dealt with bugs/patches before this problem, what is my next step to repair the problem? Download and install the patch from http://cgit.freedesktop.org/libreoffice/core/commit/?id=1ec2880679d88c89901ce00fe30dd78e584f6960 ?
no, you should wait that the release with that patch is available for download.
in this case 4.2.3 which is scheduled in april 2014.
more details here: https://wiki.documentfoundation.org/ReleasePlan
if you cannot wait you can also download a pre-release version of LibO 4.2.3 from here: http://dev-builds.libreoffice.org/daily/libreoffice-4-2/
it should already have that patch inside