Description: Subform is not reachable after entering date inside drop down calender in main form Example: https://thefrugalcomputerguy.com/downloads/15/odb78-Invoice-pt4c-TheInvoice.odb Steps to Reproduce: 1.enter a date for the invoice 2.try to enter the subform 3.... a big nothing occours Actual Results: the form doesn't react anymore ... the data isn't entered inside the database Expected Results: to get inside the subform and edit some new data Reproducible: Always User Profile Reset: No Additional Info: Example from https://thefrugalcomputerguy.com
https://thefrugalcomputerguy.com/downloads/15/odb78-Invoice-pt4c-TheInvoice.odb
No repro with Version: 7.0.0.3 Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e Threads CPU : 8; OS : Mac OS X 10.15.6; UI Render : par défaut; VCL: osx Locale: fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded
@Michael : I would suggest either trying both LO7 and LO646 to see whether this issue has been fixed there for you. Alternatively, it might be specific to the version you are using as provided by the distro (if that is indeed the case).
...I guess it is not specific for a version, because it occours for several versions and I was just too lacy to make a report
(In reply to Alex Thurgood from comment #2) > No repro with > > Version: 7.0.0.3 > Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e > Threads CPU : 8; OS : Mac OS X 10.15.6; UI Render : par défaut; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR > Calc: threaded no changes with version LibreOfficeDev_7.0.0.3 Debian 10 / no Mac
@Michael : please indicate - whether you are using a TDF version, or Debian-supplied version of LO ? - whether the results are different if you use a different VCL backend engine within LO, i.e. instead of using GTK3, you use vcl-gen ? There is an environment variable you can enter to force use of the various VCL backends when starting LO from the command line.
I used LO 6.4.5 and 7 no problems in Debian version 6.1.5.2
CPU-Threads: 4; BS: Linux 4.19; UI-Render: GL; VCL: gtk3_kde5; That is the version of Debian and this one is working Version: 6.4.5.1 Build-ID: be964ce243d03404cfeed53d0487f5d6bd49c627 CPU-Threads: 4; BS: Linux 4.19; UI-Render: GL; VCL: kf5; Version: 7.0.0.3 Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 4; OS: Linux 4.19; UI render: GL; VCL: kf5 Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded These both versions aren't The malfunction only occours with VCL=kf5
SAL_USE_VCLPLUGIN=gtk3 libreoffice6.4 (soffice:29644): Gdk-WARNING **: 14:11:01.328: XSetErrorHandler() called with a GDK error trap pushed. Don't do that. ** (soffice:29644): WARNING **: 14:11:30.507: Focused object has invalid index in parent ...output on the command line --- same with version 7
workaround: insert export SAL_USE_VCLPLUGIN=gtk3 or export SAL_USE_VCLPLUGIN=gtk3_kde5 into bashrc or zshrc there is still a warning starting LO from terminal: (soffice:41800): Gdk-WARNING **: 15:05:41.014: XSetErrorHandler() called with a GDK error trap pushed. Don't do that. ** (soffice:41800): WARNING **: 15:06:00.708: Focused object has invalid index in parent
I don't have access to any KDE or kf5 environment, so can't test any further, sorry.
Tried this: Opened the form Invoices and selected for a new row "Customer" and "Invoice Date". Then I set the cursor into the tablecontrol of the subform. The data of the mainform will be saved and data could be entered in the subform with Version: 6.4.6.2 Build-ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115 CPU-Threads: 6; BS: Linux 4.12; UI-Render: Standard; VCL: gtk3; If I do the same with Version: 6.4.6.2 Build-ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115 CPU-Threads: 6; BS: Linux 4.12; UI-Render: Standard; VCL: kf5; the data won't be saved automatically when leaving the mainform. I have to save the data and then I could enter the subform. This would only happen when entering data into date field "Invoice Date", not when only entering data in "Customer" only. So I could confirm a bug for kf5, but couldn't confirm the subform isn't reachable. I will edit the title to reflect this.
Dear michael, 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