This bug was filed from the crash reporting server and is br-263ba3a7-926f-4f4d-b8a1-96be91a9a5a9. ========================================= Crashed when creating new database. LO repeatedly attempted to recover file and go into safe mode.
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
Created attachment 150683 [details] Dialog that opens after saving new database. Dialog that opens after saving new database.
Created attachment 150684 [details] 2nd Dialog
Created attachment 150685 [details] 3rd Dialog After this dialog, it cycles back to first dialog. This does not happen in Windows 10. It only happens in Linux Mint 19.1. I have looked at permissions, but can find no obvious problems.
@Mike : sorry, but we need more information than just screenshots. 1) Which kind of database are you attempting to create ? 2) From the trace, it appears that you tried to create an embedded Firebird ODB file, but can you please set out the steps you carried out to try and create this file ?
I would add that LO6222 is not the default distro-provided version for LM19.1, so either you are using a snap, or else you have downloaded and installed a PPA, or you have obtained that LO version from somewhere else. Please specify.
No repro for me with : Linux Mint 19.1 libreoffice-6.2.2.2-snap1 Linux kernel 4.15 VCL: GTK3 I can create a Firebird embedded ODB, for example using the db creation wizard, without any of the described problems. I can also create a table with a primary key and autovalue, save it and then subsequently enter data in to the table.
I downloaded it yesterday from https://www.libreoffice.org/download/download/ It has also not been working for the previous download.
I just checked the download. It is 6.2.2.2-2 DEBS for AMD 64.
I am running Linux kernel 4.18.0-17-generic.
It is probably not relevant, but I had to add myself to the firebird group before I could run FlameRobin. I used the following command: usermod -a -G firebird mike I can now create and work with new databases and tables with FlameRobin. However, it makes no difference to Base. Base always enters the recover file loop described before when trying to open a file that works in Firebird and FlameRobin.
I have downloaded and run AppImage Fresh. Base works. However, a firebird database file created via the AppImage cannot be opened properly by the Deb version. Only one of three tables in a database is shown.
@Mike : please provide the detailed steps of creating the database that lead up to the crash.
Created attachment 150777 [details] Zip file of screen shots
Removed and reinstalled LO6222 Fresh DEBS. Then created simple single table as per the screenshots in the zip file.
Created attachment 150834 [details] Database ATest.odb created with AppImage 6.2.2.2 - works This saves and opens. Smallest possible file. Default create and register database settings. File size 1853 bytes.
Created attachment 150835 [details] Dtabase file created with 6.2.2.2 DEBS version of LO Smallest possible file using default settings to create and register new database file. File size is 1789 bytes. Inspection with hex editor shows it is very different from AppImage version. Only the name is different Atest.odb vs BTest.odb.
No repro for me with Version: 6.2.2.2 Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d Threads CPU : 8; OS : Mac OS X 10.14.3; UI Render : par défaut; VCL: osx; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded @Mike : it might also help if you provided your distro name / version. What I did : 1) Started LibreOffice 6222 2) Clicked on New Database from StartCenter 3) Chose Create new embedded Firebird as db type. 4) Click Next 5) Leave default radio button choices of "Yes, I want the database to be registered" and "Open the database for editing" 6) Click on End and Save with name of my choice. 7) Database file is saved and opened for editing.
Alex, that was exactly what I did. My PC details are: Linux Mint 19.1 Cinnamon Cinnamon Version 4.0.10 Linux Kernel 4.18.0.17-generic Processor Intel Core i5-7200U CPU @2.50GHz x 2 Memory 7.7 GiB Graphics card Intel HD Graphics 620
Sorry, I was a bit slow there. The LO details are Version: 6.2.2.2 Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded
@Mike : Did you completely purge all traces of the distrib-provided version of LO before installing the TDF 6222 download ? I'm begining to wonder whether the libfbembed engines or the libfbclient libraries might be conflicting. In the screenshots you provided, there were standalone FDB files, and you also mention using FlameRobin, which indicates to me that you have also installed a firebird server on your machine ? There may be some conflict somewhere in there.
Everything now works, after removing every trace of LO and reinstalling. I deleted the AppImage of LO,then removed the DEBS with sudo apt-get remove --purge libreoffice* sudo apt-get clean sudo apt-get autoremove I used synaptic to search and remove anything with 'LibreOffice' or 'odf'. I then used sudo nemo to search for 'libreoffice' and removed every file that I found. There were very many icon files and symlinks, and a some library files. During the process I found some files going back to 3.0 and 3.4. I deleted the LO 6.2.2.2-2 DEBS. Altogether I found 30Gb of extra disk space! I then rebooted the PC. I downloaded the latest Fresh which has changed to 6.2.3.2-2 and installed. I created a minimal new database file, as above, and saved it as CTest.odb. In GHex it appears identical to the ATest.odb file created earlier from the AppImage LO. I opened several files, including some complex examples. Everything now works. Thank you very much for persevering with me.
@Mike : glad to have been able to be of some help. Changing to RESOLVED WORKSFORME though, as FIXED is reserved for when a patch has gone in to fix an identified and confirmed bug.