[Bug 1872282] [NEW] Failed to get user record: Invalid argument

[Josef Hopfgartner]

Public bug reported:

system is ubuntu focal with pam_winbind and nss_winbind enabled.

unix users are not affected.
this bug won't happen with systemd version 2.44.3

beginning with version 245 (including 245.4-2) no user session will be created after login.
login itself works e.g. on tty2.
but loginctl does not show a corresponding user session.
gdm login needs a user session, so it fails.

this bug already seems to be handled here:
https://github.com/systemd/systemd/issues/15149

this bug only affects user sessions directly on a samba domain controller.
users can log in with pam_systemd version 245 on winbind client workstations in the same domain.

journalctl reports:
Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: pam_systemd(login:session): Failed to get user record: Invalid argument

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libpam-systemd:amd64 244.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Apr 12 11:44:41 2020
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1872282

Title:
  Failed to get user record: Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  system is ubuntu focal with pam_winbind and nss_winbind enabled.

  unix users are not affected.
  this bug won't happen with systemd version 2.44.3

  beginning with version 245 (including 245.4-2) no user session will be created after login.
  login itself works e.g. on tty2.
  but loginctl does not show a corresponding user session.
  gdm login needs a user session, so it fails.

  this bug already seems to be handled here:
  https://github.com/systemd/systemd/issues/15149

  this bug only affects user sessions directly on a samba domain controller.
  users can log in with pam_systemd version 245 on winbind client workstations in the same domain.

  journalctl reports:
  Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: pam_systemd(login:session): Failed to get user record: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-systemd:amd64 244.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 12 11:44:41 2020
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872282/+subscriptions