Mailing List Archive

On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverplus@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...

Could you please post the output from:

journalctl -b -u gdm.service

after you try to log in and it fails?

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverplus@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

On Jun 23, 2015 3:23 AM, "Gmail" <serverplus@gmail.com> wrote:
>
> On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverplus@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

Il 23/06/2015 18:34, Canek Peláez Valdés ha scritto:
On Jun 23, 2015 3:23 AM, "Gmail" <serverplus@gmail.com> wrote:
>
> On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverplus@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

On Tue, Jun 23, 2015 at 1:35 PM, Gmail <serverplus@gmail.com> wrote:
>
> Il 23/06/2015 18:34, Canek Peláez Valdés ha scritto:
> On Jun 23, 2015 3:23 AM, "Gmail" <serverplus@gmail.com> wrote:
> >
> > On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverplus@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.

Well, at least we know that's the problem. Could you set

[debug]
Enable=true

in /etc/gdm/custom.conf, and restart gdm.service and try to log in again?
It will fill the logs with lots of information, but it could tell us where
the exact problem is.

Also, when using journalctl please use the -b flag, so only the logs from
the last boot are printed.

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

On Tue, Jun 23, 2015 at 1:35 PM, Gmail <serverplus@gmail.com> wrote:
>
> Il 23/06/2015 18:34, Canek Peláez Valdés ha scritto: On Jun 23,
> 2015 3:23 AM, "Gmail" <serverplus@gmail.com> wrote:
>>
>> On Mon, Jun 22, 2015 at 6:40 AM, Gmail <serverplus@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.

Well, at least we know that's the problem. Could you set

[debug]
Enable=true

in /etc/gdm/custom.conf, and restart gdm.service and try to log in
again? It will fill the logs with lots of information, but it could
tell us where the exact problem is.

Also, when using journalctl please use the -b flag, so only the logs
from the last boot are printed.

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

giu 23 21:08:00 webandhardware gdm-session-worker[5149]:
<7>GdmSessionWorker: trying to get updated username
giu 23 21:08:00 webandhardware gdm-session-worker[5149]:
<7>GdmSessionWorker: PAM conversation returning 0: Successo
giu 23 21:08:02 webandhardware gdm-session-worker[5149]:
<7>GdmSessionWorker: authentication returned 7: Autenticazione fallita
giu 23 21:08:02 webandhardware gdm-session-worker[5149]:
<7>GdmSessionWorker: uninitializing PAM
giu 23 21:08:02 webandhardware gdm-session-worker[5149]:
<7>GdmSessionWorker: state NONE
giu 23 21:08:02 webandhardware gdm-session-worker[5149]:
<7>GdmSessionWorker: Unable to verify user
giu 23 21:08:03 webandhardware gdm-session-worker[5157]: <7>Enabling
debugging
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: connecting to address:
unix:abstract=/tmp/dbus-c3XhgnUx
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: calling 'ListCachedUsers'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Listing cached users, so not
setting loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: get_session_proxy
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Listing cached users, so not
setting loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Listing cached users, so not
setting loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: Ignoring non-user session c1 (class greeter)
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Listing cached users, so not
setting loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Listing cached users, so not
setting loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: ListCachedUsers finished, will set
loaded property after list is fully loaded
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: tracking new user with object path
/org/freedesktop/Accounts/User1004
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: unrefing manager owned by finished
ListCachedUsers call
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: trying to track new user with
username mist3r
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: finding user 'mist3r' state 1
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: waiting for user manager to load
before finding user 'mist3r'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: user mist3r is now loaded
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: user mist3r was not yet known,
adding it
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: tracking user 'mist3r'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: not yet loaded, so not emitting
user-added signal
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: no pending users, trying to set
loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Seat loaded, so now setting loaded
property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: user manager now loaded,
proceeding with fetch user request for user 'mist3r'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: finding user 'mist3r' state 2
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Looking for user 'mist3r' in
accounts service
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: sending user-changed signal for
user mist3r
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: sent user-changed signal for user
mist3r
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: updating user mist3r
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: Found object path of user
'mist3r': /org/freedesktop/Accounts/User1004
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: finding user 'mist3r' state 3
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: user 'mist3r' fetched
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: finished handling request for user
'mist3r'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: unrefing manager owned by fetch
user request
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: user mist3r is now loaded
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: sessions changed (user mist3r) num=0
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: no pending users, trying to set
loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>AccountsService: ActUserManager: already loaded, so not setting
loaded property
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionSettings: saved session is gnome
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: Saved session is gnome
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionSettings: saved language is it_IT.utf8
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: Saved language is it_IT.utf8
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: queuing setup for user: mist3r
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: attempting to change state to SETUP_COMPLETE
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: initializing PAM; service=gdm-password
username=mist3r seat=seat0
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: Set PAM environment variable: 'XDG_SEAT=seat0'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: state SETUP_COMPLETE
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: attempting to change state to AUTHENTICATED
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: authenticating user mist3r
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: 1 new messages received from PAM
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: username is 'mist3r'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: old-username='mist3r' new-username='mist3r'
giu 23 21:08:03 webandhardware gdm-session-worker[5157]:
<7>GdmSessionWorker: received pam message of type 1 with payload
'Password: '


