No more fallback images at boot?
it’s strange, this change should be applied only for new installation , anyway you can enable it again if you need it mkinitcpio - ArchWiki
3 Likes
pkexec: PAM unable to dlopen(/usr/lib/security/pam_fprintd.so):
/usr/lib/security/pam_fprintd.so: cannot open shared object file: No such file or directory
pkexec: PAM adding faulty module: /usr/lib/security/pam_fprintd.so
after upgrading networkmanager.
and after removing un-needed fprintd (1.94.5-1) :
polkit-agent-helper-1: PAM unable to dlopen(/usr/lib/security/pam_fprintd.so): /usr/lib/security/pam_fprintd.so: cannot open shared object file: No such file or directory
polkit-agent-helper-1[19435]: PAM adding faulty module: /usr/lib/security/pam_fprintd.so
And (pamac-manager) of user 1000 dumped core 
polkit-agent-helper-1[6130]: PAM unable to dlopen(/usr/lib/security/pam_fprintd.so): /usr/lib/security/pam_fprintd.so: cannot open shared object file: No such file or directory
PAM adding faulty module: /usr/lib/security/pam_fprintd.so
VIRUS??
$ grep -R fprintd /etc/pam.d/ /usr/lib/pam.d/
/etc/pam.d/kde-fingerprint:-auth required pam_fprintd.so
$ pacman -Qo /etc/pam.d/kde-fingerprint
/etc/pam.d/kde-fingerprint is owned by kscreenlocker 6.5.3-1
So in my case a missing file should not be logged due to the leading -, see pam.d(5) — Arch manual pages.
Perhaps your configuration looks different?
1 Like
Seems I masked fprintd.service before un-installing fprint. Just leftovers…
and:
grep -R fprintd /etc/pam.d/ /usr/lib/pam.d/
/etc/pam.d/polkit-1:auth sufficient pam_fprintd.so
/etc/pam.d/sudo:auth sufficient pam_fprintd.so
/etc/pam.d/gdm-fingerprint:auth required pam_fprintd.so
$ pacman -Qo /etc/pam.d/kde-fingerprint
Error: No package owns /etc/pam.d/kde-fingerprint
Re-installed pam now. Waiting for “whatever happens”.
Ah, /etc/pam.d/sudo and /etc/pam.d/gdm-fingerprint apparently reference pam_fprintd.so and due to those lines not leading with a - you get your log entries I think.
If I’m not mistaken it should be fixed by re-installing fprintd or by modifying those lines
/etc/pam.d/sudo
-auth sufficient pam_fprintd.so
and /etc/pam.d/gdm-fingerprint
-auth required pam_fprintd.so
1 Like
Did this, (modifying lines) added same procedure for /etc/pam.d/polkit-1
(3 times the expression fprintd found in /etc.)
After reboot no message when using pkexec Requester…
After Glib2 update, every time the polkit or some apps call libfprint, the libfprint.so crashes when using a goodix finger print sensor.
It seems to be an ABI breaking change of Glib2, causing the function address changed.
Systemd Log for Libfprint Crash(Stack Trace)
Process 20779 (fprintd) of user 0 dumped core.
11/ 22 18:10:10 wlmqljj-wujie14pro systemd-coredump[20785]: [🡕] Process 20779 (fprintd) of user 0 dumped core.
Stack trace of thread 20779:
#0 0x00007f198e6ee2bf n/a (libgobject-2.0.so.0 + 0x2a2bf)
#1 0x00007f198e70063b g_type_register_static (libgobject-2.0.so.0 + 0x3c63b)
#2 0x00007f198e70085d g_type_register_static_simple (libgobject-2.0.so.0 + 0x3c85d)
#3 0x00007f198b61db3d n/a (libfprint-2.so.2 + 0x1db3d)
#4 0x00007f198b615ced n/a (libfprint-2.so.2 + 0x15ced)
#5 0x00007f198e702a69 g_type_create_instance (libgobject-2.0.so.0 + 0x3ea69)
#6 0x00007f198e6e7c05 n/a (libgobject-2.0.so.0 + 0x23c05)
#7 0x00007f198e6e92a7 g_object_new_with_properties (libgobject-2.0.so.0 + 0x252a7)
#8 0x00007f198e6ea2e2 g_object_new (libgobject-2.0.so.0 + 0x262e2)
#9 0x0000564c2f467a5d n/a (/usr/lib/fprintd + 0xda5d)
#10 0x00007f198e6e7d9a n/a (libgobject-2.0.so.0 + 0x23d9a)
#11 0x00007f198e6e9ebb g_object_new_valist (libgobject-2.0.so.0 + 0x25ebb)
#12 0x00007f198e6ea2c0 g_object_new (libgobject-2.0.so.0 + 0x262c0)
#13 0x0000564c2f462463 n/a (/usr/lib/fprintd + 0x8463)
#14 0x00007f198b227635 n/a (libc.so.6 + 0x27635)
#15 0x00007f198b2276e9 __libc_start_main (libc.so.6 + 0x276e9)
#16 0x0000564c2f462a25 _start (/usr/lib/fprintd + 0x8a25)
Stack trace of thread 20782:
#0 0x00007f198b29f002 n/a (libc.so.6 + 0x9f002)
#1 0x00007f198b29316c n/a (libc.so.6 + 0x9316c)
#2 0x00007f198b2931b4 n/a (libc.so.6 + 0x931b4)
#3 0x00007f198b30d9f6 ppoll (libc.so.6 + 0x10d9f6)
#4 0x00007f198e955784 n/a (libglib-2.0.so.0 + 0x60784)
#5 0x00007f198e955865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865)
#6 0x00007f198e9558b2 n/a (libglib-2.0.so.0 + 0x608b2)
#7 0x00007f198e98c8bc n/a (libglib-2.0.so.0 + 0x978bc)
#8 0x00007f198b29698b n/a (libc.so.6 + 0x9698b)
#9 0x00007f198b31a9cc n/a (libc.so.6 + 0x11a9cc)
Stack trace of thread 20783:
#0 0x00007f198b29f002 n/a (libc.so.6 + 0x9f002)
#1 0x00007f198b29316c n/a (libc.so.6 + 0x9316c)
#2 0x00007f198b2931b4 n/a (libc.so.6 + 0x931b4)
#3 0x00007f198b30d9f6 ppoll (libc.so.6 + 0x10d9f6)
#4 0x00007f198e955784 n/a (libglib-2.0.so.0 + 0x60784)
#5 0x00007f198e955a17 g_main_loop_run (libglib-2.0.so.0 + 0x60a17)
#6 0x00007f198e83d264 n/a (libgio-2.0.so.0 + 0x11a264)
#7 0x00007f198e98c8bc n/a (libglib-2.0.so.0 + 0x978bc)
#8 0x00007f198b29698b n/a (libc.so.6 + 0x9698b)
#9 0x00007f198b31a9cc n/a (libc.so.6 + 0x11a9cc)
Stack trace of thread 20781:
#0 0x00007f198b31872d syscall (libc.so.6 + 0x11872d)
#1 0x00007f198e98482e g_cond_wait (libglib-2.0.so.0 + 0x8f82e)
#2 0x00007f198e91b1cd n/a (libglib-2.0.so.0 + 0x261cd)
#3 0x00007f198e98d487 n/a (libglib-2.0.so.0 + 0x98487)
#4 0x00007f198e98c8bc n/a (libglib-2.0.so.0 + 0x978bc)
#5 0x00007f198b29698b n/a (libc.so.6 + 0x9698b)
#6 0x00007f198b31a9cc n/a (libc.so.6 + 0x11a9cc)
ELF object binary architecture: AMD x86-64
11/ 22 18:10:10 wlmqljj-wujie14pro systemd[1]: fprintd.service: Main process exited, code=dumped, status=11/SEGV
After rebuilding the libfprint package from Arch Linux / Packaging / Packages / libfprint · GitLab
The libfprint works again~ 
I won’t be submitting a bug report to Arch Linux (as it would be quite time-consuming for I don’t have an archlinux gitlab account to submit an issue), but if anyone facing the same issue , and, is willing to take this on, I’d sincerely appreciate your effort in advance!
Does anyone else have this phenomenon?
4.491s systemd-rfkill.service
1 Like
The time or the service?
Anyway mine is:
22ms systemd-rfkill.service
I don’t know since when or through which update. But the boot time of the service has increased noticeably. Is it just me?
476ms systemd-rfkill.service
Keep in mind: this does not necessarily translate to longer overall boot time.
systemd-rfkill.service is not in the critical-chain of graphical.target on any of my systems I checked.
It gets triggered on demand by systemd-rfkill.socket. If you don’t have any WiFi or Bluetooth connections, you can mask it. 
sudo systemctl mask systemd-rfkill.{service,socket}
qt6-webengine-6.10.1-1 crashes dependent applications, dont know further complications, but downgrading to qt6-webengine-6.10.0-3 works for the time being
There must be some additional condition at play, the package alone cannot be it: I’m not seeing any crashes 
1 Like
Please create a new Support thread for further troubleshooting.
I’m actually attempting to package the new Collabora Office desktop application which depends on qt6-webengine, so I’m interested.
2 Likes
oops, sorry, looks very much like a false flag, checked with another laptop with the same apps that were crashing earlier. had no issues with the latest qt6-webengine-6.10.1-1. the probable “additional condition at play”, could very well be the withheld updates to mesa on that laptop. i’ll create a support thread if find some worthwhile to report.
Ah a partial update scenario - classic.
2 Likes
HDSPMixer (alsa-tools) dumped the core, HDSPConf works…; looks like fltk is the culprit: downgraded from fltk-1.4.4-3 => fltk-1.4.3-1, then the thing comes to life again… (fltk-git is at 1.5… we need 1.4 libfltk…).