Description: It seems the new color palettes intoduced in 5.3 did not handle updates properly: I had two named custom colors that were used in documents. After upgrading I noticed that the colors are still in the documents, but when viewing the format properties (font effects' color), I see that the custom color now has lost its name. Looking in the config folder I found the name of my custom color in standard.soc. When I select "standard.soc" as palette, the colors appear with name again. My expectations would be that user-defined colors somehow "overlay" the standard palette (i.e. they should be visible with any palette selected). Also meaning: User-defines colors per palette do not make any sense; instead the use should define a new palette for user colors if needed. Steps to Reproduce: 1. Open an older document that uses named custom-defined colors with a recent LibreOffice Writer 2. Open the format properties that uses the custom-color Actual Results: The color is not part of the current palette, meaning it's name is not available Expected Results: The named color should be available with its name Reproducible: Always User Profile Reset: No Additional Info:
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Dear Ulrich Windl, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Ulrich Windl, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp