It also locks as soon as the screensaver kicks in. Just for fun, I recently tried installing KDE desktop and that did work as expected, so it looks like it is an issue with Cinnamon (I then uninstalled KDE and used a Timeshift restoration to clear up any mess).Īt the moment, I've had to disable that option to lock it with the screen closure and I've instead set keepassxc to lock its database after 3600 seconds of inactivity, which is not a bad situation, but it would be great if the LM team could suggest anything I might try as ideally, I would prefer it to lock after 1 h of laptop inactivity (rather than 1 h of keepassxc inactivity). That's really tedious as I have the screensaver set to 2 minutes and the lock set to 1 hour, so I'd not expect keepassxc to lock its database until 1h after the screensaver kicks in. Additionally, you should switch to our Flatpak distribution.Īnyhow, I uninstalled the snap version (and removed snap, as well as toggling it's availability back off) and I installed flatpak, followed by the flatpak version of keepassxc, however, whilst this does lock the database when the lid is closed (or when the session is locked) it also locks as soon as the screensaver kicks in. You need to make sure the desktop env can send the appropriate dbus signal based on standards. In fact, I closed the lid one evening and when I opened it and logged into LM in the morning, the keepassxc database was still unlocked.Īnyhow, I reached out to the keepassxc folks and their response was as below: I then tried the snap version and that worked, but even though I'd configured it to lock the database when the session's locked or the laptop lid is closed, it didn't do so. The first version I tried was via the apt install route and that worked fine, but it was a little out of date. I've been using keepassxc for a good few months and I really do like it. The below relates to LM21.1 Cinnamon version running on a Dell XPS 17 laptop (which dual boots to some hideous OS, the name of which temporarily escapes me of course, I seldom require to boot into that OS, but I do still require it). That being said, there is a minor issue with one of the settings options, so I'll explain all that below and note what I'm currently doing to get around that issue. To answer the above, last time I looked the version in the repository (so the apt version) was not up to date, but if you'd like the latest and greatest, IMHO the flatpak version is the one to install (as that'll get updated with all the other packages). You could simply copy the database file over to the phone or if you want to keep it in sync, people are using for example Syncthing to do that. If you have a recent Linux Mint version then Update Manager also handles updating flatpak apps.įor considerations between system packages/PPAs, AppImages or flatpaks you can read How to install software on Linux Mintįor the 2nd question see the FAQ with recommendations for Android apps. If you don't need web browser integration then flatpak may be preferabele as it runs the app in a security sandbox. Linux Mint disables the proprietary snap store. I don't know if the AppImage is self-updating but you get updates for the PPA through Update Manager. If you want to use the KeePassXC-Browser extension in Firefox/Chrome/Chromium to connect the web browser to KeePassXC, that probably works best with the PPA or AppImage and you should go for either of those. mail? KeePassXC doesn't exist for Android, so can I just copy password database (which I guess is just an encrypted file with all passwords) to phone and use some other password manager (available in google play store)? I have machine with Mint, Windows & phone/Android - do I need to install KeePassXC at each of the device to access i.e. My second doubt is related to cross-platform. What do you advice ? I would like to be sure that whenever new KeePassXC is released, I will be informed that new version is available to be able to update it (that's why I prefer Mint Update Manger - single program to update everything). Whenever new KeePassXC version is released it won't be updated by Mint Update Manager, right ?įlatpak - usually consumes a lot of space, so maybe Snap ? or maybe the best option is just Ubuntu PPA ? Looks like default/recommended method is appimage.but isn't it just standalone file ? Which one is the best installation method (in terms of Mint upgrade and possible problems) as well as KeePassXC updates itself ? However there are 4 methods of installation: appimage, flatpak, snap and ubuntu PPA. I would like to start using some password manager, and noticed that many users of this forum recommends KeePassXC, so why not ?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |