Description: Open a new Writer document. Go to Edit > Exchange Database. Click "Browse" in the dialogue. You could open every file of your documents-folder. Now try a *.pdf-file. The *.odb-file for this *.pdf-file will be created by the wizard in the documents-folder. Close the wizard. Open the created *.odb-file in the documents-folder. Try to open the table-pane of the *.odb-file. Won't work because there is no connection available. Seems the default for no available connection ist to set JDBC to this ... Steps to Reproduce: See above Actual Results: See above Expected Results: See above (I don't understand this form: Description is filled by all the content) Reproducible: Always User Profile Reset: No Additional Info: Tried all this with OpenSUSE 15, 64bit rpm Linux, LO 6.2.4.2
Not reproducible in Version: 6.3.0.0.alpha1+ Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
My previous comment was wrong. I can reproduce it in Version: 6.3.0.0.alpha1+ Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded The new database is in 'My Documents'
Also reproduced in Versión: 6.2.3.2 Id. de compilación: aecc05fe267cc68dde00352a451aa867b3b546ac Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded
Also reproduced in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Dear Robert Großkopf, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still the same in LO 7.1.3.2 on OpenSUSE 15.2 64bit rpm Linux.
https://opengrok.libreoffice.org/xref/core/sw/source/ui/fldui/changedb.cxx?r=200626e4#251 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2820 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2656 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2563 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2571 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2708 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2753 https://opengrok.libreoffice.org/xref/core/dbaccess/source/core/dataaccess/databasecontext.cxx?r=3f65724e#430 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2757 https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2735
might have missed something. continuing investigation...
sorry, no exception was thrown.
Still present in Version: 7.2.1.2 / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded
I would propose returning here. https://opengrok.libreoffice.org/xref/core/sw/source/uibase/dbui/dbmgr.cxx?r=8a017d25#2658
and give error message here. (through catching an exception or checking the return value or whatever) https://opengrok.libreoffice.org/xref/core/sw/source/ui/fldui/changedb.cxx?r=200626e4#257
Dear Robert Großkopf, 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
Bug is still the same with Version: 25.2.3.2 (X86_64) / LibreOffice Community Build ID: bbb074479178df812d175f709636b368952c2ce3 CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded