--- Comment #6 from Keith N. McKenna <> ---
(In reply to Stephen L'Allier from comment #1)
> I have successfully replicated this issue. Additionally, I have also found
> the corrupted lines of registrymodifications.xcu (which I will hereby refer
> to as the AOO configuration file) that are causing the Styles and Formatting
> to not open when F11 is pressed. Below I have listed the specifications of
> my test machine, the steps taken to reproduce the bug, and information about
> the corrupted lines in the AOO configuration file.
> Test Machine Specifications
> AOO Version: 4.0.1
> CPU: AMD FX-8350 4.0 GHz
> GPU: AMD Radeon HD 7870
> RAM: 8 GB DDR4
> OS: Windows 10 w/ Anniversary Update
> Steps taken to reproduce failure
> 1.    Open AOO Writer and press F11 to ensure Styles and Formatting window
> opens regularly.
> 2.    Close AOO Writer.
> 3.    Download potentially corrupted AOO file from the Bug Report.
> 4.    Replace current AOO configuration file with the downloaded one while
> OpenOffice Writer is closed. Current file located at:
> C:\Users\USER\AppData\Roaming\OpenOffice\4\user\registrymodifcations.xcu
> 5.    Open AOO Writer.
> 6.    Press F11 and see that the Styles and Formatting window does not appear.
> 7.    Close AOO Writer.
> 8.    Replace corrupted AOO configuration file with the old one.
> 9.    Open AOO Writer.
> 10.   Pres F11 and see that the Styles and Formatting windows appears as it is
> supposed to.
> Steps taken to fix failure
> I noticed that the size of the corrupted AOO configuration file was much
> larger than my original one, so I decided to open it to look inside. It is
> in XML format, but I had to use an XML Formatter online in order to get the
> indentation to show up. After doing so, the number of lines in the corrupted
> file was 8148. For comparison, my fresh AOO configuration file was 372 lines.
> With such a drastic difference in size, I knew the issue could be anywhere.
> I decided to manually perform a Binary Search on the corrupted file in order
> to see if I could isolate the corrupted lines. I did so by repeating the
> following steps until finding the corrupted lines.
> 1.    Remove one half of the N lines (where N is 8148 to start) from the
> corrupted AOO configuration file.
> 2.    Save the file.
> 3.    Open AOO Writer.
> 4.    Press F11 to see if the problem is fixed.
> 5.    If the problem is fixed, the sample size of the lines is reduced to only
> the half that was tested, as the corrupted lines are in that sample. N is
> half the size that it was. Repeat steps 1-4 until the corrupted lines are
> found.
> 6.    If the problem is not fixed, perform steps 1-4 on the other half of the
> lines and proceed.
> This method worked excellently, and after following the procedure outlined
> above, I narrowed down the corrupted lines to lines 6189-6193. Those lines
> are pasted below.
> <item
> oor:path="/org.openoffice.Office.Views/Windows/org.openoffice.Office.Views:
> WindowType['5539']/UserData">
>     <prop oor:name="Data" oor:op="fuse" oor:type="xs:string">
>         <value>V2,H,0,AL:(5,16,0/1/1/430,1;917)</value>
>     </prop>
> </item>
> I experimented with leaving different parts of this item entry in place and
> only removing small parts. If I removed the “/UserData” at the end of the
> oor:path, F11 began functioning correctly again. I did a search for the
> string “/UserData” in the configuration file and found one more instance of
> it, on line 6014. I removed that one as well, and found that a sidepane that
> had been hidden was no longer hidden.
> Because the corrupted AOO configuration file was so large, it is possibly
> filled with other issues as well. Some of the effects of these changes are
> noticeable when comparing the screenshots I have attached. Hopefully this
> new information helps to track down the bug that is causing the lines above
> in the AOO configuration file to be corrupted.

Stephen I would strongly urge you to subscribe to the QA mailing list and ask
to be added to the QA team on Bugzilla. This will allow you to set the Status
of Items as Confirmed. Also if you have not already read through the
Orientation Guide for QA at

You are receiving this mail because:
You are the assignee for the issue.

Reply via email to