DC desktop: Where is the sqlite database?

Hi,

I fail to find my local DC sqlite database. Do you have a hint?

Some information:

I have DC 2.11.1 running on a PC (linux, flatpak, created via the secondary device method). I am following this link to export the keys but fail to find any DC database…

Hello :waving_hand:,
unfortunately, I don’t know where the database is stored in Linux, but as a workaround, you could create a backup of your profile. It contains the SQLite database.

On Linux, the GUI should have a key-export function. It may be in the advanced settings, and be called “Export private keys”, though it will probably export the public ones too. It tells you the export location.

The Android GUI key export options were removed due to an Android-specific security problem, whence the post you linked. Since the security problem was not present on Linux, the functionality is still there.

My DeltaTouch DBs are in the subfolders of ~/.config/deltatouch/accounts (almost). There is one subfolder and one “.db” file per account. I know you are not running DeltaTouch but it should be similar.

If you just want your public keys, open the “Saved messages” chat, press the attach-button (“+”)>Contact>Me. Send, then export the attachment to an “.asc” file. It will contain your public keys.

Hey,

well, the desktop version has the key export function but it does not work here. See Github Issue.

And my entire home dir does not contain a single *.db file…

(I haven’t tried to create a backup and search in there.)

Hm!

flatpak stores the data in a different folder. The easiest way to get there is go into the View → developer → open current log folder. (this should also work on other systems)
Then look at the path. go one directory up and then into the accounts folder, there you find your accounts. And in the account’s folder you’ll find the database and the directory of blob-files (all media and other files that are not stored inside of the database).

1 Like

Thanks for the correction @Simon, apologies for the misdirection @mpa, and thanks to m1027 for the bug report.