<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> changed <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WORKSFORME - Font colors dropdown corrupted after upgrade to LO 5.4.7.2" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117959">bug 117959</a> <table border="1" cellspacing="0" cellpadding="8"> <tr> <th>What</th> <th>Removed</th> <th>Added</th> </tr> <tr> <td style="text-align:right;">Resolution</td> <td>--- </td> <td>WORKSFORME </td> </tr> <tr> <td style="text-align:right;">Status</td> <td>UNCONFIRMED </td> <td>RESOLVED </td> </tr></table> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WORKSFORME - Font colors dropdown corrupted after upgrade to LO 5.4.7.2" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117959#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WORKSFORME - Font colors dropdown corrupted after upgrade to LO 5.4.7.2" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117959">bug 117959</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=117959#c3">comment #3</a>) > > The listed cmyk, palette, gallery, web, and scribus fonts were all removed Sorry, change that this is a color palette and not a font issue =) s/cmyk, palette, gallery, web, and scribus fonts/cmyk, gallery, web and scribus palettes/ (In reply to Martin Terry from <a href="show_bug.cgi?id=117959#c4">comment #4</a>) > ... > Resetting my profile by deleting the 'registrymodifications.xcu' file did > not have any effect. > > Howver, when I moved some of the redundant font files you mentioned in > my<user>\config folder to a different location and ran LO in normal mode the > drop down list of fonts looked better, without the duplicates and redundant > ones. The sole 'standard' option now shows a full palette of colours rather > than whilte space. For a default ALLUSER installation LibreOffice palettes are found in the <installDir>/share/palette directory... The file "extension" for color palettes is .soc, but some others are used by other components. .sob (zip containing .png, "bitmaps") .sod (XML, "dashes") .soe (XML, "line ends?") .sog (XML, "gradients") .soh (XML, "hatches") .sop (zip containing .png, "patterns") Users can add their own .soc palettes into their own <user>\config folder and they will show in the UI for their own use. Or, they can add them to the share\palettes folder for general use on a shared computer. Otherwise, the "custom" palette from the GUI is held as "UserColors" stanzas in the per user profile "registrymodifications.xcu"--both recently used colors and colors available from the custom palette are recorded to profile. At the moment only the Area fill dialog will allow you to create the colors that will show as swatches in the "custom" palette. While the "recent" color bar swatches will cycle as a stack on use. > > Could this be a problem with the upgrade? If some fonts were removed before > 5.3.0 why were these files still in my config folder? Just a thought... > Possibly. Suspect at some point you'd done a non-administrator install "Only for me", and then with the 5.4.7 install for "Anyone who uses this computer". So you'd had a bad profile for some time--just more noticeable with removal of some of the palettes (<a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Remove dispensable palettes" href="show_bug.cgi?id=104047">bug 104047</a>, <a class="bz_bug_link bz_status_NEW " title="NEW - Remove color palettes Breeze, Tango and LibreOffice" href="show_bug.cgi?id=113858">bug 113858</a>). Creating a new user profile (deleting renaming %APPDATA%\LibreOffice\User\4) should cleanly resolve this or similar issues.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>