Google Drive and Zorin 17 & 18 and Keepass2 Issue

Hi There

I have recently installed the new Zorin 18 and Keepass2 to share my Password database between
Windows 11 PC, Windows 10 Nuc, Windows 11 Laptop, Android Samsung Phone and Zorin 18.

Everytime I try to open the Keepass database on Zorin it trashes the File name in Google Drive and replaces My Passwords.kdbx with a random number 01276649885646.kbdx and if I don't have Google drive backed up I have to go back to an old Password database on all my devices.

Does anyone know how to overcome this, or having the same issue. I hate Onedrive so don't have it on any Devices but I need my Customers passwords on my Android Phone and my Linux Mini PC.

Zorin 18 Installed on Lenovo Thinkcentre M73, 64Gb SSD, 16Gb RAM

Hi, as Zorin 18 is based on Ubuntu 24.04 I used this as my search criteria for an A.I. answer:

" The issue where Keepass2 renames your My Passwords.kdbx file to a random string on Google Drive when using a fresh Ubuntu 24.04 installation is a known problem related to how the application handles file operations on networked or cloud storage systems like Google Drive. This behavior occurs because Keepass2, by default, uses a file transaction method where it creates a temporary file with a new name during save operations and then renames it to the original filename. This process fails on Google Drive, which does not support atomic file renaming, causing the original file to be replaced with a temporary file that retains the original name but has a random identifier, leading to sync conflicts across devices.

To resolve this, you can disable the "use file transactions for writing databases" option in Keepass2's settings. This setting can be found under the "Advanced" tab in the "Options" dialog.

Disabling this feature prevents Keepass2 from creating temporary files and renaming them, thus avoiding the filename corruption on Google Drive. It is crucial to apply this change on all devices that access the same database file to maintain consistency.

Additionally, ensure that you are using the correct Google Drive integration method. The default Ubuntu Online Accounts integration may not be reliable for this use case. Consider using google-drive-ocamlfuse to mount Google Drive as a local filesystem, which provides a more stable environment for file operations.

This involves installing the google-drive-ocamlfuse package and mounting your Google Drive to a local directory, allowing Keepass2 to interact with the file more predictably. AI-generated answer. Please verify critical facts."