Il 23/06/2015 18:34, Canek Peláez Valdés ha scritto: On Jun 23, 2015 3:23 AM, "Gmail" <serverp...@gmail.com> wrote: > > On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverp...@gmail.com> > wrote: >> >> Hi, in a system with gnome 3, systemd and gdm as LM; i can use >> only startx to login. >> >> After the boot, the gdm welcome appear right, but if i try to >> login an error message stop "Don't works!! Try again" then >> Alt+Ctrl+F2 to start with startx command. >> >> In the log there aren't error message... > > > Il 22/06/2015 19:17, Canek Peláez Valdés ha scritto: >> journalctl -b -u gdm.service > > > It's too long to attach. > > I see two error messages: > > giu 23 10:11:18 webandhardware gdm-launch-environment][4986]: > pam_systemd(gdm-launch-environment:session): Unknown parameter > 'kill-session-processes=1', ignoring > > giu 23 10:11:59 webandhardware gdm-password][5158]: > pam_unix(gdm-password:auth): authentication failure; logname= > uid=0 euid=0 tty= ruser= rhost= user=mist3r
If it's too long, use journalctl -u gdm.service -p err Or -p warning. Check Regarding the pam_systemd error; kill-session-processes, the option was removed almost two years ago since it was unnecessary[1]. It should be harmless; gdm adds that option in my system too. The second error looks like your user (I'm assuming it's "mist3r") failed to authenticate. It's accounts-daemon.service running? Regards. [1] https://github.com/systemd/systemd/commit/405e0255d5e6950180d9563f1a26294b5360db03 -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México mag 09 12:09:59 webandhardware gdm-password][5192]: pam_unix(gdm-password:auth): conversation failed mag 09 12:09:59 webandhardware gdm-password][5192]: pam_unix(gdm-password:auth): auth could not identify password for [mist3r] -- Reboot -- mag 13 08:58:06 webandhardware gdm-password][5175]: pam_unix(gdm-password:auth): conversation failed -- Reboot -- mag 23 13:23:13 webandhardware gdm-password][7252]: pam_unix(gdm-password:auth): conversation failed -- Reboot -- giu 04 20:08:34 webandhardware gdm-password][5192]: pam_unix(gdm-password:auth): conversation failed -- Reboot -- giu 06 10:16:13 webandhardware gdm-password][5602]: pam_unix(gdm-password:auth): conversation failed giu 06 11:10:57 webandhardware gdm-password][5612]: pam_unix(gdm-password:auth): conversation failed -- Reboot -- giu 14 13:37:17 webandhardware gdm-password][7845]: pam_unix(gdm-password:auth): conversation failed -- Reboot -- giu 15 23:33:32 webandhardware gdm-password][9730]: pam_unix(gdm-password:auth): conversation failed -- Reboot -- giu 16 19:12:19 webandhardware gdm-password][9801]: pam_unix(gdm-password:auth): conversation failed giu 16 19:12:19 webandhardware gdm-password][9808]: pam_unix(gdm-password:auth): conversation failed giu 16 19:12:19 webandhardware gdm-password][9808]: pam_unix(gdm-password:auth): auth could not identify password for [mist3r] -- Reboot -- giu 23 16:02:32 webandhardware gdm-password][5161]: pam_unix(gdm-password:auth): conversation failed The accounts-daemon.service running, i've enabled it and started many times. Now i don't know wich upgrade causes it. Regards
