Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About genbushi

  • Rank
  1. Are you getting a specific error? If you run it from the command line via "enpass" command what errors or output is generated?
  2. It kind of sounds like the repository didn't get added fully or your list didn't update. - Check all steps from install are complete. https://www.enpass.io/support/kb/general/how-to-install-enpass-on-linux/ - Afterwards, do an `sudo apt-get clean` and `sudo apt-get update` - Did you see the `apt.enpass.io` repository scroll by when running `sudo apt-get update`? Do you see the repo file when entering the command `cat /etc/apt/sources.list.d/enpass.list` ? - Try installing Enpass again with `sudo apt-get install enpass`.
  3. of course, on the most recent installation, everything works mainly as intended, lol. Try to relate what I did see however: Environment: - On initial install, observed minor notification: Setting up enpass ( ... Error in file "/usr/share/applications/org.kde.kdeconnect_open.desktop": "*/*" is an invalid MIME type ("*" is an unregistered media type) Processing triggers for mime-support (3.64ubuntu1) ... - Continue to configure app, and click to setup cloud sync, Dropbox for example. Get normal dialog for "xdg-open" which is normal: After clicking "open xdg-open" or "Redirect" that I was presented with a "KIO mimetype error, no application associated with enpassauth". As mentioned however, on this most recent installation everything is fine though. My guess is, looking at the file on a working install: $ grep MimeType /usr/share/applications/enpass.desktop MimeType=x-scheme-handler/enpassauth;x-scheme-handler/enpasscard;x-scheme-handler/enpassstart;x-scheme-handler/enpass;x-scheme-handler/cloudkit-xxxxxxxx.in.sinew.walletx;application/enpasscard; that on the install where I was having "KIO mimetype" errors it was likely missing this info in file "/usr/share/applications/enpass.desktop": x-scheme-handler/enpassauth
  4. Apparently there's a mimetype issue when it's calling the xdg-open command to go back to enpass during this process. I'll try to grab more screenshots later today/tomorrow.
  5. Hi @avinator What method was used to wipe the HD before the fresh install? Unless you use a method like shred, DoD wipe, or similar utilities that write random passes of null data to the drive, data persists even though one is doing a "fresh install". I do lots of installs across different linux based systems and do use the Enpass cloud sync to a local, private network resource but haven't been able to reproduce the behavior. The only way I can somewhat replicate is on a new installation where I manually tell Enpass on the initial setup to restore an existing user database from my cloud resource and enter those details - then it will do exactly that. The only explanation really is that what @Ivarson mentioned that possibly your /home partition was not fully wiped and picked up that information, or you possibly did a database restore on configuration?
  • Create New...