kDrive AppImage fails to start - "Unable to open parameters database" error

[wvrossem]

I am experiencing an issue when attempting to start the kDrive AppImage on my system. The application fails to initialize properly and presents the following error message when ran via the command line:

kDrive server starting
kDrive server initialization error: Unable to open parameters database.

Details:

AppImage Version: kDrive-3.6.1.20240604-amd64.AppImage
Operating System: TUXEDO OS 3 x86_64

Additional Information:

I have verified that my system has the necessary permissions to execute the AppImage.
Other AppImages ran without issues on this system (version 3.5.8).

[ClementKunz]

Hi @wvrossem,
Thanks for the report. Indeed it looks like there is an issue with the migration of the database. This will be fixed in the version 3.6.3 to be published soon.
In the meantime, you can still use the 3.5.8.
Regards

[herve-er]

The fix has been implemented in this commit: bba3683

[JorisBodin]

In prod: 3.6.4

[nonameuser-de]

It still happens in 3.6.4, same error as above
(3.6.1 worked well)
Kind regards
Arne
Linux Mint 21.3 Virginia 64-bit
Kernel Linux 6.8.0-40-generic x86_64
Intel® Celeron(R) J4105 CPU @ 1.50GHz × 4

[nonameuser-de]

A work around :
Delete the /home//.config/kDrive
Start the AppImage and set up a new connection with the cloud, make sure to use the same local path (whre the synced files are already) -After a few seconds the new database is there and everything works fine

[gaber-IT]

I can confirm issue is still present with 3.6.4 AppImage file.
Please, reopen this issue and keep it open until fixed.

I can also confirm the workaround from nonameuser-de.

[pascalm7]

As instructed by nonameuser-d, Removed /home//.config/kDrive as well as /tmp/kDrive-logdir
Starting the Appimage produces an error message "kDrive application will close due to a fatal error."

Error log: 20240913_1227_kDrive.log

[herve-er]

Hello,

Regarding the "Unable to open parameters database" error, a workaround is available here: #268 (comment). Please let us know if the issue persists after following these steps.

---

@pascalm7,

Unfortunately, we do not have much insight into the cause of the crash from the logs. Could you please check in the system monitor to see if there are any kDrive instances running in the background? If so, you can kill them and verify that they do not automatically restart. If they do, kill them again and they should not restart. Once you have done this, delete /home/.config/kDrive again (there is no need to delete kDrive-logdir). You can now try to start the AppImage again.

Let us know if the "kDrive application closing due to a fatal error" issue still persists.

---

[pascalm7]

@herve-er
Thanks for your help. Yes, I did check that no other process was running when the appimage was launched but the error persists.
Here is the cmd line output:
pascalm@gatta:~$ ~/AppImages/kdrive.appimage --version kDrive server starting Warning: Ignoring WAYLAND_DISPLAY on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. kDrive version 3.6.4 (build 20240814) Using Qt 6.2.3, built against Qt 6.2.3 Using 'OpenSSL 1.1.1f 31 Mar 2020'
pascalm@gatta:~$ ~/Téléchargements/kDrive-3.6.4.20240814-amd64.AppImage kDrive server starting Warning: Ignoring WAYLAND_DISPLAY on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. log4cplus:ERROR file is not open: /tmp/kDrive-logdir/20240919_1633_kDrive.log log4cplus:ERROR No appenders could be found for logger (Main). log4cplus:ERROR Please initialize the log4cplus system properly.

I hope that helps.

[herve-er]

@pascalm7
It seems that your tmp directory is full (as indicated by the error message: log4cplus:ERROR file is not open: /tmp/kDrive-logdir/20240919_1633_kDrive.log). Since AppImages are extract in /tmp and then run from there, it's possible that the AppImage cannot be fully extract, leading to these crashes.

To verify if this hypothesis is correct, please try extracting the AppImage using the following command:
./kDrive-3.6.4.20240814-amd64.AppImage --appimage-extract

This will create a new folder named squashfs-root alongside the kDrive AppImage. Inside the squashfs-root folder, navigate to squashfs-root/usr/bin, and from here, run ./kDrive.

If the application starts successfully, it's highly likely that the issue is due to insufficient space in your tmp directory.

[pascalm7]

Same error "kDrive application closing due to a fatal error"

