Comment # 2 on bug 1182835 from Walddys Emmanuel Dorrejo C���spedes

the logs show nothing.

(In reply to Fabian Vogt from comment #1)
> How did you log into the system? Apparently pam_systemd either didn't run or
> failed for some reason.
> 
> Please attach the full journal of an affected boot with "journalctl -b".

mar 01 18:08:46 microos-labs systemd[2385]: Queued start job for default target
Main User Target.
mar 01 18:08:46 microos-labs systemd[2385]: Reached target Paths.
mar 01 18:08:46 microos-labs systemd[2385]: Reached target Timers.
mar 01 18:08:46 microos-labs sshd[2392]: Starting session: shell on pts/0 for
wdorrejo from 192.168.122.1 port 37928 id 0
mar 01 18:08:46 microos-labs systemd[2385]: Starting D-Bus User Message Bus
Socket.
mar 01 18:08:46 microos-labs systemd[2385]: Listening on D-Bus User Message Bus
Socket.
mar 01 18:08:46 microos-labs systemd[2385]: Reached target Sockets.
mar 01 18:08:46 microos-labs systemd[2385]: Reached target Basic System.
mar 01 18:08:46 microos-labs systemd[2385]: Reached target Main User Target.
mar 01 18:08:46 microos-labs systemd[2385]: Startup finished in 69ms.
mar 01 18:09:22 microos-labs sudo[2433]: wdorrejo : TTY=pts/0 ;
PWD=/home/wdorrejo ; USER=astian ; COMMAND=/bin/bash
mar 01 18:09:22 microos-labs sudo[2433]: pam_unix(sudo:session): session opened
for user astian(uid=1001) by wdorrejo(uid=1000)
mar 01 18:11:08 microos-labs sudo[2433]: pam_unix(sudo:session): session closed
for user astian
lines 35-94/94 (END)