After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 631328 - Delays on login when using ldap and disconnected from network
Delays on login when using ldap and disconnected from network
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2010-10-04 15:40 UTC by C de-Avillez
Modified: 2018-05-24 10:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description C de-Avillez 2010-10-04 15:40:51 UTC 
Original Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/654249

System : Maverick RC

Steps to reproduce:
- Install libnss-ldap and set it up correctly
=> Gnome sessions should work normally for a local user
- Plug the computer in an other network or unplug it
=> the ldap server should be unreacheable
- Click on the full name of a local user in GDM
=> The password prompt doesn't appears immediately. This isn't the expected result
- Enter the password and login
=> Startup sound start about 15 seconds later. 20 seconds after logged in, the gnome-panel and the sound menu appears, but the sound is considered as mute an the sound menu doesn't appears when clicking on it.

Expected results:
- "getent passwd" may give a result immediately (the is a delay of 1 second)
- gdm should prompt for the password immediately
- the sound menu should work normally

Workaround: install libnss-ldapd that use nscd with some cache mechanisms that provide the expected results above.
Comment 1 GNOME Infrastructure Team 2018-05-24 10:30:33 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/39.