| 1 |
Il 23/06/2015 18:34, Canek Peláez Valdés ha scritto: |
| 2 |
On Jun 23, 2015 3:23 AM, "Gmail" <serverplus@×××××.com> wrote: |
| 3 |
> |
| 4 |
> On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverplus@×××××.com> |
| 5 |
> wrote: |
| 6 |
>> |
| 7 |
>> Hi, in a system with gnome 3, systemd and gdm as LM; i can use |
| 8 |
>> only startx to login. |
| 9 |
>> |
| 10 |
>> After the boot, the gdm welcome appear right, but if i try to |
| 11 |
>> login an error message stop "Don't works!! Try again" then |
| 12 |
>> Alt+Ctrl+F2 to start with startx command. |
| 13 |
>> |
| 14 |
>> In the log there aren't error message... |
| 15 |
> |
| 16 |
> |
| 17 |
> Il 22/06/2015 19:17, Canek Peláez Valdés ha scritto: |
| 18 |
>> journalctl -b -u gdm.service |
| 19 |
> |
| 20 |
> |
| 21 |
> It's too long to attach. |
| 22 |
> |
| 23 |
> I see two error messages: |
| 24 |
> |
| 25 |
> giu 23 10:11:18 webandhardware gdm-launch-environment][4986]: |
| 26 |
> pam_systemd(gdm-launch-environment:session): Unknown parameter |
| 27 |
> 'kill-session-processes=1', ignoring |
| 28 |
> |
| 29 |
> giu 23 10:11:59 webandhardware gdm-password][5158]: |
| 30 |
> pam_unix(gdm-password:auth): authentication failure; logname= |
| 31 |
> uid=0 euid=0 tty= ruser= rhost= user=mist3r |
| 32 |
|
| 33 |
If it's too long, use |
| 34 |
|
| 35 |
journalctl -u gdm.service -p err |
| 36 |
|
| 37 |
Or -p warning. Check |
| 38 |
|
| 39 |
Regarding the pam_systemd error; kill-session-processes, the option |
| 40 |
was removed almost two years ago since it was unnecessary[1]. It |
| 41 |
should be harmless; gdm adds that option in my system too. |
| 42 |
|
| 43 |
The second error looks like your user (I'm assuming it's "mist3r") |
| 44 |
failed to authenticate. It's accounts-daemon.service running? |
| 45 |
|
| 46 |
Regards. |
| 47 |
|
| 48 |
[1] |
| 49 |
https://github.com/systemd/systemd/commit/405e0255d5e6950180d9563f1a26294b5360db03 |
| 50 |
-- |
| 51 |
Canek Peláez Valdés |
| 52 |
Profesor de asignatura, Facultad de Ciencias |
| 53 |
Universidad Nacional Autónoma de México |
| 54 |
|
| 55 |
|
| 56 |
mag 09 12:09:59 webandhardware gdm-password][5192]: |
| 57 |
pam_unix(gdm-password:auth): conversation failed |
| 58 |
mag 09 12:09:59 webandhardware gdm-password][5192]: |
| 59 |
pam_unix(gdm-password:auth): auth could not identify password for [mist3r] |
| 60 |
-- Reboot -- |
| 61 |
mag 13 08:58:06 webandhardware gdm-password][5175]: |
| 62 |
pam_unix(gdm-password:auth): conversation failed |
| 63 |
-- Reboot -- |
| 64 |
mag 23 13:23:13 webandhardware gdm-password][7252]: |
| 65 |
pam_unix(gdm-password:auth): conversation failed |
| 66 |
-- Reboot -- |
| 67 |
giu 04 20:08:34 webandhardware gdm-password][5192]: |
| 68 |
pam_unix(gdm-password:auth): conversation failed |
| 69 |
-- Reboot -- |
| 70 |
giu 06 10:16:13 webandhardware gdm-password][5602]: |
| 71 |
pam_unix(gdm-password:auth): conversation failed |
| 72 |
giu 06 11:10:57 webandhardware gdm-password][5612]: |
| 73 |
pam_unix(gdm-password:auth): conversation failed |
| 74 |
-- Reboot -- |
| 75 |
giu 14 13:37:17 webandhardware gdm-password][7845]: |
| 76 |
pam_unix(gdm-password:auth): conversation failed |
| 77 |
-- Reboot -- |
| 78 |
giu 15 23:33:32 webandhardware gdm-password][9730]: |
| 79 |
pam_unix(gdm-password:auth): conversation failed |
| 80 |
-- Reboot -- |
| 81 |
giu 16 19:12:19 webandhardware gdm-password][9801]: |
| 82 |
pam_unix(gdm-password:auth): conversation failed |
| 83 |
giu 16 19:12:19 webandhardware gdm-password][9808]: |
| 84 |
pam_unix(gdm-password:auth): conversation failed |
| 85 |
giu 16 19:12:19 webandhardware gdm-password][9808]: |
| 86 |
pam_unix(gdm-password:auth): auth could not identify password for [mist3r] |
| 87 |
-- Reboot -- |
| 88 |
giu 23 16:02:32 webandhardware gdm-password][5161]: |
| 89 |
pam_unix(gdm-password:auth): conversation failed |
| 90 |
|
| 91 |
|
| 92 |
The accounts-daemon.service running, i've enabled it and started many |
| 93 |
times. |
| 94 |
|
| 95 |
Now i don't know wich upgrade causes it. |
| 96 |
|
| 97 |
Regards |
Archives