[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#760496: marked as done (libpam-mklocaluser: Unable to send messages back to kdm)



Your message dated Fri, 22 May 2020 16:34:05 +0000
with message-id <E1jcAcX-000Gug-2Q@fasolo.debian.org>
and subject line Bug#760496: fixed in libpam-mklocaluser 0.18
has caused the Debian Bug report #760496,
regarding libpam-mklocaluser: Unable to send messages back to kdm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
760496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760496
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-mklocaluser
Version: 0.10
Severity: important
User: debian-edu@lists.debian.org
Usertags: debian-edu

When logging in a LDAP user into kdm for the first time on a freshly
installed Roaming Workstation based on Debian Edu Jessie, the login went
fine but instead of being told that a local user was created, I was told
that the user had no home directory and the login failed.

These are the related messages in /var/log/auth.log:

Sep  4 19:32:08 thinkpadx200 kdm: :0[2256]: pam_unix(kdm:auth): authentication failure; logname= uid=0 euid
=0 tty=:0 ruser= rhost=  user=pere
Sep  4 19:32:08 thinkpadx200 kdm: :0[2256]: pam_sss(kdm:auth): authentication success; logname= uid=0 euid=
0 tty=:0 ruser= rhost= user=pere
Sep  4 19:32:08 thinkpadx200 kdm: :0[2256]: pam_unix(kdm:session): session opened for user pere by (uid=0)
Sep  4 19:32:08 thinkpadx200 systemd-logind[1735]: New session 1 of user pere.
Sep  4 19:32:08 thinkpadx200 systemd-logind[1735]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
Sep  4 19:32:08 thinkpadx200 systemd: pam_unix(systemd-user:session): session opened for user pere by (uid=
0)
Sep  4 19:32:08 thinkpadx200 pam_mklocaluser[3283]: Creating local passwd/shadow entry uid=1000(pere) gid=1
000(pere) gecos='Petter Reinholdtsen' home=/home/pere
Sep  4 19:32:08 thinkpadx200 pam_mklocaluser[3283]: Creating local home directory for user 'pere'
Sep  4 19:32:08 thinkpadx200 pam_mklocaluser[2256]: pam_ck_connector(kdm:session): nox11 mode, ignoring PAM
_TTY :0
Sep  4 19:32:08 thinkpadx200 pam_mklocaluser[3283]: Failure while creating local user: Conversation error
Sep  4 19:32:08 thinkpadx200 pam_mklocaluser[3283]: pam_ck_connector(systemd-user:session): cannot determin
e display-device
Sep  4 19:33:11 thinkpadx200 kdm: :0[2256]: pam_unix(kdm:session): session closed for user pere
Sep  4 19:33:17 thinkpadx200 systemd-logind[1735]: Removed session 1.

The new user is present in /etc/passwd and /etc/shadow, so I expect the
python script crashed when trying to send a message back to kdm, but it
could have happend earlier too.  The mklocaluser.d/ fragment in place
seem to have executed as it should (~pere/.local/share/user-places.xbel
is correct).

      syslog.syslog("Creating local home directory for user '%s'" % user)
      # Copy content of /etc/skel
      shutil.copytree("/etc/skel/.", newhomedir, True)

      # Change perm of new home dir
      os.chmod(newhomedir, dirmode)
      chown_recursive(newhomedir, uid, gid)

      # Flush nscd cache to get rid of original user entry
      if os.access("/usr/sbin/nscd", os.X_OK):
        runcmd(pamh, "/usr/sbin/nscd -i passwd")

      # Hook for adjusting the freshly created home directory
      # FIXME Should be rewritten in python, I guess
      runcmd(pamh, "if [ -d /etc/mklocaluser.d ]; then ORIGHOMEDIR='%s' USER='%s' /bin/run-parts /etc/mklocaluser.d ; fi" % (homedir, user))

      # Let the user know what is going on
      msg = pamh.Message(pamh.PAM_TEXT_INFO,
                         "Local user created in /home/, please log in again to start using it.")
      pamh.conversation(msg)

      # Throw out user, as the log process cached the home directory
      # and need to be restarted.
      return pamh.PAM_TRY_AGAIN

No idea what could go wrong here.

-- 
Happy hacking
Petter Reinholdtsen

--- End Message ---
--- Begin Message ---
Source: libpam-mklocaluser
Source-Version: 0.18
Done: Mike Gabriel <sunweaver@debian.org>

We believe that the bug you reported is fixed in the latest version of
libpam-mklocaluser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 760496@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel <sunweaver@debian.org> (supplier of updated libpam-mklocaluser package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 22 May 2020 18:01:47 +0200
Source: libpam-mklocaluser
Architecture: source
Version: 0.18
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers <debian-edu@lists.debian.org>
Changed-By: Mike Gabriel <sunweaver@debian.org>
Closes: 760496 961254
Changes:
 libpam-mklocaluser (0.18) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Mike Gabriel ]
   * debian/control:
     + Line-wrap B-D and D fields.
     + Provide more info in LONG_DESCRIPTION.
     + Update Section: field. Using "admin" section seems more appropriate.
       Thanks lintian.
   * debian/pam-python.py:
     - Set HOME env variable to the new home directory, also on initial user
       login. This makes it possible to drop the concept of enforced re-login
       on initial user login. (Closes: #760496, #961254).
     - Whitespace clean-up.
 .
   [ Holger Levsen ]
   * Use secure URI in Homepage field, thanks lintian-brush.
   * Upgrade to newer source format 3.0 (native), thanks lintian-brush.
   * Update standards version to 4.5.0, no changes needed & thanks once more,
     lintian-brush.
   * Bump debhelper-compat to 13.
   * Drop versioned suggests on libpam-ccreds, as even squeeze has a newer
     version.
Checksums-Sha1:
 ece2cec55c0727adcfa458caaca279e40262628b 1761 libpam-mklocaluser_0.18.dsc
 7f9a3968de378a0cf707d0f3b79e85bf7e1fc154 6780 libpam-mklocaluser_0.18.tar.xz
 11fbb4d4f5e1a17a9141f17cd5758a22a9331040 6813 libpam-mklocaluser_0.18_source.buildinfo
Checksums-Sha256:
 6ed70625c2d73b2e7fe05a3cb9732cefa8134439db93dab3840fb68671167c29 1761 libpam-mklocaluser_0.18.dsc
 15ddb527d1fb7c8d2a95ee70d0e311d61768c57c5880dd6634222dbdce1e04f4 6780 libpam-mklocaluser_0.18.tar.xz
 a054dbb86776512e51cb4b9554fa102b897ee3e8a38ed91f373e616f46fc09d7 6813 libpam-mklocaluser_0.18_source.buildinfo
Files:
 89769856ce3012a3e06bc8a8f10f0d15 1761 admin optional libpam-mklocaluser_0.18.dsc
 89198c8af3b3a24cf8c813e12393c545 6780 admin optional libpam-mklocaluser_0.18.tar.xz
 48d331ca7793106260f8ccde9c9cb3ed 6813 admin optional libpam-mklocaluser_0.18_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl7H/BIVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx3tUQALWCeX/wawzTj71EOUxWkj7V80Lh
iE1h/vey29nZNuzr7uOpYzmv0FE260LrfFUeSuJ6igPQAOXtpwGMH70lMqLp+Njj
o/L/yex2e2vlp2ffL0IFE4S3ea8MHYuHJMU67IPWrIgzbNFkKlnyfDhGMgEsoIJt
W0BJFFRX7zmlJrUIqPJim2+RrtOYcEoFrccRVGFkm8YxKGcK6FyHMwN4f0sj1XRV
oGnyl5v8a1EhWcFen01J50K3c+GWaINlWe3XNlDtju1C8gNGjJHo/Xy9IWHLVzSB
4z9R+BgcoQqLaBr2xYQgt+4z7aKcJZk2ewyTVDsBAcgawm+0ug5EW+MFmejFUMkc
swSEpDrQR8BGzzdGYHtpOQvkhMvAbF1C703QE8zH9BmeF08+e0Pu66e5zYUKcvah
J2AlnA5gcb5nxSlUCSt3vF42My5S2yNvlEF5SxUNXRjYw4o8OAUffPdOBi6K3YV8
QTQrvNZ0GC7rmikIKAC6yYpFzY05rJ57y/W19+vbpgswqgN36Ol8dey+UHIJDXAo
NiZSXTzrk4K9pO1WjgQ6j9wJSYRbI5HjldtYD8fCFxeZ7/Jl5N6KrtMnC3+aLYyk
tcwIJI+tOwuoujObgd6GNtIbekl7CyxCwxw6F+ghzhOY43kAc2Z5HHl0m2TJuIhU
8Eog58EBtn+XU0F0
=b8Uk
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: