Bug#762651: libreoffice-core: soffice cores during start with SIGSEGV

[Rene Engelhard <rene@debian.org>]

severity 762651 important
retitle 762651 libreoffice-core: SIGSEGV during start with (some9) recovery items
thanks

> After some comparison and analyze, it looks that the cause is in the file 'registrymodifications.xcu'.  When using the following content, soffice cores:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <oor:items xmlns:oor="http://openoffice.org/2001/registry"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> <item oor:path="/org.openoffice.Office.Recovery/RecoveryList"><node oor:name="recovery_item_2" oor:op="replace"><prop oor:name="DocumentState" oor:op="fuse"><value>0</value></prop><prop oor:name="Filter" oor:op="fuse"><value>draw8</value></prop><prop oor:name="Module" oor:op="fuse"><value>com.sun.star.drawing.DrawingDocument</value></prop><prop oor:name="OriginalURL" oor:op="fuse"><value></value></prop><prop oor:name="TempURL" oor:op="fuse"><value></value></prop><prop oor:name="TemplateURL" oor:op="fuse"><value></value></prop><prop oor:name="Title" oor:op="fuse"><value>Untitled 2</value></prop><prop oor:name="ViewNames" oor:op="fuse"><value><it>Default</it></value></prop></node></item>
> <item oor:path="/org.openoffice.Office.Recovery/RecoveryList"><node oor:name="recovery_item_3" oor:op="remove"/></item>
> <item oor:path="/org.openoffice.Office.Recovery/RecoveryList"><node oor:name="recovery_item_1" oor:op="remove"/></item>
> <item oor:path="/org.openoffice.Office.Recovery/RecoveryInfo"><prop oor:name="Crashed" oor:op="fuse"><value>false</value></prop></item>
> <item oor:path="/org.openoffice.Office.Recovery/RecoveryInfo"><prop oor:name="SessionData" oor:op="fuse"><value>true</value></prop></item>

Did you have pending recoveriies before? Froma hard kill or a crash before?

> It might be a coincidence that some packages were updated at the same time.  (If you still want, I can send you the list.)

For reference, yes, ut I tend to agree it's probably a coincidence.

> I'm not sure if 'grave' is still valid: a workaround is to open the config file and delete the appropriate files. Nevertheless, it's not 'nice'....

Indeed. Downgrading.

Regards,

Rene