Steps how to reproduce with Server Installation of "LibreOffice 3.6.0beta1 German UI/Locale [Build-ID: 1f1cdd8] on German WIN7 Home Premium (64bit): 1. download / open Sample document <https://issues.apache.org/ooo/attachment.cgi?id=77876> from a.m. AOOo Bug 2. <f11> to show styles if necessary 3. Click icon to show 'Page Styles' 4. Double click "Envelope" Expected: Style changes Actual: Crash Already crashes OOo 3.2, so seems inherited from OOo. Currently only reproducible with particular sample document, other documents do not crash for me. So below critical.
NEW and OS=All due to AOOo issue Very old bug, so IMHO not MAB @Michael: Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug or forward the Bug if it's not your turf.
Created attachment 62954 [details] Bug 51001 - WinDbg session with FAILED_SOURCE_CODE Confirmed with: LO 3.5.4.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Crashed. Attached full WinDbg session with FAILED_SOURCE_CODE.
On pc Debian x86-64, with master sources updated today, I didn't reproduce the crash. Noticed these logs on console : warn:legacy.tools:5922:1:/home/julien/compile-libreoffice/libo/sfx2/source/dialog/filtergrouping.cxx:371: ReferToFilterEntry::operator(): already have an element for this name! warn:legacy.tools:5922:1:/home/julien/compile-libreoffice/libo/sfx2/source/dialog/filtergrouping.cxx:371: ReferToFilterEntry::operator(): already have an element for this name! warn:legacy.tools:5922:1:/home/julien/compile-libreoffice/libo/sfx2/source/dialog/filtergrouping.cxx:371: ReferToFilterEntry::operator(): already have an element for this name! warn:legacy.tools:5922:1:/home/julien/compile-libreoffice/libo/sfx2/source/dialog/filtergrouping.cxx:371: ReferToFilterEntry::operator(): already have an element for this name! warn:legacy.tools:5922:1:/home/julien/compile-libreoffice/libo/sfx2/source/dialog/filtergrouping.cxx:371: ReferToFilterEntry::operator(): already have an element for this name! warn:legacy.osl:5922:1:/home/julien/compile-libreoffice/libo/xmloff/source/core/xmlimp.cxx:1315: duplicate style name warn:legacy.osl:5922:1:/home/julien/compile-libreoffice/libo/xmloff/source/core/xmlimp.cxx:1315: duplicate style name warn:svx:5922:1:/home/julien/compile-libreoffice/libo/svx/source/xml/xmlgrhlp.cxx:449: SvXMLGraphicHelper::ImplInsertGraphicURL: invalid scheme: vnd.sun.star.Package: warn:legacy.osl:5922:1:/home/julien/compile-libreoffice/libo/sw/source/core/unocore/unochart.cxx:1078: XLabeledDataSequence in data source contains 0 entries warn:legacy.osl:5922:1:/home/julien/compile-libreoffice/libo/sw/source/core/unocore/unochart.cxx:1078: XLabeledDataSequence in data source contains 0 entries warn:legacy.osl:5922:1:/home/julien/compile-libreoffice/libo/chart2/source/tools/WrappedPropertySet.cxx:267: Exception caught. Type: N3com3sun4star5beans24UnknownPropertyExceptionE, Message: warn:legacy.osl:5922:1:/home/julien/compile-libreoffice/libo/chart2/source/tools/WrappedPropertySet.cxx:272: unknown property warn:legacy.tools:5922:1:/home/julien/compile-libreoffice/libo/xmloff/source/chart/XMLChartStyleContext.cxx:119: unknown property exception -> shape style not completly imported for chart style warn:legacy.osl:5922:1:/home/julien/compile-libreoffice/libo/sw/source/core/unocore/unochart.cxx:1078: XLabeledDataSequence in data source contains 0 entries
https://issues.apache.org/ooo/show_bug.cgi?id=119654 status: RESOLVED FIXED commit http://svn.apache.org/viewvc?view=revision&revision=1349168
not reproducible with LO 4.0.2.2 (Win7 Home, 64bit) I would suppose that this bug was resolved in the meantime. Can anybody else confirm this? If yes, then I would propose to close this issue.
On pc Debian x86-64 with master sources updated today, I don't reproduce this. The problem is I wasn't able to reproduce last time (perhaps Windows only bug) On Win7 with LO 4.0.2.2 (French localization), I've got 2 styles for paragraph styles and 0 for others! So I can't even try to reproduce this case. bfoman: could you give an update? (Have you got the styles and do you still have the crash)
(In reply to comment #6) > bfoman: could you give an update? (Have you got the styles and do you still > have the crash) Checked with: LO 4.0.2.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Could not reproduce. Seems to be fixed.
bfoman: great! Thank you for your feedback! I put it as WFM since there's no specifix fix identified on LO repo.