Simon Dawson

You can close this as now, despite countless tries earlier it is now working. THe only difference was to run it from the terminal to get some feedback......that has forced into working properly.

This morning Enpass wouldn't recognise the Master Password on my main computer. It still works on the laptop and my mobile. I've various 'solutions' on this forum: 1: Uninstall and re-install 2: Delete the 'Enpass' directory in my 'Documents' and reinstall 3: Tried Flatpack and Snap - neither gets me any further 4: Ensured the Laptop had a backup of the vault and then turned sync off and deleted the Google Drive copy. Turned Sync back on and let it recreate the 'Drive' version by resync'ing. What happens? 1: I can activate my copy and am sent the 6 digit activation code - that part appears to work. 2: Next I try and connect to Google Drive to grab the vault on my main machine. I get redirected to CHrome to login to Google and the works. I am told that Enpass has some permissions to Google drive already and do I want to continue etc. After confirming I get passed back to the desktop app and it goes through the sync'ing process and then it asks for my Master Password. I enter that and then it just crashes. When I re-run Enpass it has to go through the whole Activation/Sync process again. Please help!!!

Enpass has suddenly stopped working on my Linux desktop (Solydk - Debian derivation). Starting from a console I get the following messages: /opt/enpass/Enpass: /lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by /opt/enpass/Enpass) QFile::remove: Empty or null file name QQmlComponent: Created graphical object was not placed in the graphics scene. with the QQmlComponent line being repeated a 100 or so times and finishing with: QQmlComponent: Created graphical object was not placed in the graphics scene. terminate called after throwing an instance of 'std::runtime_error' what(): bad zip Aborted It has been working across all my devices for months/years without any problems until this week where it suddenly produced this error. Luckily I can still access my vaults through the mobile and laptop but it makes copying the passwords a bit painful. Anybody got any ideas?