On Fri, 2012-07-13 at 10:18 +0200, Josselin Mouette wrote: > Can you enable debugging and try again? > In /etc/gdm3/daemon.conf, uncomment Enable=true in the debug section.
Thanks for the hint. I am now able to see what is going wrong. In :0-sloave.log, I have now the following blocking lines: [...] gdm-welcome][7146]: DEBUG(+): GdmSessionWorker: saving account details for user Debian-gdm gdm-welcome][7146]: AccountsService-DEBUG(+): ActUserManager: user Debian-gdm changed gdm-welcome][7146]: DEBUG(+): GdmSessionWorker: attempting to change state to SESSION_OPENED gdm-welcome][7146]: pam_unix(gdm-welcome:session): session opened for user Debian-gdm by (uid=0) gdm-welcome][7146]: DEBUG(+): GdmSessionWorker: 1 new messages received from PAM gdm-welcome][7146]: DEBUG(+): GdmSessionWorker: username is 'Debian-gdm' gdm-welcome][7146]: DEBUG(+): GdmSessionWorker: old-username='Debian-gdm' new-username='Debian-gdm' gdm-welcome][7146]: DEBUG(+): GdmSessionWorker: received pam message of type 1 with payload 'reenter password for pam_mount:' gdm-welcome][7146]: DEBUG(+): GdmSessionWorker: Calling SecretInfoQuery gdm-simple-slave[7124]: DEBUG(+): GdmSessionDirect: got message gdm-simple-slave[7124]: DEBUG(+): session_message_handler: destination=(null) obj_path=/org/gnome/DisplayManager/Session interface=org.gnome.DisplayManager.Session method=SecretInfoQuery gdm-simple-slave[7124]: DEBUG(+): GdmSessionDirect: Emitting 'secret-info-query' signal By disabling pam_mount in /etc/pam.d/common-auth and /etc/pam.d/common-session I am now able to get the greeter back and to log in normally. The problem is that gdm is starting a session for Debian-gdm user and pam_mount request a password in order to mount the cifs network drive in its home directory. Do you have an idea how I could still have normal user mounting automatically their network drive and Debian-gdm excluded from this feature? BTW, I do not know if it is a gdm or a pam_mount bug. Many thanks, Antoine -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