I don't understand the meaning of these lines..

Regards

On Tue, Jun 23, 2015 at 2:21 PM, Gmail <serverplus@gmail.com> wrote:
>
> On Tue, Jun 23, 2015 at 1:35 PM, Gmail <serverplus@gmail.com> wrote:
[ ... ]
> I don't understand the meaning of these lines..

GDM it's printing its authentication protocol step by step, basically. It's
that all? I'm pretty sure it should be more messages. From the previous
log, mine has this different:

Jun 23 14:30:54 tenochtitlan gdm-session-worker[31715]:
<7>GdmSessionWorker: PAM conversation returning 0: Success

Could you please post the part of the logs around the message "PAM
conversation"?

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Il 23/06/2015 21:36, Canek Peláez Valdés ha scritto:
> On Tue, Jun 23, 2015 at 2:21 PM, Gmail <serverplus@gmail.com
> <mailto:serverplus@gmail.com>> wrote:
>>
>> On Tue, Jun 23, 2015 at 1:35 PM, Gmail <serverplus@gmail.com
> <mailto:serverplus@gmail.com>> wrote: [ ... ]
>> I don't understand the meaning of these lines..
>
> GDM it's printing its authentication protocol step by step,
> basically. It's that all? I'm pretty sure it should be more
> messages. From the previous log, mine has this different:
>
> Jun 23 14:30:54 tenochtitlan gdm-session-worker[31715]:
> <7>GdmSessionWorker: PAM conversation returning 0: Success
>
> Could you please post the part of the logs around the message "PAM
> conversation"?
>
> Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de
> Ciencias Universidad Nacional Autónoma de México


There's no more log...probably this is different with the debug enabled.

On Tue, Jun 23, 2015 at 4:06 PM, Gmail <serverplus@gmail.com> wrote:
>
> Il 23/06/2015 21:36, Canek Peláez Valdés ha scritto:
> > On Tue, Jun 23, 2015 at 2:21 PM, Gmail <serverplus@gmail.com
> > <mailto:serverplus@gmail.com>> wrote:
> >>
> >> On Tue, Jun 23, 2015 at 1:35 PM, Gmail <serverplus@gmail.com
> > <mailto:serverplus@gmail.com>> wrote: [ ... ]
> >> I don't understand the meaning of these lines..
> >
> > GDM it's printing its authentication protocol step by step,
> > basically. It's that all? I'm pretty sure it should be more
> > messages. From the previous log, mine has this different:
> >
> > Jun 23 14:30:54 tenochtitlan gdm-session-worker[31715]:
> > <7>GdmSessionWorker: PAM conversation returning 0: Success
> >
> > Could you please post the part of the logs around the message "PAM
> > conversation"?
> >
> > Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de
> > Ciencias Universidad Nacional Autónoma de México
>
>
> There's no more log...probably this is different with the debug enabled.

No, "debug" just shows up more messages. When using journalctl, the output
is shows trough the less command. I'm sure there is more of it.

