Created attachment 71726 [details] Opened is a sample file, but it is happening with any file. Problem description: when double click a file (ODT, DOC... type does not matter) LO opens, show the doc and then crashes. It crashes randomly, I tried with a few different files and with the same file it crashes 80% of times. If the same file is opened through File->Open I have no problem. Steps to reproduce: 1. Create a file (ODT, DOC or whatever is opened by LO) 2. Close all instances of LO 3. Double click the file to open it with LO Current behavior: LO opens, load the file, then crashes Expected behavior: LO opens, load the file, remains opened to work with the file Operating System: Linux (Other)
Juan, Using 4.0.0.0.beta1 I have opened your file about 10 times--five from the commands line and five from Nautilus--without any problem. Each time I see the text and the lines that the text says should be there. Can you please tell us what Linus distro you are using and what file manager you are using. Did you do a "parallel" installation of the beta? Thanks, Terry.
Terry, I'm using elementaryOS Luna Beta 1, $ uname -a Linux jdelacamara-POSITIVO-BGH 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Filemanager is Pantheon Files 0.1. No, I tried to install parallel with no success (desktop integration didn't install). So I deinstalled LibreOffice3 and then installed 4. I ran LO from command line to see messages, but no matters if it crash or not the messages are always the same. So I think they are usual. May I do any other test to collect more info?
(In reply to comment #2) > Terry, > > I'm using elementaryOS Luna Beta 1, > Filemanager is Pantheon Files 0.1. I am not familiar with either that distribution or the file manager. > > No, I tried to install parallel with no success (desktop integration didn't > install). So I deinstalled LibreOffice3 and then installed 4. The lack of desktop integration is deliberate, so that you can keep your installed version for "real" work while you test at the cutting edge. With my failure to see a problem, I have to suspect that something went wrong in the installation or there is something different between our environments. When I have the chance, I shall try to upen your file in a 64-bit Linux. > > I ran LO from command line to see messages, but no matters if it crash or > not the messages are always the same. So I think they are usual. > > May I do any other test to collect more info? Please try soffice --backtrace test_paragraphlines_001.odt and attach the resulting gdbtrace.log. Terry.
Created attachment 71745 [details] gdbtrace for opening odt and docx files from command line
Ok, first: I used: lodev4.0 --backtrace test_paragraphlines_001.odt instead of: soffice --backtrace test_paragraphlines_001.odt Well, running from command line with the backtrace works perfectly. It didn't crash. So I ran a few times with and without the backtrace: lodev4.0 --backtrace test_paragraphlines_001.odt lodev4.0 test_paragraphlines_001.odt Without backtrace it crashed a few times. But this time ODT worked ok in almost all the times. DOCX crashed almost all times. Also double clicking form filemanager LO crashed with almost all the files almost all the times. I'm attaching two files: one for the ODT successful open and the other for the DOCX successful open.
Juan Matías, Alas, I shall have to leave it somebody more knowledgeable to get us any forwarder in this issue. Terry.
@Juan Matías de la Cámara Beovide: I doubt that it's related, but it is an easy test: Can you try with a new user profile <https://wiki.documentfoundation.org/UserProfile#User_profile_location> And you should not use "doc" as abbreviation for document, this string should be reserved for the MS WORD file format.
Juan: I don't find anything useful in your bt. Just for the try, could you retrieve a bt by following this link (https://wiki.documentfoundation.org/BugReport#How_to_get_a_backtrace_.28on_Linux.29)
I'm going to mark this as NEEDINFO as we need a bt and no one has this distro or file browser. Leaving in UNCONFIRMED won't help anyone. Juan - are you able to do a backtrace? If not then please do the following: 1. Test on RC2 that is coming out shortly, let us know if the problem is fixed then. If it's not, please reopen this bug as UNCONFIRMED and I will go ahead and try out your distribution (I really am hoping to avoid this). We haven't seen any behavior like this on any other distro. Thanks for your help
Eight months with no action; I am closing the bug report. Juan, If you want to keep working on this, please set the status back to NEEDINFO. Terry.