Bug 155660 - Custom colors dialog is not shown
Summary: Custom colors dialog is not shown
Status: RESOLVED DUPLICATE of bug 155543
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.6.0.0 alpha1+
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2023-06-03 10:20 UTC by Stefan_Lange_KA@T-Online.de
Modified: 2023-06-07 14:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of Font Color menu (39.09 KB, image/png)
2023-06-06 11:14 UTC, Joseph Walton
Details
Screenshot in german version (30.65 KB, image/png)
2023-06-06 11:38 UTC, Stefan_Lange_KA@T-Online.de
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan_Lange_KA@T-Online.de 2023-06-03 10:20:08 UTC
The dialog to create or define user defined colors for text color or background color is not shown at least in Writer and in Calc.
Reproduce the bug:
- open an existing document (odt, ods, ...) or create a new document
- select any existing characters / if the document is new enter any characters before
- try to change the font color or the background color e.g. by Format -> Character -> Font effects -> Font color
- click on "User defined color"
Expected result: The dialog to define or select user defined colors is shown.
Actual result: Nothing happens!

Behavior bibisected, result: 93d21ef56334bf2f9550cdd6856e3358a48f8eb3 is the first bad commit
commit 93d21ef56334bf2f9550cdd6856e3358a48f8eb3
Author: Norbert Thiebaud <nthiebaud@gmail.com>
Date:   Thu Apr 20 23:30:27 2023 -0700

    source 901360967dde5d3948d4a28d156ad526b0802ca1

    source 901360967dde5d3948d4a28d156ad526b0802ca1

 instdir/program/services/services.rdb | 2 +-
 instdir/program/setup.ini             | 2 +-
 instdir/program/version.ini           | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
Comment 1 Joseph Walton 2023-06-06 11:14:04 UTC
Thank you for reporting the bug. I can confirm that the bug is present in
Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: f65949452bd3a61f0eeb1b95db7ec2ce2e1c59f3
CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: CL threaded

I followed your exact steps in both Writer and Calc and got the same results as you, one small note though is I couldn't find a 'User defined color' but there was a 'Custom Color' button. Before I change the status to NEW, please could you look at the attached file and confirm that 'Custom Color' is the same button you are referring to in your report?
Comment 2 Joseph Walton 2023-06-06 11:14:43 UTC
Created attachment 187749 [details]
Screenshot of Font Color menu
Comment 3 Stefan_Lange_KA@T-Online.de 2023-06-06 11:38:24 UTC
Created attachment 187750 [details]
Screenshot in german version

It's the same button. In German the name is "Benutzerdefinierte Farbe" and I have translated to "User defined color" instead of "Custom color".
Comment 4 Joseph Walton 2023-06-06 11:41:06 UTC
(In reply to Stefan_Lange_KA@T-Online.de from comment #3)
> Created attachment 187750 [details]
> Screenshot in german version
> 
> It's the same button. In German the name is "Benutzerdefinierte Farbe" and I
> have translated to "User defined color" instead of "Custom color".

Thank you very much for confirming, I have changed the status to new.
Comment 5 Stefan_Lange_KA@T-Online.de 2023-06-06 14:25:51 UTC
In the bug report I have also reported the first bad commit as the result of bibisecting the bug.
Therefore I guess the keywords "bisect" and/or "bibisect" (What is the difference?) should/could be set and also the keyword "regression". Is this OK?
Comment 6 Stéphane Guillou (stragu) 2023-06-07 14:43:42 UTC
Thank you both!
This had already been reported in bug 155543, and is already fixed in master.
Glad we've got many eyes spotting the same issues! :)

(In reply to Stefan_Lange_KA@T-Online.de from comment #5)
> In the bug report I have also reported the first bad commit as the result of
> bibisecting the bug.
> Therefore I guess the keywords "bisect" and/or "bibisect" (What is the
> difference?) should/could be set and also the keyword "regression". Is this
> OK?

That's correct, both should be added when you arrive to a precise commit with a bibisect repository, along with the "regression" keyword. (Sometimes a bibisect only leads to a _range_ of commits. In that case, you wouldn't add the "bisected" keyword.)
Please see the difference between the two keywords here: https://wiki.documentfoundation.org/QA/Bibisect#General_Instructions

*** This bug has been marked as a duplicate of bug 155543 ***