[Bug 1728055] Re: GDM3 hangs, if local home directory is not accessible

Launchpad Bug Tracker 1728055 at bugs.launchpad.net
Sun Sep 16 04:18:19 UTC 2018


[Expired for autofs (Ubuntu) because there has been no activity for 60
days.]

** Changed in: autofs (Ubuntu)
       Status: Incomplete => Expired

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

Title:
  GDM3 hangs, if local home directory is not accessible

Status in autofs package in Ubuntu:
  Expired

Bug description:
  In Ubuntu 17.10 with GDM 3.26.1-3ubuntu3, the greeter will hang, if
  local /home directory is not accessible.

  Our setup:
  - Ubuntu Server (16.04) with DNS, LDAP, Kerberos 5 and NFS servers. The home directories are present on the server and made available via NFS with krb5 authentication. LDAP provides the user data for clients.
  - Ubuntu client (17.10), bound to the server, uses AutoFS to automount remote home directories under /home. This makes the otherwise present local user directories unaccessible.

  Expected behaviour: After system startup, the greeter should provide a way for users to log in.
  Actual behaviour: The system hangs before the greeter displays the user list (but it does display the top menu bar and Ubuntu logo at the bottom).

  Additional remarks:
  If the settings for local users under /var/lib/AccountsService/users contain SystemAccount=true, the greeter will work as expected (while not displaying local users). This is a workaround, that I'm using right now. BUT: if the network user will log in and invoke the authentication dialog for system-wide settings (e.g. if he will try to add a new printer, or change the system update settings), the system will hang before displaying the expected dialog window. Also if a local user will try to log in by entering his login name and password, the system will hang (it should either produce an error message, or log in without a home directory).

  AutoFS uses this line to mount the remote home directories under /home:
  * -fstype=nfs4,rw,intr,sec=krb5 FQDN:/home/&

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



More information about the foundations-bugs mailing list