Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-109902

Unable to log in as "user@domain" or "domain\user" if systemd-userdbd is enabled

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • rhel-10.2
    • rhel-10.0
    • systemd
    • Yes
    • Moderate
    • rhel-systemd
    • 26
    • 0
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • None
    • None
    • Unspecified Release Note Type - Unknown
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      Log in as an IPA/AD user using either "user@domain" or "domain\user" as user name.

      What is the impact of this issue to you?

      At the moment, just an annoyance.

      Please provide the package NVR for which the bug is seen:

      • gdm-47.0-4.el10.x86_64
      • systemd-257-9.el10_0.1.x86_64

      How reproducible is this bug?:

      Always.

      Steps to reproduce

      1. Configure the system as an IPA/AD client.
      2. Try to log in via gdm as "user@domain" or "domain\user".

      Expected results

      User should be able to log in.

      Actual results

      Login fails and the system journal shows this:

      Aug 19 09:32:49 rhel-10-2.example.com systemd[1]: systemd-hostnamed.service: Deactivated successfully.
      Aug 19 09:32:49 rhel-10-2.example.com systemd[1]: systemd-localed.service: Deactivated successfully.
      Aug 19 09:32:52 rhel-10-2.example.com systemd[1]: Starting sssd-kcm.service - SSSD Kerberos Cache Manager...
      Aug 19 09:32:52 rhel-10-2.example.com systemd[1]: Started sssd-kcm.service - SSSD Kerberos Cache Manager.
      Aug 19 09:32:52 rhel-10-2.example.com sssd_kcm[10727]: Starting up
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=bashuser@example.com
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: gkr-pam: unable to locate daemon control file
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: gkr-pam: stashed password to try later in open session
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: Gdm: could not save session and language settings
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: pam_systemd(gdm-password:session): Failed to get user record: No such process
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: pam_unix(gdm-password:session): session opened for user bashuser@example.com(uid=336400003) by bashuser(uid=0)
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: gkr-pam: unable to locate daemon control file
      Aug 19 09:32:53 rhel-10-2.example.com gdm-password][10698]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
      Aug 19 09:32:55 rhel-10-2.example.com kernel: rfkill: input handler enabled
      Aug 19 09:32:55 rhel-10-2.example.com /usr/libexec/gdm-wayland-session[10756]: dbus-daemon[10756]: [session uid=336400003 pid=10756] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=336400003 pid=10753 comm="/usr/libexec/gdm-wayland-session /usr/bin/gnome-se" label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
      Aug 19 09:32:55 rhel-10-2.example.com /usr/libexec/gdm-wayland-session[10756]: dbus-daemon[10756]: [session uid=336400003 pid=10756] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
      Aug 19 09:32:55 rhel-10-2.example.com /usr/libexec/gdm-wayland-session[10753]: Unable to register display with display manager
      Aug 19 09:32:55 rhel-10-2.example.com gdm-password][10698]: pam_unix(gdm-password:session): session closed for user bashuser@example.com
      Aug 19 09:32:55 rhel-10-2.example.com gdm[10170]: Gdm: GdmDisplay: Session never registered, failing
      Aug 19 09:32:55 rhel-10-2.example.com kernel: rfkill: input handler disabled
      Aug 19 09:32:55 rhel-10-2.example.com wireplumber[7437]: spa.bluez5: BlueZ system service is not available
      Aug 19 09:32:55 rhel-10-2.example.com org.gnome.Shell.desktop[10776]: The XKEYBOARD keymap compiler (xkbcomp) reports:
      Aug 19 09:32:55 rhel-10-2.example.com org.gnome.Shell.desktop[10776]: > Warning:          Unsupported maximum keycode 708, clipping.
      Aug 19 09:32:55 rhel-10-2.example.com org.gnome.Shell.desktop[10776]: >                   X11 cannot support keycodes above 255.
      Aug 19 09:32:55 rhel-10-2.example.com org.gnome.Shell.desktop[10776]: > Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
      Aug 19 09:32:55 rhel-10-2.example.com org.gnome.Shell.desktop[10776]: > Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
      Aug 19 09:32:55 rhel-10-2.example.com org.gnome.Shell.desktop[10776]: Errors from xkbcomp are not fatal to the X server
      Aug 19 09:33:19 rhel-10-2.example.com geoclue[10517]: Service not used for 60 seconds. Shutting down..
      Aug 19 09:33:19 rhel-10-2.example.com systemd[1]: geoclue.service: Deactivated successfully.
      Aug 19 09:33:21 rhel-10-2.example.com realmd[10588]: quitting realmd service after timeout
      Aug 19 09:33:21 rhel-10-2.example.com realmd[10588]: stopping service
      Aug 19 09:33:21 rhel-10-2.example.com systemd[1]: realmd.service: Deactivated successfully. 

      It works if systemd-userdbd is stopped:

      # systemctl stop systemd-userdbd.service systemd-userdbd.socket
      # systemctl restart gdm.service

              fsumsalrh Frantisek Sumsal
              rhn-support-casantos Carlos Santos
              systemd maint mailing list systemd maint mailing list
              Frantisek Sumsal Frantisek Sumsal
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: