Description: I am following a simple tutorial on Youtube from @TheFrugalComputerGuy to learn how to use Libreoffice Base. I am following his examples step by step without variation. My machine is ubuntu, his is Windows. I can create a table and set some of the columns to have limitations, such as Auto Value Increment or Entry Required. Everything goes just fine here. However, after I finish creating the table and then later reopen it for editing, if I attempt to change a column by turning off Auto Value or Entry Required, the entire libreoffice suite crashes (including other libreoffice applications running, such as Calc). The system automatically attempts to recover the files. However, if I allow it to attempt to reopen them during the application restart process, the applications (all libreoffice applications) hang indefinitely during the launch process. They do not fully launch, so I cannot see them in the desktop environment, but they are running and the only way I can get past this is to either use pkill or restart the machine. I have tried resetting the user configuration profile. This does not change anything. The bug persists and is replicable. Keywords: EDITING, FILEOPEN Steps to Reproduce: 1. Create a table with an auto value increment or entry required limitation 2. Save the table and close the editor 3. Reopen the table in edit mode 4. Attempt to Change auto value increment etc. so that it is no longer required etc. 5. Libreoffice suite crashes. 6. Attempting to allow the auto recovery process to recover the files will results in full suite hang without successful launch. Actual Results: Libreoffice suite crashes Expected Results: The constraint should be removed without error Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.5.2 (X86_64) / LibreOffice Community Build ID: 60(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 4:7.6.5-0ubuntu0.23.10.1 Calc: threaded
Thank you for the report. Which type of database are you using? Are you able to provide a sample database file to make it easier to test? I tested with Firebird, and on changing the table's field from AutoValue = Yes to No, I get the warning "The column could not be changed".
Created attachment 193114 [details] This is the current state of the database as I am progressing through the tutorial series Here is a copy of my current tutorial database. The bug was still present and affected my experience in the tutorial yesterday. I believe the last time the bug occurred, I was changing the decimal count of a numeric column from 0 to 2, using the dialogue box at the bottom of the table definition editor. Everything in that instance of the bug was the same (full suite crash etc.), except I didn't bother trying to auto recover the files, since that only leads to a full system reboot.
(In reply to Stéphane Guillou (stragu) from comment #1) > Thank you for the report. > Which type of database are you using? > Are you able to provide a sample database file to make it easier to test? > > I tested with Firebird, and on changing the table's field from AutoValue = > Yes to No, I get the warning "The column could not be changed". Also, to answer your question, I'm using the HSQLDB Embedded database, as that's what's used in the series.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to contact from comment #2) > Created attachment 193114 [details] Thank you, but I still can't reproduce. I tried setting the 2 tables' integer fields to AutoValue = Yes and then editing the tables further, but no crash. (In reply to contact from comment #0) > 4. Attempt to Change auto value increment etc. so that it is no longer > required etc. How do you do that? Any chance you could provide steps starting from your attachment, that consistently crash it for you? Thank you
(In reply to Stéphane Guillou (stragu) from comment #5) > (In reply to contact from comment #2) > > Created attachment 193114 [details] > Thank you, but I still can't reproduce. I tried setting the 2 tables' > integer fields to AutoValue = Yes and then editing the tables further, but > no crash. > > (In reply to contact from comment #0) > > 4. Attempt to Change auto value increment etc. so that it is no longer > > required etc. > How do you do that? > > Any chance you could provide steps starting from your attachment, that > consistently crash it for you? > > Thank you Hi Stephane, I don't know why I would be receiving the error and you would not. I am on Mantic 23.10, which has created instabilities in other software distributions that I also use. Perhaps there's something there? The issue is persistent and has occurred on around 5 more occasions since last we spoke. Here is the tutorial series I am following: https://www.youtube.com/watch?v=ry7xn4VG0S4&ab_channel=TheFrugalComputerGuy Here is the link to the demo database download page that the tutorial creator provides: https://thefrugalcomputerguy.com/seriespg.php?ser=15#Vid59 I am going through the tutorial series step-by-step and following everything the tutorial provides gives, without variation. I frequently download the demo sample databases found on the second link above, and the same issue repeats. To repeat the issue, you should be able to download one of the databases from the above page, open it up, edit a table column to have a new setting, and then it will crash. I've had this happening while dealing with auto incrementing values, changing the number of decimal places in a numeric, and other settings as well. Are there any queries or bug tracing commands I could run to help you pin point the issue?
Still unable to reproduce the crash. I've: 1. Downloaded https://thefrugalcomputerguy.com/downloads/15/odb59-Clean%20up%20and%20Review%20part%202.odb 2. Opened it with Lo 7.6.5 3. Edited the table tbl_Department 4. Added a new numeric field, changed its decimal places, changed the first field's autoValue from Yes to No back to Yes... no crash. If you get a crash report dialog after the crash, please submit that and share the link to it. Otherwise, you could: 1. get a debug ("-dbg") build from here: https://dev-builds.libreoffice.org/daily/master/current.html 2. see if it crashes too 3. if it does, get a backtrace by following these steps: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
I'll try to get a debug build going with backtrace. Can't do it right this moment, but will try soon.
Tested the attached database with OpenSUSE 15.4 64bit rpm Linux and LO 24.2.2.2. No problem to set AutoValue to 'yes' in both tables. You are using a special packed LO-version of Ubuntu. There are often differences between Base of LO directly and packed by a distribution. Please try to install LO directly from LO packages. You could install it parallel: https://wiki.documentfoundation.org/Installing_in_parallel/Linux
I'm not sure how you're coming to the conclusion that I'm using a special packed version of LO? Looking at the environment notes and scripts I keep, it would seem that I installed using: sudo apt install libreoffice-java-common libreoffice libreoffice-base I've spent a good amount of time attempting to build a debug version, and I'm honestly confused about what the best route is. I first downloaded the .deb version from the link provided. Ran tar -xvf <file-name>, and then looked in the /deb dir. There were a ton of .deb files, and I'm not sure if you're expecting me to install all of them? And in parallel? I then noticed that on the link provided, there was a debug version, so I downloaded that. I ran tar -xvf < file-name> and inside there was not a /deb dir, but rather a /program dir. I'm not sure what's expected there. The other link provided, for installing in parallel, suggests that I simply install the /deb packages from the command line. I'm not certain that those would provide a backtrace? Clarification is appreciate. Thank you.
(In reply to contact from comment #11) > I'm not sure how you're coming to the conclusion that I'm using a special > packed version of LO? Looking at the environment notes and scripts I keep, > it would seem that I installed using: > > sudo apt install libreoffice-java-common libreoffice libreoffice-base What Robert means is that you've got the version packaged by Ubuntu, and sometimes issues are only reproducible in a distribution's package. If that's the case, it might be worth it reporting the issue to Ubuntu maintainers/packagers on Launchpad: https://bugs.launchpad.net/ubuntu/+source/libreoffice > I first downloaded the .deb version from the link provided. Ran tar -xvf > <file-name>, and then looked in the /deb dir. There were a ton of .deb > files, and I'm not sure if you're expecting me to install all of them? Those debs won't have the debug symbols. Don't use this one for collecting a backtrace, but it's good to have anyway to test the latest trunk sources and see if issues are already resolved. To install this one, you can run the following in the directory that has all the debs: sudo dpkg -i *.deb > I then noticed that on the link provided, there was a debug version, so I > downloaded that. I ran tar -xvf < file-name> and inside there was not a /deb > dir, but rather a /program dir. I'm not sure what's expected there. Please use this one, you can run the following from that directory to reproduce the steps and collect the backtrace: ./program/soffice --backtrace More details in: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace