Description: When selecting tools->relationships, Base hangs, requiring the application to be forced to quit. Steps to Reproduce: 1. Follow the tutorial in the LibreOffice Getting Started Guide, Chapter 8, Getting Started with Base. 2. After building up the "automobile.odb" database, and finally arriving at the section entitled "Defining relationships", select Tools->Relationships as instructed in the tutorial. Actual Results: LibreOffice Base hangs after bringing up the Relation Design window. The Add Tables dialog does not appear and the mouse pointer busy indicator keeps spinning forever. The program has hung, has stopped responding to input and has to be forced to quit. Expected Results: The program should never hang, even if the information entered is incorrect. Reproducible: Always User Profile Reset: No Additional Info: If I remove the two tables named "CD-Collection" and "CD-Jazz" and save the database, the program no longer hangs as before. Version: 6.2.0.3 Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3; Locale: en-CA (en_CA.UTF-8); UI-Language: en-US Calc: threaded OS: Ubuntu 18.04 LTS
Created attachment 150022 [details] File that hangs.
Created attachment 150023 [details] File also hangs with fewer tables.
(In reply to Allan Macdonald from comment #1) > Created attachment 150022 [details] > File that crashes. Sorry, meant to say "Hang"
More info: The file that I said doesn't hang, actually does. However, if I copy a table and remove the old table, it stops hanging. After closing and opening the database, it starts hanging again. Steps to reproduce: 1. Copy the table named "Fuel" 2. Paste the table, naming it "Fuel2" 3. Copy all fields. Keep all defaults. 4. Save the table. 5. Delete the old table named "Fuel" 6. Save the database file. 7. Confirm that the program doesn't hang when selecting tools->relationships. 8. Close the add table dialog and the relation design window. 8. Close the database file. 7. Open the database again. 8. Right away, select tools->relationshps. HANG!
Can confirm that the error happens using LO 6.2.0.3. However using: Version: 6.2.3.0.0+ Build ID: bd5ef0f1ecb445021fc693bfd3cab0979a4c4c28 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; (downloaded from daily build yesterday) I can not reproduce with either file. The relationship window appears to be functioning properly again. Not sure what status to set for the issue, fixed?
OK - Works for me, makes more sense..so
(In reply to Drew Jensen from comment #6) > OK - Works for me, makes more sense..so Is it appropriate to resolve this bug when the bug is not fixed in an official release? The problem still happens with LibreOffice 6.2.1.2.
(In reply to Allan Macdonald from comment #7) > (In reply to Drew Jensen from comment #6) > > OK - Works for me, makes more sense..so > > Is it appropriate to resolve this bug when the bug is not fixed in an > official release? The problem still happens with LibreOffice 6.2.1.2. Nor is it fixed in the RC1 pre-release of 6.2.2.1 (just downloading that now to try and the bug is there) but is fixed in the very latest 6.2.3.0 build. IDK what the chances are that this alone would be a showstopper bug for the 6.2.2; I do know that for myself it would not.
(In reply to Drew Jensen from comment #8) > (In reply to Allan Macdonald from comment #7) > > (In reply to Drew Jensen from comment #6) > > > OK - Works for me, makes more sense..so > > > > Is it appropriate to resolve this bug when the bug is not fixed in an > > official release? The problem still happens with LibreOffice 6.2.1.2. > > Nor is it fixed in the RC1 pre-release of 6.2.2.1 (just downloading that now > to try and the bug is there) but is fixed in the very latest 6.2.3.0 build. > > IDK what the chances are that this alone would be a showstopper bug for the > 6.2.2; > I do know that for myself it would not. I think you missed my point. As far as a general user is concerned, this is a bug that still exists in the normal release that is available at libreoffice.org and the presence of this bug might preclude any sensible person from trying to use that version of software for any critical purpose. As such, I am suggesting that perhaps marking this bug as resolved is premature until a fix is available for normal releases. I am not willing to go so far as go and change the resolution myself and will defer to those in better authority to state what the policy is for LibreOffice develpment community regarding bug resolution. Nevertheless, whether the bug is a "showstopper" or not is irrelevant with respect to whether or not the bug is fixed in the normal release. If I am off base, please do not hesitate to let me know.
(In reply to Allan Macdonald from comment #9) > (In reply to Drew Jensen from comment #8) > > (In reply to Allan Macdonald from comment #7) > > > (In reply to Drew Jensen from comment #6) > > > > OK - Works for me, makes more sense..so > > > > > > Is it appropriate to resolve this bug when the bug is not fixed in an > > > official release? The problem still happens with LibreOffice 6.2.1.2. > > > > Nor is it fixed in the RC1 pre-release of 6.2.2.1 (just downloading that now > > to try and the bug is there) but is fixed in the very latest 6.2.3.0 build. > > > > IDK what the chances are that this alone would be a showstopper bug for the > > 6.2.2; > > I do know that for myself it would not. > > I think you missed my point. As far as a general user is concerned, this is > a bug that still exists in the normal release that is available at > libreoffice.org and the presence of this bug might preclude any sensible > person from trying to use that version of software for any critical purpose. > As such, I am suggesting that perhaps marking this bug as resolved is > premature until a fix is available for normal releases. I am not willing to > go so far as go and change the resolution myself and will defer to those in > better authority to state what the policy is for LibreOffice develpment > community regarding bug resolution. > > Nevertheless, whether the bug is a "showstopper" or not is irrelevant with > respect to whether or not the bug is fixed in the normal release. If I am > off base, please do not hesitate to let me know. Never mind; I guess I AM off base: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/RESOLVED#The_Meaning_of_RESOLVED I'll shut up now.