Description: LibreOffice can't open dbf files on my Ubuntu computer. These files open flawlessly on my office's Win10 computer with the same version of LibreOffice. Steps to Reproduce: 1. Open a dbf file (this one for instance https://bugs.documentfoundation.org/show_bug.cgi?id=53027 ) Actual Results: General Error. General input/output error. Expected Results: Opening the file Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.2.2.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 24; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: fr-BE (fr_BE.UTF-8); UI: fr-FR Ubuntu package version: 1:7.2.2-0ubuntu0.21.10.1 Calc: threaded
Maybe there is an error on the disk where the file is. Try renaming the file and copy a new one, so the new it's not wrote over the old.
I moved it all over the computer. Tried with old files as well as with new ones... No improvement...
It opens fine for me win10. Take a look it this can help. https://askubuntu.com/questions/491292/general-error-general-input-output-error-when-opening-documents-with-libreoff
That's exactly what I say in my bug report: it opens fine on Win10 but not on Ubuntu.
@Olivier : are you sure that this isn't an Ubuntu package problem specific to the version being provided there ? Is this version of LO the default distribution version, a snap, some other package manager provided source (e.g. PPA) ? If it is, then we should mark this as NOTOURBUG.
No repro for me with LO 7.2.3.1 LibreOffice Community VCL:gtk3 running on Ubuntu 20.04.3 I picked a folder containing 3 dbf files, all 3 of them could be opened within LO from a correspondingly configured Base ODB file.
Maybe this is specific to Ubuntu Impish 21.10 ?
Ubuntu tends to split LibreOffice into separate packages. is there a libreoffice-base package in the repo, which should be installed?
This seems to have been fixed by one of the latest updates, either of LibreOffice or of Ubuntu... I can again open DBF files :-) Thanks!
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been identified.