Hi,

database migrated from KeepassX, can access it with my passphrase.

When logging in, enpass is either started from start menu or when restoring previous session (tried both constellations). When I enter my passphrase, it is stated as wrong.

When killing enpass and restarting it, I can enter my passphrase and it unlocks the DB as expected

Any idea why the enpass that's started upon user login is not able to open the DB ?

 

Many thanks

 

Hi @jhf2442

That's very strange! Please provide some more info for further investigation like  Enpass version, Cloud sync, Desktop environment along with Keyboard layout and default language for Enpass.

 

 

Hey @Anshu kumar

I'm using enpass 5.3.0-1 on arch linux / KDE

cloud sync not configured - owncloud not working

keyboard layout is "de"

could the cause be that the root cause is that my enpass file is not located in a standard directory in my /home/$USER ? (BTW, what's the default location if any ?)

 

Many thanks for your support

 

I have the same problem. Enpass is used on multiple linux machines but only on one this problem exists.

• All Ubuntu with KDE (neon) 5.8.x
• enpass 5.3 and 5.4.1 (same Problem)
• "de" keyboard layout
• sync with google drive

I deleted the Enpass directory and setup Enpass again for that user. Same result.

The passphrase is not working after login (autostart). I quit Enpass. After restart all works as expected.

I can't say what is different on this machine/user. The same data can be unlocked without problems on another machine with similar setup.

 

 

I found in .xsession-errors:

QSqlDatabase: QSQLCIPHER driver not loaded
QSqlDatabase: available drivers: QSQLITE QMYSQL QMYSQL3

This does not happen when I restart Enpass.

 

On a machine where it works I have a process:

/opt/Enpass/bin/Enpass startWithTray

Where the problem exists:

/opt/Enpass/bin/Enpass -session 101.....

 

Maybe the autostart 'startWithTray' doesn't work for some reason and KDE restart Enpass without the wrapper script because of restoring the session, but then the environment for Enpass is missing and QSQLCIPHER driver is not found?!

Any idea how to fix that?

 

 

 

I can confirm this - the Enpass process after reboot has the -session 101 parameter (strange enough, mine also starts with 101 !)