Bug 102282 - Crash at start
Summary: Crash at start
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 103732 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-19 13:52 UTC by Hector Acevedo
Modified: 2017-02-16 15:39 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
log file (611 bytes, text/x-log)
2016-09-23 02:37 UTC, Hector Acevedo
Details
log file (611 bytes, text/x-log)
2016-09-23 02:42 UTC, Hector Acevedo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hector Acevedo 2016-09-19 13:52:44 UTC
I have just purchased a new Dell XPS 13 9350 ultrabook (with 256 GB SSD) and installed a fresh Lubuntu 16.04 LTS (AMD64). I use Google Drive for storing all my .odt and .ods documents.

Libre Office will start correctly but most of the times will shut down and reboot the system.

If other software is used beforehand, then it could happen that LibreOffice works normally. In fact I was able to create and edit several documents. However it is difficult to find a pattern for this strange behaviour.

I was unable to find a similar report in the knowledge base. Will appreciate your help.

Thank you
Comment 1 Julien Nabet 2016-09-20 19:23:37 UTC
Which LO version do you use?

Do you use reproduce this if you use local hard disk?
Would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Comment 2 Hector Acevedo 2016-09-20 21:21:44 UTC
Dear Julien:

I followed the instructions of the link you supplied and had to install soffice-common. However, after requesting a backtgrace I get the following errror:

Error: Can't find the tool "gdb", --backtrace option will be ignored.

The LO version is 5.2.1.2.

I have now successfully opened files stored in the machine's SSD and also directly from my Google Drive account. I decided to clear the list of opened files and retested without any problems. 

Could the installarion of soffice-common be the cure?

I'll keep on testing and inform you of the results. Same if the problem reappears.

Thank you

Héctor
Comment 3 Julien Nabet 2016-09-21 10:38:29 UTC
To install gdb, try this:
sudo apt-get install gdb

Let's put WFM for the moment, don't hesitate to reopen this tracker if you still reproduce the problem.
Comment 4 Hector Acevedo 2016-09-23 02:37:01 UTC
Created attachment 127565 [details]
log file
Comment 5 Hector Acevedo 2016-09-23 02:42:19 UTC
Created attachment 127566 [details]
log file

The installation of soffice-common partially resolved the problem and several writer documents could be opened, edited and saved with apparent normality.

However, if the main window is opened and a file from the list is not selected immediately, after some time moving the cursor over the window will again blank the screen and reboot the system.

I am adding gdbtrace.log as an attachment.
Comment 6 Julien Nabet 2016-09-23 05:06:41 UTC
Comment on attachment 127565 [details]
log file

No stack here
Comment 7 Julien Nabet 2016-09-23 05:06:58 UTC
Comment on attachment 127566 [details]
log file

No stack here too
Comment 8 Julien Nabet 2016-09-23 05:07:36 UTC
Ok let's put this one to UNCONFIRMED
Comment 9 Xisco Faulí 2016-09-23 08:21:40 UTC
let's put it to NEEDINFO
Comment 10 Hector Acevedo 2016-10-14 19:33:27 UTC
(In reply to Xisco Faulí from comment #9)
> let's put it to NEEDINFO

Which info do you need?
Comment 11 Julien Nabet 2016-11-06 07:50:15 UTC
*** Bug 103732 has been marked as a duplicate of this bug. ***
Comment 12 Julien Nabet 2016-11-06 08:36:32 UTC
Could you update to last stable LO version 5.2.2?

For the test, could you rename your LO directory profile (see 
https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) and give a new try?

Just to be sure, do you reproduce this with documents on local hard disk? (after having cleaned the menu recent documents)
Comment 13 Hector Acevedo 2016-11-27 02:12:17 UTC
This is to inform you that upgrading to Version 5.2.3.3 has solved the problem. I purposely delayed providing the information on account of extensive testing to ascertain that the issue indeed disappeared.
Comment 14 Julien Nabet 2016-11-27 08:55:57 UTC
Thank you Hector for your feedback.
Let's put this one to WFM then.