Created attachment 189122 [details] Duplicate entry in document themes "LibreOffice" document theme is duplicated twice by default. See attached image for more info.
Confirmed Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Dear medmedin2014, 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
This is the worst processing operation I have seen, to mark bugs as needing information and force them to be closed if the reported in not available. Version: 25.8.0.4 (X86_64) / LibreOffice Community Build ID: 580(Build:4) CPU threads: 2; OS: Linux 6.16; UI render: default; VCL: kf6 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US 25.8.0-1 Calc: threaded
Your report is not closed.
(In reply to BogdanB from comment #4) > Your report is not closed. But if didn't open my gmail, I would never keep the bug open, so all reports done by sick or died or people not able to connect or lost their mails will be closed with 1 or 2 weeks without any investigation. I never saw this kind of trick to reduce bugs number.
"To make sure we're focusing on the bugs that affect our users today"... "it's possible that the bug has been fixed" - some bugs are solved meanwhile, so testing could give as a new good result today You reported this bug 2023-08-24, so 4 major versions behind, and 28 minor versions behind. every day at least 10-20 commits are made to LibreOffice code. Any change could solve a bug somewhere. "If the bug is present, please leave a comment that includes the information from Help - About LibreOffice." This is helping to know that recent versions still have this problem. So it is still relevant today. "If you want to do more to help you can test to see if your issue is a REGRESSION." If an old version worked and now is broken this means a regression. Users can help here testing older versions until they find what version was not affected in the past by the bug, so someone else can llok at exact change that was made and see what made that bug to appear. So, each info from that info was good to know and relevant.