[Unstable Update] November 2025

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 :slight_smile:

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…

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. :backhand_index_pointing_down:

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 :man_shrugging:

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…).