Description: Selecting the "Tools>Customize...>Notebookbar>LibreOffice Writer - Tabbed (scope) / All Commands (target) / Export as PDF (Assigned Commands)" button doesn't result in it being showed in the Notebook bar. All the other buttons, including "Export Directly as PDF" seem to be working. Steps to Reproduce: Tools>Customize...>Notebookbar>LibreOffice Writer - Tabbed (scope) / All Commands (target) / Export as PDF (Assigned Commands) Actual Results: "Export as PDF" doesn't show up Expected Results: "Export as PDF" button showing up Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded
I see what happens is that the checkbox does not stay checked, if you reopen the Customize dialog. I tested with some older versions and there were some confusing results: around 7.1 on Linux, I could get the checkbox to stick, but there was no logic regarding how to bibisect (worked in last commit of 7.1, didn't work in 7.2). So I suspected some kind of fluke. Looking at bug 127421 and commit c437948f6c0d602bb200fc92e80cb73ae8ae5109, I tested the commit in Windows 7.0 repo and already in that commit, the checkbox did not stay checked. Issue still seen in Arch Linux 64-bit, X11 Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 18e579761cb622e8ff7e67f319ef80c61b3bd588 CPU threads: 8; OS: Linux 6.7; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 19 January 2024
Dear dattero2011, 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