“Whiteboard: QA:needsComment”
What other comment is needed from the reporter? I can’t find an explanation in the Whiteboard page. The steps are explained. The bug rather needs someone to fix it.

(In reply to maison from comment #1)
> “Whiteboard: QA:needsComment”
> What other comment is needed from the reporter? I can’t find an explanation
> in the Whiteboard page. The steps are explained. The bug rather needs
> someone to fix it.

QA:needsComment is for QA, not for the reporter.

Hello Maison.

Thank you for reporting the bug.  I was not able to reproduce the bug using the following versions:


Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a834bbad8295cba0ca88a91a524aad48640271ec
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded


Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded


Kind Regards

@maison, Please open LO, menu help > about. Click the icon in the middle of the dialog. Then come back to the bug report and add a comment. Pressing [CTRL]+[V] should paste the info in the comment.

(In reply to maison from comment #5)
> CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Maybe this happens only in Windows Seven (?).

Nope, otherwise I would have mentioned. Windows 10 also.

(In reply to maison from comment #7)
> Nope, otherwise I would have mentioned. Windows 10 also.

I just raised the potential question, according to the info you posted in comment 5. It was an attempt to try to narrow down the situation so as to replicate the issue, by someone with a similar context.

If you can replicate the problem under Windows 10, please paste here that info. And if you test this under Windows 10 and you cannot replicate this problem, please add such details too.

BTW, which type of toolbar/UI are you using? Is it the standard UI, or some other? (Menu View > User Interface)

Have you tried menu Help > Restart in Safe Mode? (I would suggest a backup of your profile before resetting to factory default.)

(In reply to maison from comment #9)
> So, it’s not the profile. It’s the one toolbar interface that resets the
> colours and maybe who knows what other settings.

Again, have you tested different UI variants (menu View > UI Interface)? Does it happen with all of them? Or only with some of them? Which ones?

You still haven’t pasted the info when running this under Windows 10 (according to your comment 7), and whether you can replicate the exact same behavior, or there is any difference there.

ady, I don’t understand why you are asking for things again and again.
What brought the pasted text of what I have entered yet?

I’m not logged on this website from Win 10 and it’s worthless to just copy things from one to the other without drawing a conclusion from the previous one.

Should I keep testing more and more? I gave a reproducible way. Can you rather confirm and take the bug for fixing? Where is its origin? Then we can start testing according to where it originates rather than keep shooting in the air.

(In reply to maison from comment #11)
> ady, I don’t understand why you are asking for things again and again.

Because you answered that you can also reproduce the behavior in win10, not just in win7, but did not provide the info I requested previously, and then you mentioned the standard toolbar, but didn't answer what I asked about other UIs.

I am trying to narrow down the context, because I was not able to reproduce it. With additional details (whether from your own tests, or from other users), we might be able to find out in which context or which conditions are necessary to trigger the problem. Until this moment, I was not able to.

For example, if this happens when using the standard toolbar, but not with Notebook (or some other) UI, then we can retest under that particular UI.

Or perhaps this happens under a certain locale, but not with English (US), as another random example.

If, instead of testing different variables, you are happy to wait until someone by chance finds this report and, by chance, is able to replicate it, that's fine, let's wait.

There might be some setting in Accessibility, or in View, or... that changes the behavior. Yes, it might sound as guesses, but it is not completely uneducated random guess. Maybe someone else might have a better idea on how to trigger the reported behavior.