Description: Database wizard opens when press CTRL+A inside the extension manager window Steps to Reproduce: 1. Open Writer 2. Open the extension manager 3. Press CMD+A / CTRL+A Actual Results: Database wizard opens Expected Results: Nothing? Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha1+ Build ID: 317f5f2323b8ff7948c4812faaeb0c2a3b907ce8 CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-11-07_00:12:59 Locale: nl-NL (nl_NL.UTF-8); Calc: threaded
Confirming with Version: 6.2.0.0.alpha1+ Build ID: 740b99783b5480fcd1e5fce7c1beb5967d015041 CPU threads: 8; OS: Mac OS X 10.14; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); Calc: threaded sigh
Note that this does not happen with Version: 6.1.2.1 Build ID: 65905a128db06ba48db947242809d14d3f9a93fe Threads CPU : 8; OS : Mac OS X 10.14; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group threaded
I don't understand, for me Ctrl-A opens the file picker dialog, and Cmd-A opens the extensions manager. This is the same both in the latest state of 6.2 macOS bibisect repo, and in 5.0.0.5.
(In reply to Aron Budea from comment #3) > I don't understand, for me Ctrl-A opens the file picker dialog, and Cmd-A > opens the extensions manager. This is the same both in the latest state of > 6.2 macOS bibisect repo, and in 5.0.0.5. to be sure.. 1. Open Writer 2. Tools -> Extension manager 3. Press CMD+A
(In reply to Telesto from comment #4) > to be sure.. > 1. Open Writer > 2. Tools -> Extension manager > 3. Press CMD+A Yes, this opens the Database Wizard for me both in 6.2 and in 5.0.0.5, so I can repro, but it's not a recent regression for me. Additionally, the title says Ctrl-A, and these are different keys that behave differently.
This is happening on LO 3.3 when you press cmd+a too, so it's not a regression. Also, this is a very minor bug - not sure why you would even press cmd+a in the Extension manager so reducing from the current High - Major
Dear Telesto, 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
No repro for me with Version: 7.3.1.3 / LibreOffice Community Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951 CPU threads: 8; OS: Mac OS X 12.2.1; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded
This is still present, in addition it totally breaks the interface such that you need to force quit. The database wizard that open up doesn't register any clicks I pressed command+A Upping the importance given the potential for data loss, but placing it one notch below critical given the expected rarity of encountering this In addition, it shows the highlighted menu bug 117851 I just closed as WFM...
Also repro with Version: 25.2.1.2 (AARCH64) / LibreOffice Community Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 CPU threads: 8; OS: macOS 15.3.1; UI render: Skia/Metal; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded In my test with the above version, the Extensions GUI gets sent to the back, and the Database wizard displayed in the foreground.
(In reply to Alex Thurgood from comment #11) > Also repro with > > Version: 25.2.1.2 (AARCH64) / LibreOffice Community > Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 > CPU threads: 8; OS: macOS 15.3.1; UI render: Skia/Metal; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR > Calc: threaded > > In my test with the above version, the Extensions GUI gets sent to the back, > and the Database wizard displayed in the foreground. Adding that the interface isn't broken for me at this stage, I can interact with either of the dialogs. No apparent dataloss ?