Bug 104896 - Writer crashes on start, fails parsing registrymodifications.xcu
Summary: Writer crashes on start, fails parsing registrymodifications.xcu
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.3.3 release
Hardware: All All
: medium normal
Assignee: Yan Pas
URL:
Whiteboard:
Keywords: corruptProfile, wantBacktrace
Depends on:
Blocks:
 
Reported: 2016-12-23 21:24 UTC by Yan Pas
Modified: 2017-02-18 17:47 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
.config/libreoffice/4/user/ (1.69 MB, application/xml)
2016-12-31 12:30 UTC, Yan Pas
Details
log (62.90 KB, text/plain)
2017-02-12 19:43 UTC, Yan Pas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yan Pas 2016-12-23 21:24:39 UTC
Description:
Once I've tried to open one docx document LibreOffice Writer has begun crashing. Other LO components (Calc etc) worked fine. I've renamed registrymodifications.xcu and LO started to work fine again. I've saved old ones, but wouldn't like to upload it here in the public area. I can send it to email to someone.

Steps to Reproduce:
replace your registrymodifications.xcu and try to launch.

Actual Results:  
crash

Expected Results:
no crash


Reproducible: Always

User Profile Reset: No

Additional Info:
Linux Mint 18, kernel 4.4


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Comment 1 Xisco Faulí 2016-12-26 13:01:52 UTC Comment hidden (obsolete)
Comment 2 Julien Nabet 2016-12-26 22:46:29 UTC
You don't want to attach your docx file, your buggy registrymodifications.xcu or both?

About registrymodifications.xcu, could you "tidy format" it and compare it with a brand new registrymodifications.xcu ?
Comment 3 Yan Pas 2016-12-31 12:30:15 UTC
Created attachment 130054 [details]
.config/libreoffice/4/user/
Comment 4 Xisco Faulí 2017-01-12 11:49:31 UTC Comment hidden (obsolete)
Comment 5 Yan Pas 2017-01-14 14:30:24 UTC
this config file works ok even with LO 5.1 on clear virtualbox. I guess that crash depends not only on this xml.
5.4 also works fine
Comment 6 Buovjaga 2017-01-24 07:25:51 UTC
Could you try getting a backtrace of the crash by downloading and extracting http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF-dbg/current/

and running
program/soffice --backtrace

Requirement is you have gdb installed

The Linux-rpm_deb-x86_64@70-TDF-dbg package includes debug symbols, but otherwise these instructions apply: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information
Comment 7 Xisco Faulí 2017-02-07 14:02:24 UTC
Setting to NEEDINFO until we get feedback from the reporter
Comment 8 Yan Pas 2017-02-12 19:43:07 UTC
Created attachment 131154 [details]
log

I cannot observe crash anymore, only a lot of warnings. And after I open writer I see bibliography dialog
Comment 9 Buovjaga 2017-02-13 17:07:51 UTC
(In reply to Yan Pas from comment #8)
> Created attachment 131154 [details]
> log
> 
> I cannot observe crash anymore, only a lot of warnings. And after I open
> writer I see bibliography dialog

I showed it in IRC and a dev commented:

that looks like a LibreOffice vs LibreOfficeDev mismatch 

user changed some color settings when using LibreOffice, then copied the registrymodifications.xcu over to a LibreOfficeDev installation?
Comment 10 Stephan Bergmann 2017-02-13 17:15:57 UTC
(In reply to Yan Pas from comment #8)
> Created attachment 131154 [details]
> log
> 
> I cannot observe crash anymore, only a lot of warnings.

(Those warnings mentioning "unknown item "/org.openoffice.Office.UI/ColorScheme/ColorSchemes/org.openoffice.Office.UI:ColorScheme['LibreOffice']/" look like they are caused by copying a registrymodifications.xcu from a LibreOffice to a LibreOfficeDev installation.  Whatever color setting modifications you made in the former will not be there in the latter, but otherwise those warnings are harmless.)
Comment 11 Buovjaga 2017-02-18 17:47:12 UTC
As Yan cannot repro the crash anymore and the warnings are harmless and expected, I will close as WFM.