Description: In a presentation I want to change a color: Select text, Go to characteristics (Eigenschaften) of the text, open the drop-down for font color and change the color. The icon to font color changes to the new color. So far so good. As soon as I select a different text, the icon for font color switched to a dark red. So I have to open the drop-down again to change color. Expected behaviour: The icon keeps the last selected color to allow quick changing of colors Version: 6.3.2.2 Build-ID: 30(Build:2) on openSUSE Tumbleweed Steps to Reproduce: 1. see above 2. 3. Actual Results: see above Expected Results: see above Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: de Module: PresentationDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Works for me in Version: 6.4.0.0.alpha0+ (x64) Build ID: 137e14ec4c3d3258df3802426b5ffe469f7fbde3 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win;
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
I tried this with a new user / new profile, and the behaviour is the same: - if I change text in the same text block, the color of the icon remains in the new color - If I select text on a different slide, color goes back to dark red
I have also observed this (for at least a year now), e.g. in LibreOffice 6.2.5.2 under Win10 as well as under (Ubuntu) linux.
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
(In reply to Xisco Faulí from comment #5) > You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone > else confirms it. Hardy has confirmed my bug report, see comment 4. No point in resetting it to 'New' or 'Unconfirmed'
(In reply to Axel Braun from comment #6) > (In reply to Xisco Faulí from comment #5) > > You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone > > else confirms it. > > Hardy has confirmed my bug report, see comment 4. > No point in resetting it to 'New' or 'Unconfirmed' You are right. Sorry for that
@Alex, Could you please paste the info from Help - about LibreOffice ?
Version: 6.3.3.2.0+ Build-ID: 30(Build:2) CPU-Threads: 4; BS: Linux 5.3; UI-Render: Standard; VCL: kde5; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded
Dear Axel Braun, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I could not verify this any longer in version Version: 7.2.3.1 / LibreOffice Community Build ID: 20(Build:1) CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Closing the bug