You are not logged in.
Pages: 1
I have keepassxc setup for secret service integration and I am having issues with logging in after suspend and hibernation, the password prompt is locked, I am unable to enter a password. I have to switch user, login, and then the password box comes back again, and now I can enter the password.
While secure it is annoying :-)
It seems it is pam looking for gnome-keyring, although everything is optional
grep pam_gnome_keyring /etc/pam.d/*
/etc/pam.d/budgie-screensaver:auth optional pam_gnome_keyring.so
/etc/pam.d/budgie-screensaver:#auth optional pam_gnome_keyring.so
/etc/pam.d/lightdm:-auth optional pam_gnome_keyring.so
/etc/pam.d/lightdm:-session optional pam_gnome_keyring.so auto_start
/etc/pam.d/lightdm-autologin:-auth optional pam_gnome_keyring.so
/etc/pam.d/lightdm-autologin:-session optional pam_gnome_keyring.so auto_startJournal https://0x0.st/8d9M.txt
I have aded this
[D-BUS Service]
Name=org.freedesktop.secrets
Exec=/usr/bin/keepassxc as
$HOME/.local/share/dbus-1/services/org.freedesktop.secrets.service
but it has not helped with this although it has not made anything worse either.
Everything else is working, and I am getting informed of access to the database by applications as needed.
Last edited by SimonJ (2025-07-18 20:31:14)
Rlu: 222126
Offline
Does the journal actually cover such incident (there's no trace of sleep or hibernation)?
Do you run into the problem by merely locking the screen (no sleep/hibernation required)?
Do you run into https://wiki.archlinux.org/title/Securi … n_attempts ?
Offline
It does not happen if I merely lock the session, only suspend and hibernate.
http://0x0.st/8dpU.txt I just did a suspend and this is the journal from that.
It is on initial presentation of the box so I don't see how it can be failed attempts causing it.
Rlu: 222126
Offline
Edi: more context
jul 18 21:44:38 silex budgie-screensaver-dialog[546104]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
jul 18 21:44:38 silex budgie-screensaver-dialog[546104]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.so
jul 18 21:44:46 silex budgie-screensaver-dialog[546241]: pam_unix(budgie-screensaver:account): setuid failed: Operation not permitted
jul 18 21:45:10 silex budgie-screensaver-dialog[546822]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
jul 18 21:45:10 silex budgie-screensaver-dialog[546822]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.soFaillock could have been triggered by somethingelse™ (eg. cron jobs that call sudo tend to cause this for users)
Last edited by seth (2025-07-18 20:00:08)
Offline
I added deny = 0 to /etc/security/faillock.conf
Rebooted, then suspended and no change.
http://0x0.st/8dfp.txt
Thank you.
Rlu: 222126
Offline
The main concern would still be
jul 18 22:08:34 silex budgie-screensaver-dialog[4077]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directoryOffline
That works, no lock and keepassxc requires a password so that will do. I will check hibernate and mark as solved :-)
Thank you
Edit: hibernate is not locked, the issue is solved.
Last edited by SimonJ (2025-07-18 20:45:05)
Rlu: 222126
Offline
Pages: 1