[Bug 210229] Unable to log in: "libpam.so.5" not found

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Jun 12 11:00:57 UTC 2016


            Bug ID: 210229
           Summary: Unable to log in: "libpam.so.5" not found
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: ben.lavery at hashbang0.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

Created attachment 171331
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=171331&action=edit
messages file from boot, includes attempted log in and subsequent failure.

After upgrading to the head on Thursday/Friday I was unable to log into my
FreeBSD-CURRENT laptop - console, X not started.  Having upgraded to base
r301834 I still have this issue.

When trying to log in at the console I get the following error:

    Jun 12 11:41:37 BIL-BSD login: in try_dlopen():
/usr/local/lib/pam_gnome_keyring.so: Shared object "libpam.so.5" not found
    Jun 12 11:41:37 BIL-BSD login: in openpam_load_module(): no
pam_gnome_keyring.so found
    Jun 12 11:41:37 BIL-BSD login: pam_start(): system error

I can, however, log in via SSH.

It seems that /usr/lib/libpam.so.5 has gone away in favour for
/usr/lib/libpam.so.6 - using a symlink seems to be a dirty, temporary,

    %>ls -l /usr/lib/libpam.so.5
    lrwxr-xr-x  1 root  wheel    11B Jun 12 11:49 /usr/lib/libpam.so.5@ ->

You are receiving this mail because:
You are on the CC list for the bug.

More information about the freebsd-amd64 mailing list