Summary: | gnome-base/gdm-3.22.1 installs pam_gdm.so into wrong directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | daniel <paessler> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jstein, yoshi3 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugzilla.gnome.org/show_bug.cgi?id=774776 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge info |
Same here! Even setting --with-pam-prefix=/lib in configure does not lead to pam_gdm.so being installed under /lib/security - pam_gdm/ simply uses libdir for the installation, which is /usr/lib64 here... Same situation here. Gdm fails to start now. A symlink unbreaks gdm autologin /lib64/security/pam_gdm.so -> /usr/lib64/security/pam_gdm.so Will investigate pushed 3.22.1-r1 with a patch. Closing. Don't hesitate to reopen if the issue still appears. Thanks ! |
Created attachment 453298 [details] emerge info After the update to gnome-3.22, gdm-autologin fails with: gdm-autologin][722]: PAM unable to dlopen(/lib64/security/pam_gdm.so): /lib64/security/pam_gdm.so: cannot open shared object file: No such file or directory gdm-autologin][722]: PAM adding faulty module: /lib64/security/pam_gdm.so because pam_gdm.so is installed in /usr/lib64/security/ instead of /lib64/security/, which leads to a black screen when auto-login is enabled in /etc/gdm/custom.conf