[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728055
Yes, the /home directory is there - but it's the remote one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728055
Title:
GDM3 hangs, if local home directory is not accessible
To manage
autofs should still work and mount /home for the terminal user that
logged in. Even after you login, and get the bash warning about the home
directory not being there: if you access the home directory, it still
won't get mounted?
--
You received this bug notification because you are a member of
autofs should still work and mount /home for the terminal user that
logged in. Even after you login, and get the bash warning about the home
directory not being there: if you access the home directory, it still
won't get mounted?
--
You received this bug notification because you are a member of
I have finally found some time to look into this, and turns out, it's
not a problem anymore (with 18.04 at least). If I set the local user
back to normal (so it does appear in the greeter), GDM works normally
(it will display the user list, without any freezing). Of course, you
cannot log into the
Here's the link to the NFS issue:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1733101
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728055
Title:
GDM3 hangs, if local home directory
But the terminal login shouldn't suffer from this root-can't-read-home,
should it? Didn't you experience this there as well?
If the problem is indeed root-squash, then the login should also fail
without autofs. Just mount the home directory first. Can you get this
down to a very simple test case
But the terminal login shouldn't suffer from this root-can't-read-home,
should it? Didn't you experience this there as well?
If the problem is indeed root-squash, then the login should also fail
without autofs. Just mount the home directory first. Can you get this
down to a very simple test case
We're using SSSD. LDAP does not use authentication for search.
In the mean time we already upgraded to 18.04 and I'm not sure if the
bug persists (but will try it again and post the results here - the
workaround is still in place). The issue seems to be with the home
directory being mounted from
How do you fetch your users from ldap, using sssd? Or nss_ldap? Or
something else? Does that need authentication, or are anonymous searches
allowed?
Does the mount()ing work if you temporarily create the user locally in
/etc/{passwd,group,shadow} but not his/her home directory?
This bug is a bit
How do you fetch your users from ldap, using sssd? Or nss_ldap? Or
something else? Does that need authentication, or are anonymous searches
allowed?
Does the mount()ing work if you temporarily create the user locally in
/etc/{passwd,group,shadow} but not his/her home directory?
This bug is a bit
This bug seems not to be related to GDM at all. This is a problem either
with automount, or mount.nfs4.
I did spend some time today digging around this and found out that the
hang lasts for several minutes, but then the system springs back to life
and the user list in the greeter will get
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
13 matches
Mail list logo