pascalm@gatta:~/Téléchargements/squashfs-root/usr/bin$ ./kDrive
kDrive server starting
Warning: Ignoring WAYLAND_DISPLAY on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
log4cplus:ERROR file is not open: /tmp/kDrive-logdir/20240920_1636_kDrive.log
log4cplus:ERROR No appenders could be found for logger (Main).
log4cplus:ERROR Please initialize the log4cplus system properly.

tmpfs size:

pascalm@gatta:~/Téléchargements/squashfs-root/usr/bin$ df -h
Filesystem                                        Size  Used Avail Use% Mounted on
tmpfs                                             6.2G  6.6M  6.2G   1% /run
/dev/mapper/keystore-rpool                        437M   28K  404M   1% /run/keystore/rpool
rpool/ROOT/ubuntu_woks98                          144G  5.2G  139G   4% /
tmpfs                                              31G  4.0K   31G   1% /dev/shm
tmpfs                                             5.0M   16K  5.0M   1% /run/lock
efivarfs                                          248K   42K  202K  18% /sys/firmware/efi/efivars
rpool/USERDATA/pascalm_0spfd9                     890G  752G  139G  85% /home/pascalm
rpool/ROOT/ubuntu_woks98/srv                      139G  256K  139G   1% /srv
rpool/USERDATA/root_0spfd9                        139G   66M  139G   1% /root
rpool/ROOT/ubuntu_woks98/var/lib                  158G   20G  139G  13% /var/lib
rpool/ROOT/ubuntu_woks98/usr/local                139G  640K  139G   1% /usr/local
rpool/ROOT/ubuntu_woks98/var/games                139G  256K  139G   1% /var/games
rpool/ROOT/ubuntu_woks98/var/log                  139G   71M  139G   1% /var/log
rpool/ROOT/ubuntu_woks98/var/mail                 139G  256K  139G   1% /var/mail
rpool/ROOT/ubuntu_woks98/var/spool                139G  5.0M  139G   1% /var/spool
rpool/ROOT/ubuntu_woks98/var/snap                 139G   15M  139G   1% /var/snap
rpool/ROOT/ubuntu_woks98/var/www                  139G  256K  139G   1% /var/www
rpool/ROOT/ubuntu_woks98/var/lib/NetworkManager   139G  1.0M  139G   1% /var/lib/NetworkManager
rpool/ROOT/ubuntu_woks98/var/lib/AccountsService  139G  256K  139G   1% /var/lib/AccountsService
rpool/ROOT/ubuntu_woks98/var/lib/apt              139G  107M  139G   1% /var/lib/apt
rpool/ROOT/ubuntu_woks98/var/lib/dpkg             139G  101M  139G   1% /var/lib/dpkg
bpool/BOOT/ubuntu_woks98                          1.8G  184M  1.6G  11% /boot
/dev/nvme0n1p1                                    511M   15M  497M   3% /boot/efi
tmpfs                                             6.2G  2.6M  6.2G   1% /run/user/1000

Maybe something to do wit AppArmor? Anyone know how to temporarily disable AppArmor in order to troubleshoot the issue?

pascalm@gatta:~/Téléchargements/squashfs-root/usr/bin$ tail -f /var/log/syslog
...
2024-09-20T17:10:43.808734+02:00 gatta kernel: audit: type=1400 audit(1726845043.803:1769): apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=37568 comm="kDrive_client" requested="userns_create" denied="userns_create"
2024-09-20T17:10:43.808754+02:00 gatta kernel: traps: kDrive_client[37568] trap int3 ip:70c597b7e604 sp:7ffd0aa125e0 error:0 in libQt6WebEngineCore.so.6[70c594533000+8b3e000]
2024-09-20T17:10:44.904429+02:00 gatta [email protected][7334]: Could not get menu properties menu proxy: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
2024-09-20T17:10:45.152699+02:00 gatta kernel: audit: type=1400 audit(1726845045.143:1770): apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=37601 comm="kDrive_client" requested="userns_create" denied="userns_create"
2024-09-20T17:10:45.152729+02:00 gatta kernel: traps: kDrive_client[37601] trap int3 ip:78c6f1d1a604 sp:7ffc7d5e4d30 error:0 in libQt6WebEngineCore.so.6[78c6ee6cf000+8b3e000]
2024-09-20T17:10:46.412014+02:00 gatta gnome-shell[7334]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x800008 specified for 0x800006.
2024-09-20T17:10:46.428060+02:00 gatta gnome-shell[7334]: [tilingshell] [extension] building a tiling manager for each monitor
...