What's your replacement for keepassxc-qt6 for local storage of .kdbx password database?

General system Applications
1

Keepassxc-qt6 (from AUR) let me configure it at first run, but never started again. It just segfaults without any message more. Once I’ve just tried Secrets, was looking good, but that relies on GTK4, and I don’t want it, the same as I don’t want Keepass from packages/extra as it relies on Qt5.

Anyone found good replacement?

For now I’ve installed Chrome extension on Helium browser (required enabling developer options and Helium services), but I’m not sure if it’s good idea…

2

I just use keepassxc from the extra repository, not the qt6 aur flavor.

5 Likes
3

Likewise, it works perfectly.

3 Likes
4

That’s what I want to avoid as I discard obsolete things. Currently. No Qt5 on my system.

5

Well, how is your bug report in the git of keppasxc-qt6 going? :wink:

6

It’s not obsolete, it’s just not the latest and greatest. A lot of software is still Qt5 based.

1 Like
7

Imagine a bug report with the only message I got: segmentation fault…

8

Ok, maybe more true reason: I’m trying to avoid my system bloated with many version of the same libs :wink::saluting_face:

9

Then use the official AppImage as means of not installing extra stuff.

11

The source of your keepassxc-qt6 package has not been updated for 9 years. :grinning_face:

kpqt6
kpqt6767×100 15.9 KB

4 Likes
12

@vazicebon i think you refer to different app, as Qt6 was created at December 2020. :laughing:

13

Fortunately it’s not that bad, it seems they occasionally apply changes in their qt6_v2 branch.

14

I see only one package in the AUR, keepassxc-qt6, when I look at the curent PKGBUILD :

source=("git+https://github.com/the-nic/keepassxc#commit=81e1e89")

This is a fork :

and it doesn’t compile anymore, according to the last comments.

15

When I look at the three PKGBUILD used for this package, the first two show it used official source + patches from a Gentoo repo, and the current one use a very old fork from the official source. :thinking:

16

The age sounded sketchy, so I took a closer look:

I would say:

  • Somewhat bad git habits making merging from upstream opaque.
  • Somewhat out of date but not badly, since official Keepass doesn’t move that fast either
  • Doesn’t provide a release but a random snapshot from upstream. No great, not terrible.
  • Rando 0 star repo. But they put Qt6 patches on top of it anyway, so you have to trust those too. Not great, not a complete show stopper for a low traffic package.

It’s in the AUR. It compiled here. It scratched someones need. The person shared it. Clearly not a five star, but not a fail either. For me no red flag, but a few yellowish enough for a password manager. But make your own choices.

3 Likes
17

:thinking: I didn’t even know there was such a qt version. I just use keepassxc on Linux and Android and share the encrypted file via email to myself.

Didn’t know what I was missing… Usually I’m better at having problems then avoiding them. :roll_eyes:

18

What about some automation via Syncthing? The limit? Local network.

19

I certainly could do that. Just too lazy to bother… But now you’re motivating me to put that on my to do list. Thanks.

20

If you’re already using Syncthing, there is no need to set up something just for the KeePass database file. You could just move the file to a directory that is already synced, or create a subdirectory inside one that is already synced.

Of course, if you weren’t already using Syncthing, then you’ve been missing out. :winking_face_with_tongue:

21

It’s really simple, worked for me OOTB. Just no point for me to sync one file that may not change for a month or more. For such casual operations I use LocalSend. Doesn’t look good on a computer, but whatever. I’ve seen uglier things… like the bloated KDE Connect. :face_with_peeking_eye:

1 Like