Regads.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Il 24/06/2015 00:24, Canek Peláez Valdés ha scritto:
> On Tue, Jun 23, 2015 at 4:06 PM, Gmail <serverplus@gmail.com
> <mailto:serverplus@gmail.com>> wrote:
>>
>> Il 23/06/2015 21:36, Canek Peláez Valdés ha scritto:
>>> On Tue, Jun 23, 2015 at 2:21 PM, Gmail <serverplus@gmail.com
> <mailto:serverplus@gmail.com>
>>> <mailto:serverplus@gmail.com <mailto:serverplus@gmail.com>>>
>>> wrote:
>>>>
>>>> On Tue, Jun 23, 2015 at 1:35 PM, Gmail <serverplus@gmail.com
> <mailto:serverplus@gmail.com>
>>> <mailto:serverplus@gmail.com <mailto:serverplus@gmail.com>>>
>>> wrote:
> [ ... ]
>>>> I don't understand the meaning of these lines..
>>>
>>> GDM it's printing its authentication protocol step by step,
>>> basically. It's that all? I'm pretty sure it should be more
>>> messages. From the previous log, mine has this different:
>>>
>>> Jun 23 14:30:54 tenochtitlan gdm-session-worker[31715]:
>>> <7>GdmSessionWorker: PAM conversation returning 0: Success
>>>
>>> Could you please post the part of the logs around the message
>>> "PAM conversation"?
>>>
>>> Regards. -- Canek Peláez Valdés Profesor de asignatura,
>>> Facultad de Ciencias Universidad Nacional Autónoma de México
>>
>>
>> There's no more log...probably this is different with the debug
>> enabled.
>
> No, "debug" just shows up more messages. When using journalctl,
> the output is shows trough the less command. I'm sure there is more
> of it.
>
> Regads. -- Canek Peláez Valdés Profesor de asignatura, Facultad de
> Ciencias Universidad Nacional Autónoma de México


Today, the log is different, i'm crazying

giu 24 16:54:19 webandhardware gdm-password][5156]:
pam_tally2(gdm-password:auth): pam_get_uid; no such user
giu 24 16:54:26 webandhardware gdm-password][5156]: gkr-pam: error
looking up user information
giu 24 16:54:26 webandhardware gdm-password][5156]: gkr-pam: error
looking up user information
giu 24 16:54:29 webandhardware gdm-password][5160]:
pam_tally2(gdm-password:auth): pam_get_uid; no such user
giu 24 16:54:32 webandhardware gdm-password][5160]: gkr-pam: error
looking up user information
giu 24 16:54:32 webandhardware gdm-password][5160]: gkr-pam: error
looking up user information
giu 24 16:54:35 webandhardware gdm-password][5164]:
pam_tally2(gdm-password:auth): pam_get_uid; no such user
giu 24 16:54:38 webandhardware gdm-password][5164]: gkr-pam: error
looking up user information
giu 24 16:54:38 webandhardware gdm-password][5164]: gkr-pam: error
looking up user information

Regards

On Wed, Jun 24, 2015 at 10:40 AM, Gmail <serverplus@gmail.com> wrote:
>
> Il 24/06/2015 00:24, Canek Peláez Valdés ha scritto:
> > On Tue, Jun 23, 2015 at 4:06 PM, Gmail <serverplus@gmail.com
> > <mailto:serverplus@gmail.com>> wrote:
> >>
> >> Il 23/06/2015 21:36, Canek Peláez Valdés ha scritto:
> >>> On Tue, Jun 23, 2015 at 2:21 PM, Gmail <serverplus@gmail.com
> > <mailto:serverplus@gmail.com>
> >>> <mailto:serverplus@gmail.com <mailto:serverplus@gmail.com>>>
> >>> wrote:
> >>>>
> >>>> On Tue, Jun 23, 2015 at 1:35 PM, Gmail <serverplus@gmail.com
> > <mailto:serverplus@gmail.com>
> >>> <mailto:serverplus@gmail.com <mailto:serverplus@gmail.com>>>
> >>> wrote:
> > [ ... ]
> >>>> I don't understand the meaning of these lines..
> >>>
> >>> GDM it's printing its authentication protocol step by step,
> >>> basically. It's that all? I'm pretty sure it should be more
> >>> messages. From the previous log, mine has this different:
> >>>
> >>> Jun 23 14:30:54 tenochtitlan gdm-session-worker[31715]:
> >>> <7>GdmSessionWorker: PAM conversation returning 0: Success
> >>>
> >>> Could you please post the part of the logs around the message
> >>> "PAM conversation"?
> >>>
> >>> Regards. -- Canek Peláez Valdés Profesor de asignatura,
> >>> Facultad de Ciencias Universidad Nacional Autónoma de México
> >>
> >>
> >> There's no more log...probably this is different with the debug
> >> enabled.
> >
> > No, "debug" just shows up more messages. When using journalctl,
> > the output is shows trough the less command. I'm sure there is more
> > of it.
> >
> > Regads. -- Canek Peláez Valdés Profesor de asignatura, Facultad de
> > Ciencias Universidad Nacional Autónoma de México
>
>
> Today, the log is different, i'm crazying
>
> giu 24 16:54:19 webandhardware gdm-password][5156]:
> pam_tally2(gdm-password:auth): pam_get_uid; no such user
> giu 24 16:54:26 webandhardware gdm-password][5156]: gkr-pam: error
> looking up user information
> giu 24 16:54:26 webandhardware gdm-password][5156]: gkr-pam: error
> looking up user information
> giu 24 16:54:29 webandhardware gdm-password][5160]:
> pam_tally2(gdm-password:auth): pam_get_uid; no such user
> giu 24 16:54:32 webandhardware gdm-password][5160]: gkr-pam: error
> looking up user information
> giu 24 16:54:32 webandhardware gdm-password][5160]: gkr-pam: error
> looking up user information
> giu 24 16:54:35 webandhardware gdm-password][5164]:
> pam_tally2(gdm-password:auth): pam_get_uid; no such user
> giu 24 16:54:38 webandhardware gdm-password][5164]: gkr-pam: error
> looking up user information
> giu 24 16:54:38 webandhardware gdm-password][5164]: gkr-pam: error
> looking up user information

