If I leave LibreOffice with a document open for a while (doc, calc, any type), then resume typing in that document, it immediately crashes. LibreOffice 3.3.2 OOO330m19 (Build:202) tag libreoffice-3.3.2.2, Ubuntu package 1:3.3.2-1ubuntu2~maverick1 uname -a Linux will 2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64 GNU/Linux dmesg output: [24354.244064] soffice.bin[4180] general protection ip:7fa9d70d9f0e sp:7fff592c1a80 error:0 in libuno_cppuhelpergcc3.so.3[7fa9d70ba000+9e000] From postings it seems this also affects 32 bit users and is not specific to LO either. It was happening to me on OOO before I migrated.
Ubuntu specific, for Björn?
Just to clarify: by IDLE I mean not using LO application - I go off and do other tasks on other apps. Then when I come back and resume typing into LO it crashes. Other apps all remain stable.
Created attachment 48444 [details] gdb backtrace and all thread backtrace remember the bug : work sometime on OOo, then do something else, come back after a while on OOo -> crash (sometime). or do CTRL+s after having spent sometime on other stuff -> crash(sometime). From my past experience, this kind of bug started first with the version 3 of openoffice. a try with IBM lotus symphony was resulting in the same crash!!! finally I though libreoffice was not affected... but that is not the case. I use ubuntu 10.10 (32b) when the problem started with compiz. (disabling opengl for OOO doesn't affect the bug). I now have on ubuntu 10.10 libreoffice 3.1 and it seems not to be affected by this bug (I was not able to reproduce it). I also recently got Ubuntu 10.04.... libreoffice 3.3 crash... 3.4 also!!! The backtrace seems explicit... the trouble come from uno, ure. Except that is a .net like stuff, I have no more idea how it works, and what part it play in Libreoffice, OOo or lotus symphony. However it seems related to file io with an exception badly uncatched prducing a SIGSEGV. My guess is that this bug should be redirected to uno framwork. Also ubuntu distro might also play a role in it. If you need testing for this bug, I have a document (but professional, not to share) that seems to trigger the bug almost garanted within an hour.
(In reply to comment #3) > Created an attachment (id=48444) [details] > gdb backtrace and all thread backtrace > > remember the bug : work sometime on OOo, then do something else, come back > after a while on OOo -> crash (sometime). or do CTRL+s after having spent > sometime on other stuff -> crash(sometime). > > From my past experience, this kind of bug started first with the version 3 of > openoffice. a try with IBM lotus symphony was resulting in the same crash!!! > finally I though libreoffice was not affected... but that is not the case. > > I use ubuntu 10.10 (32b) when the problem started with compiz. (disabling > opengl for OOO doesn't affect the bug). > I now have on ubuntu 10.10 libreoffice 3.1 and it seems not to be affected by > this bug (I was not able to reproduce it). > I also recently got Ubuntu 10.04.... libreoffice 3.3 crash... 3.4 also!!! OOOps, mistake in ubuntu version read Ubuntu 10.04 as 11.04, sorry...
gdb backtrace and valgrind from 10.10 (Mint) 64 bit.
Created attachment 49669 [details] gdb backtrace taken from 10.10 (mint), 64bit 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linuxlibreoffice-core 1:3.3.2-1ubuntu2~maverick1
Created attachment 49670 [details] valgrind taken from 10.10 (mint), 64bit 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linuxlibreoffice-core 1:3.3.2-1ubuntu2~maverick1
I am seeing the exact same behavior for many months, also since OOo. I have previously submitted two gdb traces which might be useful to people debugging this issue - below. I am seeing this issue both in Writer and Impress very often, and it makes working with these applications extremely unpredictable and unpleasant. Maybe 50% of the times I start the application, I need to go through document recovery first. https://bugs.freedesktop.org/show_bug.cgi?id=35424
not really an libreoffice bug, but an issue with encrypted home/swap.
*** Bug 35424 has been marked as a duplicate of this bug. ***
(see https://launchpad.net/bugs/745836 for details)
*** Bug 33025 has been marked as a duplicate of this bug. ***
*** Bug 40766 has been marked as a duplicate of this bug. ***
closing