Thanks for reporting this issue. However, it has certainly nothing to do
with the ubuntu-docs package. Even if I'm not sure, I changed the
affected package to lightdm.

** Package changed: ubuntu-docs (Ubuntu) => lightdm (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1274535

Title:
  LDAP cached credentials and gnome

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 13.10
  Release:      13.10

  STEPS TO REPRODUCE
  1. Implement ldpap server behind firewall (connectable behind vpn)
  2. Implement cached enabled ldap client on a laptop
  3. Start up the laptop and let it autoconnect [prior to login] to a 
previously known vlan outide the vpn
  4. Login to gnome with a ldap user that has successfully logged-in in the past

  EXPECTED RESULT:
  Logged in with cached in credentials

  ACTUAL RESULT (one of the following)
  * Long time then black screen (powercycle needed)
  * Long time then back to login
  * Text authentication error 

  WORKAROUND
  I have a local user, log in with that user and connect to vpn, log out and 
then login with my ldap user.

  NOTE
  - In step 4 above it is possible to login in to tty1 with the expected 
result, so I know my ldap client/server and the caching have been set up 
correctly. 
  - It is possible to login to gnome if laptop has not connected to a wlan (for 
example if there is no known wlan around), then the expected result happens 
after point 4.
  - I think that gnome tries to connect to the ldap, and while it is online it 
tries that forever and never goes on to the cached-in-credentials as it should.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to