I have no idea where gkr-pam comes from. Cold be gnome-keyring, but that
one is pam_gnome_keyring.so. What does

grep gkr /etc/pam.d/*

shows?

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Il 24/06/2015 21:10, Canek Peláez Valdés ha scritto:
What does

grep gkr /etc/pam.d/*

shows?

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

shows nothing

On Wed, Jun 24, 2015 at 2:13 PM, Gmail <serverplus@gmail.com> wrote:
>
> Il 24/06/2015 21:10, Canek Peláez Valdés ha scritto:
> What does
>
> grep gkr /etc/pam.d/*
>
> shows?
>
> Regards.
> --
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
>
> shows nothing

Well that's weird. Where does gkr-pam comes from?

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Il 24/06/2015 22:06, Canek Peláez Valdés ha scritto:
> On Wed, Jun 24, 2015 at 2:13 PM, Gmail <serverplus@gmail.com
> <mailto:serverplus@gmail.com>> wrote:
>>
>> Il 24/06/2015 21:10, Canek Peláez Valdés ha scritto: What does
>>
>> grep gkr /etc/pam.d/*
>>
>> shows?
>>
>> Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad
>> de Ciencias Universidad Nacional Autónoma de México
>>
>> shows nothing
>
> Well that's weird. Where does gkr-pam comes from?
>
> Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de
> Ciencias Universidad Nacional Autónoma de México


I never choose to install it.

I don't know, but seems that i'm not the only one.

https://forums.gentoo.org/viewtopic-t-980578-view-previous.html?sid=d82506cf1c95af7f8ee5bdfb20f5f7fd

https://archives.gentoo.org/gentoo-user/message/da80b62fddde004d8edc0879266065ce

I'm trying these solutions

Regards

And unfortunately...no one works
Il 24/Giu/2015 22:29, "Gmail" <serverplus@gmail.com> ha scritto:

> Il 24/06/2015 22:06, Canek Peláez Valdés ha scritto:
> > On Wed, Jun 24, 2015 at 2:13 PM, Gmail <serverplus@gmail.com
> > <mailto:serverplus@gmail.com>> wrote:
> >>
> >> Il 24/06/2015 21:10, Canek Peláez Valdés ha scritto: What does
> >>
> >> grep gkr /etc/pam.d/*
> >>
> >> shows?
> >>
> >> Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad
> >> de Ciencias Universidad Nacional Autónoma de México
> >>
> >> shows nothing
> >
> > Well that's weird. Where does gkr-pam comes from?
> >
> > Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de
> > Ciencias Universidad Nacional Autónoma de México
>
>
> I never choose to install it.
>
> I don't know, but seems that i'm not the only one.
>
>
> https://forums.gentoo.org/viewtopic-t-980578-view-previous.html?sid=d82506cf1c95af7f8ee5bdfb20f5f7fd
>
>
> https://archives.gentoo.org/gentoo-user/message/da80b62fddde004d8edc0879266065ce
>
> I'm trying these solutions
>
> Regards
>