Description: While working inside the Database Wizard trying to setup ODBC, I noticed that the Database Wizard gets confused if you first select MySQL-ODBC, then backup and select ODBC, and then backup again and select MySQL-ODBC. At that point (step 3) it should ask for the ODBC setup, but instead it asks for the JDBC setup. This might or might not have to do with the fact that there are 4 steps from MySQL setup, and 5 steps for ODBC setup. Steps to Reproduce: From the menu: File | New | Database ---Opens the Database Wizard dialog ------- Step1: * Connect to an existing database: MySQL Next>> ------------- Step2: * Connect using ODBC Next>> ------------- Step3: <<Back ------------- Step2: <<Back ------------- Step1: * Connect using ODBC Next>> ------------- Step2: <<Back ------------- Step1: * Connect using MySQL Next>> ------------- Step2: * Connect using ODBC Next>> ------------- Step3: Results: "Set up a connection to a MySQL database using JDBC" dialog. ((BUT, this should be "Set up a connection to a MySQL database using ODBC")) Actual Results: Dialog opened: "Set up a connection to a MySQL database using JDBC" Expected Results: Dialog should open: "Set up a connection to a MySQL database using ODBC" Reproducible: Always User Profile Reset: No Additional Info: I may also have a problem w/ ODBC being broken, as I still can't get that to work without crashing, so stay tuned. :-( User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
This bug appears to be more widespread than just where I reported it before. I am also seeing similar behavior under "Use Wizard to Create Form..." In other words, going forward is ok. But going back gets messed up quickly. I have two tables: ----------- Categories: Category ID Category ----------- Items: Item ID Category ID Item ----------- 1. Select Table Categories. >>Add all fields to the form. Next> 2. Check Add Subform. * Subform based on manual selection of fields. Next> 3. Select Table Items. >>Add all fields to the form. Next> 4. <Back. 3. <Back. (this click does nothing!) 3. <Back. (We skipped #2) 1. Next> (this click does nothing!) (we skipped #2) 3. Next> (this click does nothing!) (we skipped #4) 5. Just crazy. Probably just a little thing messing this all up. But it clearly does not behave as I would expect. What I expect: When I have the choice for "<Back" or "Next>" I would expect something to happen when I click on it. It might be reasonable to backup up by 2 at a time. It does not seem reasonable to go forward skipping a step. Thanks!
I could reproduce the behavior, If I do the following: New Database MySQL MySQL-connection > ODBC ODBC-connection then back to MySQL-connection, switch to JDBC JDBC-connection then back to MySQL-connection, switch to ODBC then back to MySQL You could see as step 3 now: JDBC-connection, but MySQL-connection shows ODBC and step 3 would be the dialog for JDBC-connection. Tested here with LO 5.2.2.2 on OpenSUSE 42.1 64bit rpm Linux.
On pc Debian x86-64 with master sources updated today, I could reproduce this. I suppose it's linked with svtools/source/dialogs/wizardmachine.cxx but I don't succeed in understanding where it's wrong.
@Julien : you could try asking Caolan if he has an idea, he fixed some UI stuff in the dbwizard not too long ago, perhaps this is related ?
(In reply to Alex Thurgood from comment #4) > @Julien : you could try asking Caolan if he has an idea, he fixed some UI > stuff in the dbwizard not too long ago, perhaps this is related ? Perhaps you thought about https://cgit.freedesktop.org/libreoffice/core/commit/?id=01889962cab8449e1d9682d22db0f6e1e28252fd but it's unrelated. Anyway, let's ask him! :-) Caolán: perhaps you may have some idea about root cause of this one?
** Please read this message in its entirety before responding ** 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 http://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 still exists for LO 6.1.2.1 on OpenSUSE 15, 64bit rpm Linux
Steps to Reproduce: 1. Run LibreOffice Base 2. Database Wizard comes up. 3. Click 'Connect to an existing database' 4. Choose MySQL from the Combobox 4-Sub-1. See the 'Steps' Section in the roadmap on the left side. Threr you will find confusing 'Set up JDBC Connection' item. In fact this item is for JDBC, but displayed without connection information. Probably coders thought users can choose how to connect on the page later, but they did not notice the roadmap. https://opengrok.libreoffice.org/xref/core/dbaccess/source/ui/dlg/generalpage.cxx?r=32ca8708#130 5. Next 6. you will see a page with JDBC radio button checked as default. click 'Connect using ODBC' 7. Next 8. you will see 'Setup Connection to an ODBC Database' as the title. 9. Back 10. Back 11. Now you've reached the first page. you will see 'Set up ODBC Connection' in the roadmap. Yes, it's not JDBC, but it's ODBC! 12. VERY IMPORTANT STEP. Either click radio button or combobox for the 'Connect to exisiting database'. you will see JDBC in the roadmap. 13. Next 13. you will see ODBC radio button is checked. 14. ANOTHER VERY IMPORTANT STEP. DON'T TOUCH THE RADIOBUTTONS. ESPECIALLY DO NOT TRY CLICKING JDBC FIRST, and CLICKING ODBC AFTER THAT. 15. Next ACTUAL RESULT: As the repoter says, you will see "Set up a connection to a MySQL database using JDBC" you are a nice person , who never forgets the impotant steps, and who don't like tricks in Halloween, aren't you ?
typo:Threr -> There
Dear Howard Johnson, 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 http://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
Because version 6 broke my Base applications in substantial ways, and because I haven't had time to chase down why, I am not using LO version 6 and up, but am rather am still using LO 5 for now. I was hoping at some time 6 would start working again. As far as this and other bugs that I reported, I would be very surprised if it or they are gone in the current version of LO, as it's been my experience that no one is fixing these things. I had hoped to join the effort to fix some of these bugs myself, but I'm struggling with my health and this has given me less time to attend to LO. Sorry.
Bug still exists with LO 6.4.0.0beta1 on OpenSUSE 15.1 64bit rpm Linux. You don't need any ODBC or JDBC-installation for it. Start with Database > Connect to existing database > MySQL Step 2 - choose ODBC Go <Back and step 3 will change to default JDBC-connection Go Next> ODBC is already choosen, but not recognized any more by the wizard. Next> will start (for step 3) do define a JDBC-connection, not the choosen ODBC-connection.
I have tested it also with AOO 4.1.6. It's the same behavior. So could be the bug is inherited by OOo.
Dear Howard Johnson, 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 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
Repro using Version: 24.2.2.1 (X86_64) / LibreOffice Community Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded and also using OOo 3.2.0.
Simplified new steps (6.4.0.3+): 1. File->New->Database 2. Connect to an existing database->MySQL/MariaDB => see that "Steps" list on the left has "Set up JDBC connection" step 3; this is normal, because the selected element of the combobox is associated with "sdbc:mysql:jdbc:" hardcoded prefix. 3. [Next >] 4. (*) Connect using ODBC (Open Database Connectivity) => see that "Steps" list on the left has "Set up ODBC connection" step 3 now. Clicking [Next >] at this stage will navigate to the "Set up a connection to an ODBC data source" page, as expected. 5. [< Back] to step 1 again. => see that "Steps" list on the left has "Set up JDBC connection" step 3: this is a regression in 6.4.0.3 compared to 6.3.0.4. 6. [Next >] => See that the radio button is still at ODBC, but the "Steps" still have step 3 mentioning JDBC. Clicking [Next >] at this stage will navigate to the "Set up connection to a MySQL/MariaDB database using JDBC" page. This secondary change happened after commit 69057064d8957804c76e623d57c103c3413b7cbc (weld ODbTypeWizDialogSetup, 2019-08-22). https://gerrit.libreoffice.org/c/core/+/164987
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1e66905c840dbee0a67e444fca80bdacfcb6e6b2 tdf#103068: make sure to update and use current MySQL connection type It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-24-2": https://git.libreoffice.org/core/commit/8e0bb9dadb9ef77f693cf6d334843cfb9b4701a3 tdf#103068: make sure to update and use current MySQL connection type It will be available in 24.2.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.