Arch Linux

matthies

Member

Registered: 2022-11-22

Posts: 11

[SOLVED] KDE taking ages to unlock

Hey,

previously, I often experienced the following issue:
My Laptop would be in suspend mode (just close it) and when I would wake it up again, I was stuck on the lockscreen showing a wrong time and being unresponsive for a few seconds (maybe like 30ish)

I do not have that problem anymore, however now after entering my password, the machine takes ages to unlock, around the same time.
I waited some time in hope an update would fix this, but apparently it does not.

Any ideas?

Last edited by matthies (2023-01-26 12:20:40)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,690

Re: [SOLVED] KDE taking ages to unlock

Have you set your hostname?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,153

Re: [SOLVED] KDE taking ages to unlock

nvidia GPU?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

matthies

Member

Registered: 2022-11-22

Posts: 11

Re: [SOLVED] KDE taking ages to unlock

Have you set your hostname?

In case what you mean is

/etc/hostename

I have set it, yes.

nvidia GPU?

I have integrated Intel Graphics (Iris Xe)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,153

Re: [SOLVED] KDE taking ages to unlock

Ok, since blind guesses didn't lead anywhere, please post a complete system journal covering the incident. (sudo journalctl -b | curl -F 'file=@-' 0x0.st)

Ftr, 25s would be the dbus timeout.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

matthies

Member

Registered: 2022-11-22

Posts: 11

Re: [SOLVED] KDE taking ages to unlock

Thanks, did a lock, unlock, then ran the command:
http://0x0.st/oFZ4.txt

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,153

Re: [SOLVED] KDE taking ages to unlock

Jan 25 18:57:43 ThiccPad dbus-daemon[339]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Jan 25 18:57:43 ThiccPad kscreenlocker_greet[30532]: pam_fprintd(kde:auth): GetDevices failed: Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Jan 25 18:57:43 ThiccPad dbus-daemon[339]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.143' (uid=1000 pid=30532 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Jan 25 18:57:43 ThiccPad dbus-daemon[339]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.

There's something off w/ the fprint configuration.
Probably

Jan 25 16:36:03 ThiccPad fprintd[18432]: /usr/lib/fprintd: error while loading shared libraries: libopencv_features2d.so.406: cannot open shared object file: No such file or directory
Jan 25 16:36:03 ThiccPad systemd[1]: fprintd.service: Main process exited, code=exited, status=127/n/a
Jan 25 16:36:03 ThiccPad systemd[1]: fprintd.service: Failed with result 'exit-code'.
Jan 25 16:36:03 ThiccPad systemd[1]: Failed to start Fingerprint Authentication Daemon.

pacman -Qs opencv

Edit:
libopencv_features2d.so.406 is dated since 3 weeks,

pacman -Qs fprint

Last edited by seth (2023-01-25 18:22:55)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

matthies

Member

Registered: 2022-11-22

Posts: 11

Re: [SOLVED] KDE taking ages to unlock

Jan 25 18:57:43 ThiccPad dbus-daemon[339]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Jan 25 18:57:43 ThiccPad kscreenlocker_greet[30532]: pam_fprintd(kde:auth): GetDevices failed: Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Jan 25 18:57:43 ThiccPad dbus-daemon[339]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.143' (uid=1000 pid=30532 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Jan 25 18:57:43 ThiccPad dbus-daemon[339]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.

There's something off w/ the fprint configuration.
Probably

Jan 25 16:36:03 ThiccPad fprintd[18432]: /usr/lib/fprintd: error while loading shared libraries: libopencv_features2d.so.406: cannot open shared object file: No such file or directory
Jan 25 16:36:03 ThiccPad systemd[1]: fprintd.service: Main process exited, code=exited, status=127/n/a
Jan 25 16:36:03 ThiccPad systemd[1]: fprintd.service: Failed with result 'exit-code'.
Jan 25 16:36:03 ThiccPad systemd[1]: Failed to start Fingerprint Authentication Daemon.

pacman -Qs opencv

Edit:
libopencv_features2d.so.406 is dated since 3 weeks,

pacman -Qs fprint

Removing the fingerprint as a sufficient login method in /etc/pam.d/system-local-login and /etc/pam.d/kde solved it, thanks!

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,153

Re: [SOLVED] KDE taking ages to unlock

You might still want to look into the packages you use, there's probably some dated fprint build from the AUR around?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc