[Résolu] auto login avec Debian 10 Mate

Debeee · 30-12-2018 16:58:40

Bonjour,
je viens de m'installer une Debian 10 testing avec Mate comme environnement de bureau.
Pour avoir un démarrage sans taper mon mot de passe, j'ai fait ce que j'avais fait avec Jessie il y a 4 ans : dans le fichier /etc/lightdm/lightdm.conf, j'ai décommenté et renseigné les deux lignes suivantes :

autologin-user= moimeme
autologin-user-timeout=0

J'ai regardé sur plusieurs forums, ça semble être la procédure en cours encore actuellement.

Le hic, c'est que mon boot prend le double de temps !
En session manuelle, j'ai 20s pour arriver à la fenêtre de choix de login, puis moins de 5s ensuite pour avoir le bureau => total, 25s max.
En auto, je suis entre 55s et 1'05, j'ai un écran noir pendant un grand moment…

Quelqu'un a une idée du pb ?

Merci !

Dernière modification par Debeee (26-12-2019 15:16:01)

anonyme · 31-12-2018 00:26:09

Bonjour,

Pas d'idée précise mais le fichier /var/log/lightdm/x-0.log contient peut-être des informations utiles.

anonyme · 31-12-2018 05:46:26

Bonjour

tu a le détail dans /var/log/lightdm/lightdm.log
tu a aussi /var/log/auth.log
peut être des modifications sur le comportement sur Buster pour l'auto loging.
a priori tu n'a pas d' échec de loging , juste le temps est anormalement long pour arriver au bureau.
je n'utilise pas cette option sur Mate.

Debeee · 31-12-2018 14:36:14

bonjour,
alors j'ai fait deux manips : la première, j'ai récupéré les fichiers avec log manuel, la 2e avec log auto

le fichier /var/log/lightdm/x-0.log ne semble pas très intéressant, et dans les deux cas, c'est strictement la même chose à part l'heure :

X.Org X Server 1.20.3

X Protocol Version 11, Revision 0

Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian

Current Operating System: Linux domeee 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64

Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-1-amd64 root=UUID=536c2b1f-d5b8-4ef5-a463-09da7c3dc3d6 ro quiet

Build Date: 25 October 2018  06:15:23PM

xorg-server 2:1.20.3-1 (https://www.debian.org/support) 

Current version of pixman: 0.36.0

  Before reporting problems, check http://wiki.x.org

  to make sure that you have the latest version.

Markers: (--) probed, (**) from config file, (==) default setting,

  (++) from command line, (!!) notice, (II) informational,

  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 31 13:50:43 2018

(==) Using system config directory "/usr/share/X11/xorg.conf.d"

(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.

(II) AIGLX: Suspending AIGLX clients for VT switch

pour le fichier /var/log/lightdm/lightdm.log, voilà la version en log manuel :

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log

[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=481

[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d

[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf

[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d

[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d

[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf

[+0.00s] DEBUG: Registered seat module local

[+0.00s] DEBUG: Registered seat module xremote

[+0.00s] DEBUG: Registered seat module unity

[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager

[+0.05s] DEBUG: Monitoring logind for seats

[+0.05s] DEBUG: New seat added from logind: seat0

[+0.05s] DEBUG: Seat seat0: Loading properties from config section Seat:*

[+0.05s] DEBUG: Seat seat0: Starting

[+0.05s] DEBUG: Seat seat0: Creating greeter session

[+0.05s] DEBUG: Seat seat0: Creating display server of type x

[+0.05s] DEBUG: posix_spawn avoided (fd close requested) 

[+0.06s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)

[+0.06s] DEBUG: Using VT 7

[+0.06s] DEBUG: Seat seat0: Starting local X display on VT 7

[+0.06s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log

[+0.06s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0

[+0.06s] DEBUG: XServer 0: Launching X Server

[+0.06s] DEBUG: Launching process 503: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

[+0.06s] DEBUG: XServer 0: Waiting for ready signal from X server :0

[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager

[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0

[+0.06s] DEBUG: Loading users from org.freedesktop.Accounts

[+0.06s] DEBUG: User /org/freedesktop/Accounts/User1000 added

[+0.18s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 

[+0.86s] DEBUG: Got signal 10 from process 503

[+0.86s] DEBUG: XServer 0: Got signal from X server :0

[+0.86s] DEBUG: XServer 0: Connecting to XServer :0

[+0.97s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+0.98s] DEBUG: Seat seat0: Display server ready, starting session authentication

[+0.98s] DEBUG: Session pid=561: Started with service 'lightdm-greeter', username 'lightdm'

[+1.02s] DEBUG: Session pid=561: Authentication complete with return value 0: Success

[+1.02s] DEBUG: Seat seat0: Session authenticated, running command

[+1.02s] DEBUG: Session pid=561: Running command /usr/sbin/lightdm-gtk-greeter

[+1.02s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm

[+1.02s] DEBUG: Session pid=561: Logging to /var/log/lightdm/seat0-greeter.log

[+1.16s] DEBUG: Activating VT 7

[+1.16s] DEBUG: Activating login1 session c1

[+1.16s] DEBUG: Seat seat0 changes active session to c1

[+1.16s] DEBUG: Session c1 is already active

[+1.47s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false

[+2.22s] DEBUG: Greeter start authentication

[+2.22s] DEBUG: Session pid=606: Started with service 'lightdm', username '(null)'

[+2.23s] DEBUG: Session pid=606: Got 1 message(s) from PAM

[+2.23s] DEBUG: Prompt greeter with 1 message(s)

[+6.59s] DEBUG: Greeter start authentication for domeee

[+6.59s] DEBUG: Session pid=606: Sending SIGTERM

[+6.59s] DEBUG: Session pid=609: Started with service 'lightdm', username 'domeee'

[+6.59s] DEBUG: Session pid=606: Terminated with signal 15

[+6.59s] DEBUG: Session: Failed during authentication

[+6.59s] DEBUG: Seat seat0: Session stopped

[+6.60s] DEBUG: Session pid=609: Got 1 message(s) from PAM

[+6.60s] DEBUG: Prompt greeter with 1 message(s)

[+10.40s] DEBUG: Continue authentication

[+10.43s] DEBUG: Session pid=609: Authentication complete with return value 0: Success

[+10.43s] DEBUG: Authenticate result for user domeee: Success

[+10.43s] DEBUG: User domeee authorized

[+10.47s] DEBUG: Greeter requests session lightdm-xsession

[+10.47s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session

[+10.47s] DEBUG: Terminating login1 session c1

[+10.48s] DEBUG: Session pid=561: Sending SIGTERM

[+10.49s] DEBUG: Greeter closed communication channel

[+10.49s] DEBUG: Session pid=561: Exited with return value 0

[+10.49s] DEBUG: Seat seat0: Session stopped

[+10.49s] DEBUG: Seat seat0: Greeter stopped, running session

[+10.49s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0

[+10.49s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+10.49s] DEBUG: Session pid=609: Running command /etc/X11/Xsession default

[+10.49s] DEBUG: Creating shared data directory /var/lib/lightdm/data/domeee

[+10.49s] DEBUG: Session pid=609: Logging to .xsession-errors

[+10.68s] DEBUG: Activating VT 7

[+10.68s] DEBUG: Activating login1 session 2

[+10.68s] DEBUG: Seat seat0 changes active session to 

[+10.68s] DEBUG: Seat seat0 changes active session to 2

[+10.68s] DEBUG: Session 2 is already active

[+209.01s] DEBUG: Seat seat0: Creating greeter session

[+209.01s] DEBUG: Seat seat0: Creating display server of type x

[+209.01s] DEBUG: Using VT 8

[+209.01s] DEBUG: Seat seat0: Starting local X display on VT 8

[+209.01s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log

[+209.01s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1

[+209.01s] DEBUG: XServer 1: Launching X Server

[+209.01s] DEBUG: Launching process 1092: /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch

[+209.01s] DEBUG: XServer 1: Waiting for ready signal from X server :1

[+209.22s] DEBUG: Seat seat0 changes active session to 

[+209.70s] DEBUG: Got signal 10 from process 1092

[+209.70s] DEBUG: XServer 1: Got signal from X server :1

[+209.70s] DEBUG: XServer 1: Connecting to XServer :1

[+209.73s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+209.73s] DEBUG: Seat seat0: Display server ready, starting session authentication

[+209.73s] DEBUG: Session pid=1109: Started with service 'lightdm-greeter', username 'lightdm'

[+209.76s] DEBUG: Session pid=1109: Authentication complete with return value 0: Success

[+209.76s] DEBUG: Seat seat0: Session authenticated, running command

[+209.76s] DEBUG: Session pid=1109: Running command /usr/sbin/lightdm-gtk-greeter

[+209.76s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm

[+209.76s] DEBUG: Session pid=1109: Logging to /var/log/lightdm/seat0-greeter.log

[+209.97s] DEBUG: Activating VT 8

[+209.97s] DEBUG: Locking login1 session 2

[+209.97s] DEBUG: Activating login1 session c2

[+209.98s] DEBUG: Seat seat0 changes active session to c2

[+209.98s] DEBUG: Session c2 is already active

[+210.15s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false

[+210.72s] DEBUG: Greeter start authentication

[+210.72s] DEBUG: Session pid=1173: Started with service 'lightdm', username '(null)'

[+210.73s] DEBUG: Session pid=1173: Got 1 message(s) from PAM

[+210.73s] DEBUG: Prompt greeter with 1 message(s)

[+214.44s] DEBUG: Greeter start authentication for root

[+214.44s] DEBUG: Session pid=1173: Sending SIGTERM

[+214.44s] DEBUG: Session pid=1176: Started with service 'lightdm', username 'root'

[+214.44s] DEBUG: Session pid=1173: Terminated with signal 15

[+214.44s] DEBUG: Session: Failed during authentication

[+214.44s] DEBUG: Seat seat0: Session stopped

[+214.45s] DEBUG: Session pid=1176: Got 1 message(s) from PAM

[+214.45s] DEBUG: Prompt greeter with 1 message(s)

[+219.03s] DEBUG: Continue authentication

[+219.06s] DEBUG: Session pid=1176: Authentication complete with return value 0: Success

[+219.06s] DEBUG: Authenticate result for user root: Success

[+219.06s] DEBUG: User root authorized

[+219.09s] DEBUG: Greeter requests session lightdm-xsession

[+219.09s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session

[+219.09s] DEBUG: Terminating login1 session c2

[+219.10s] DEBUG: Session pid=1109: Sending SIGTERM

[+219.13s] DEBUG: Greeter closed communication channel

[+219.13s] DEBUG: Session pid=1109: Exited with return value 0

[+219.13s] DEBUG: Seat seat0: Session stopped

[+219.13s] DEBUG: Seat seat0: Greeter stopped, running session

[+219.13s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session1

[+219.13s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+219.15s] DEBUG: Session pid=1176: Running command /etc/X11/Xsession default

[+219.15s] DEBUG: Creating shared data directory /var/lib/lightdm/data/root

[+219.15s] DEBUG: Session pid=1176: Logging to .xsession-errors

[+219.33s] DEBUG: Activating VT 8

[+219.33s] DEBUG: Activating login1 session 5

[+219.33s] DEBUG: Seat seat0 changes active session to 

[+219.33s] DEBUG: Seat seat0 changes active session to 5

[+219.33s] DEBUG: Session 5 is already active

et en mode auto :

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log

[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=499

[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d

[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf

[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d

[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d

[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf

[+0.00s] DEBUG: Registered seat module local

[+0.00s] DEBUG: Registered seat module xremote

[+0.00s] DEBUG: Registered seat module unity

[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager

[+0.01s] DEBUG: Monitoring logind for seats

[+0.01s] DEBUG: New seat added from logind: seat0

[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*

[+0.01s] DEBUG: Seat seat0: Starting

[+0.01s] DEBUG: Seat seat0: Creating user session

[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts

[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added

[+0.06s] DEBUG: Seat seat0: Creating display server of type x

[+0.06s] DEBUG: posix_spawn avoided (fd close requested) 

[+0.06s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)

[+0.06s] DEBUG: Using VT 7

[+0.06s] DEBUG: Seat seat0: Starting local X display on VT 7

[+0.06s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log

[+0.07s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0

[+0.07s] DEBUG: XServer 0: Launching X Server

[+0.07s] DEBUG: Launching process 538: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

[+0.07s] DEBUG: XServer 0: Waiting for ready signal from X server :0

[+0.07s] DEBUG: Acquired bus name org.freedesktop.DisplayManager

[+0.07s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0

[+0.07s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 

[+0.09s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 

[+0.74s] DEBUG: Got signal 10 from process 538

[+0.74s] DEBUG: XServer 0: Got signal from X server :0

[+0.74s] DEBUG: XServer 0: Connecting to XServer :0

[+0.85s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+0.85s] DEBUG: Seat seat0: Display server ready, starting session authentication

[+0.85s] DEBUG: Session pid=560: Started with service 'lightdm-autologin', username 'domeee'

[+0.90s] DEBUG: Session pid=560: Authentication complete with return value 0: Success

[+0.90s] DEBUG: Seat seat0: Session authenticated, running command

[+0.90s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0

[+0.90s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+0.90s] DEBUG: Session pid=560: Running command /etc/X11/Xsession default

[+0.90s] DEBUG: Creating shared data directory /var/lib/lightdm/data/domeee

[+0.90s] DEBUG: Session pid=560: Logging to .xsession-errors

[+1.04s] DEBUG: Activating VT 7

[+1.04s] DEBUG: Activating login1 session 1

[+1.04s] DEBUG: Seat seat0 changes active session to 1

[+1.04s] DEBUG: Session 1 is already active

[+92.65s] DEBUG: Seat seat0: Creating greeter session

[+92.65s] DEBUG: Seat seat0: Creating display server of type x

[+92.65s] DEBUG: Using VT 8

[+92.65s] DEBUG: Seat seat0: Starting local X display on VT 8

[+92.65s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log

[+92.65s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1

[+92.65s] DEBUG: XServer 1: Launching X Server

[+92.65s] DEBUG: Launching process 886: /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch

[+92.65s] DEBUG: XServer 1: Waiting for ready signal from X server :1

[+92.87s] DEBUG: Seat seat0 changes active session to 

[+93.35s] DEBUG: Got signal 10 from process 886

[+93.35s] DEBUG: XServer 1: Got signal from X server :1

[+93.35s] DEBUG: XServer 1: Connecting to XServer :1

[+93.37s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+93.38s] DEBUG: Seat seat0: Display server ready, starting session authentication

[+93.38s] DEBUG: Session pid=899: Started with service 'lightdm-greeter', username 'lightdm'

[+93.40s] DEBUG: Session pid=899: Authentication complete with return value 0: Success

[+93.40s] DEBUG: Seat seat0: Session authenticated, running command

[+93.40s] DEBUG: Session pid=899: Running command /usr/sbin/lightdm-gtk-greeter

[+93.40s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm

[+93.40s] DEBUG: Session pid=899: Logging to /var/log/lightdm/seat0-greeter.log

[+93.54s] DEBUG: Activating VT 8

[+93.54s] DEBUG: Locking login1 session 1

[+93.55s] DEBUG: Activating login1 session c1

[+93.55s] DEBUG: Seat seat0 changes active session to c1

[+93.55s] DEBUG: Session c1 is already active

[+93.71s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false

[+94.29s] DEBUG: Greeter start authentication

[+94.29s] DEBUG: Session pid=944: Started with service 'lightdm', username '(null)'

[+94.30s] DEBUG: Session pid=944: Got 1 message(s) from PAM

[+94.30s] DEBUG: Prompt greeter with 1 message(s)

[+97.19s] DEBUG: Greeter start authentication for root

[+97.19s] DEBUG: Session pid=944: Sending SIGTERM

[+97.19s] DEBUG: Session pid=947: Started with service 'lightdm', username 'root'

[+97.19s] DEBUG: Session pid=944: Terminated with signal 15

[+97.19s] DEBUG: Session: Failed during authentication

[+97.19s] DEBUG: Seat seat0: Session stopped

[+97.20s] DEBUG: Session pid=947: Got 1 message(s) from PAM

[+97.20s] DEBUG: Prompt greeter with 1 message(s)

[+101.71s] DEBUG: Continue authentication

[+101.75s] DEBUG: Session pid=947: Authentication complete with return value 0: Success

[+101.75s] DEBUG: Authenticate result for user root: Success

[+101.75s] DEBUG: User root authorized

[+101.80s] DEBUG: Greeter requests session lightdm-xsession

[+101.80s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session

[+101.80s] DEBUG: Terminating login1 session c1

[+101.81s] DEBUG: Session pid=899: Sending SIGTERM

[+101.83s] DEBUG: Greeter closed communication channel

[+101.83s] DEBUG: Session pid=899: Exited with return value 0

[+101.83s] DEBUG: Seat seat0: Session stopped

[+101.83s] DEBUG: Seat seat0: Greeter stopped, running session

[+101.83s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session1

[+101.83s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 

[+101.83s] DEBUG: Session pid=947: Running command /etc/X11/Xsession default

[+101.83s] DEBUG: Creating shared data directory /var/lib/lightdm/data/root

[+101.83s] DEBUG: Session pid=947: Logging to .xsession-errors

[+102.06s] DEBUG: Activating VT 8

[+102.06s] DEBUG: Activating login1 session 4

[+102.06s] DEBUG: Seat seat0 changes active session to 

[+102.06s] DEBUG: Seat seat0 changes active session to 4

[+102.06s] DEBUG: Session 4 is already active

voilà, si quelqu'un sait décrypter ces hiéroglyphes...

NB : le log auto a duré environ 1"30, ce qui peut correspondre aux 93s du fichier

Dernière modification par Debeee (31-12-2018 14:38:14)

anonyme · 31-12-2018 15:09:21

Bonjour

j'ai la même chose que toi sans l auto loging , ça semble normal
par contre avec l auto loging ça passe de +1.04s à +92.65s sans détails

avec buster + mate + lightdm il n'y aurait pas un bug en cour ?

pourquoi le début du log de X sur ton #4 , a priori tu n'a pas de soucis avec le serveur X ?

voir le syslog si plus bavard "/var/log/syslog"

Debeee · 31-12-2018 15:48:04

Merci de te plonger là dedans !
En fait, oui, ça pue le gros bug (testing, ne l'oublions pas...), et en prime, j'ai quand même un truc pas cool, y'a pas d'item "users" dans le centre de contrôle.
j'ai une mint lmde II (basée sur jessie) sur cet ordi, il y a cet item dans le centre de contrôle, et il figure aussi dans la doc de mate de ma version debian 10.
J'ai fait une mise à jour complète + redémarrage => rien de nouveau (de visible !)

le syslog est très long, j'ai récupéré le morceau qui doit correspondre au boot en mode auto :

Dec 31 14:08:00 domeee systemd[1]: Starting Disk Manager...

Dec 31 14:08:00 domeee cron[415]: (CRON) INFO (pidfile fd = 3)

Dec 31 14:08:00 domeee systemd[1]: Starting Modem Manager...

Dec 31 14:08:00 domeee systemd[1]: Started Daily rotation of log files.

Dec 31 14:08:00 domeee systemd[1]: Reached target Timers.

Dec 31 14:08:00 domeee cron[415]: (CRON) INFO (Running @reboot jobs)

Dec 31 14:08:00 domeee avahi-daemon[400]: Successfully called chroot().

Dec 31 14:08:00 domeee avahi-daemon[400]: Successfully dropped remaining capabilities.

Dec 31 14:08:00 domeee wpa_supplicant[410]: Successfully initialized wpa_supplicant

Dec 31 14:08:00 domeee avahi-daemon[400]: No service file found in /etc/avahi/services.

Dec 31 14:08:00 domeee avahi-daemon[400]: Network interface enumeration completed.

Dec 31 14:08:00 domeee avahi-daemon[400]: Server startup complete. Host name is domeee.local. Local service cookie is 2009103325.

Dec 31 14:08:00 domeee systemd[1]: Started System Logging Service.

Dec 31 14:08:00 domeee systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.

Dec 31 14:08:00 domeee udisksd[421]: udisks daemon version 2.8.1 starting

Dec 31 14:08:00 domeee bluetoothd[416]: Bluetooth daemon 5.50

Dec 31 14:08:00 domeee bluetoothd[416]: Starting SDP server

Dec 31 14:08:00 domeee systemd[1]: Started Raise network interfaces.

Dec 31 14:08:00 domeee udisksd[421]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory

Dec 31 14:08:00 domeee systemd[1]: Reached target Sound Card.

Dec 31 14:08:00 domeee systemd[1]: Started Bluetooth service.

Dec 31 14:08:00 domeee kernel: [    5.143110] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Dec 31 14:08:00 domeee kernel: [    5.143111] Bluetooth: BNEP filters: protocol multicast

Dec 31 14:08:00 domeee kernel: [    5.143116] Bluetooth: BNEP socket layer initialized

Dec 31 14:08:00 domeee bluetoothd[416]: Bluetooth management interface 1.14 initialized

Dec 31 14:08:00 domeee ModemManager[428]: <info>  ModemManager (version 1.8.2) starting in system bus...

Dec 31 14:08:00 domeee dbus-daemon[403]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.5' (uid=0 pid=416 comm="/usr/lib/bluetooth/bluetoothd ")

Dec 31 14:08:00 domeee bluetoothd[416]: Sap driver initialization failed.

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.2336] NetworkManager (version 1.14.4) is starting... (for the first time)

Dec 31 14:08:00 domeee bluetoothd[416]: sap-server: Operation not permitted (1)

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.2336] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)

Dec 31 14:08:00 domeee udisksd[421]: Failed to load the 'mdraid' libblockdev plugin

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.2376] wifi-nl80211: (wlp2s0): using nl80211 for WiFi device control

Dec 31 14:08:00 domeee dbus-daemon[403]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.4' (uid=0 pid=421 comm="/usr/lib/udisks2/udisksd ")

Dec 31 14:08:00 domeee systemd[1]: Started Avahi mDNS/DNS-SD Stack.

Dec 31 14:08:00 domeee systemd[1]: Started WPA supplicant.

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.2510] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"

Dec 31 14:08:00 domeee systemd[1]: Starting Authorization Manager...

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.2541] manager[0x5577013df030]: monitoring kernel firmware directory '/lib/firmware'.

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.2542] monitoring ifupdown state file '/run/network/ifstate'.

Dec 31 14:08:00 domeee systemd[1]: Starting Hostname Service...

Dec 31 14:08:00 domeee systemd[1]: Started Make remote CUPS printers available locally.

Dec 31 14:08:00 domeee systemd[1]: Reached target Bluetooth.

Dec 31 14:08:00 domeee systemd[1]: Started Network Manager.

Dec 31 14:08:00 domeee systemd[1]: Reached target Network.

Dec 31 14:08:00 domeee systemd[1]: Starting Permit User Sessions...

Dec 31 14:08:00 domeee systemd[1]: Started Permit User Sessions.

Dec 31 14:08:00 domeee polkitd[458]: started daemon version 0.105 using authority implementation `local' version `0.105'

Dec 31 14:08:00 domeee dbus-daemon[403]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'

Dec 31 14:08:00 domeee accounts-daemon[401]: started daemon version 0.6.45

Dec 31 14:08:00 domeee dbus-daemon[403]: [system] Successfully activated service 'org.freedesktop.hostname1'

Dec 31 14:08:00 domeee udisksd[421]: Acquired the name org.freedesktop.UDisks2 on the system message bus

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.4056] hostname: hostname: using hostnamed

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.4057] hostname: hostname changed from (none) to "domeee"

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.4060] dns-mgr[0x5577013eb130]: init: dns=default, rc-manager=resolvconf

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.4073] rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.4077] manager[0x5577013df030]: rfkill: WiFi hardware radio set enabled

Dec 31 14:08:00 domeee NetworkManager[408]: <info>  [1546261680.4077] manager[0x5577013df030]: rfkill: WWAN hardware radio set enabled

Dec 31 14:08:00 domeee dbus-daemon[403]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=408 comm="/usr/sbin/NetworkManager --no-daemon ")

Dec 31 14:08:01 domeee kernel: [    5.986167] psmouse serio2: sentelic: Finger Sensing Pad, hw: 14.4.1, sn: 69171, sw: 1.1.0-K

Dec 31 14:08:01 domeee kernel: [    6.105043] Console: switching to colour frame buffer device 170x48

Dec 31 14:08:01 domeee kernel: [    6.127958] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device

Dec 31 14:08:01 domeee systemd[1]: Started Getty on tty1.

Dec 31 14:08:01 domeee systemd[1]: Reached target Login Prompts.

Dec 31 14:08:01 domeee systemd[1]: Starting Light Display Manager...

Dec 31 14:08:01 domeee systemd[1]: Started Authorization Manager.

Dec 31 14:08:01 domeee systemd[1]: Started Accounts Service.

Dec 31 14:08:01 domeee systemd[1]: Started Modem Manager.

Dec 31 14:08:01 domeee systemd[1]: Started Hostname Service.

Dec 31 14:08:01 domeee systemd[1]: Started Disk Manager.

Dec 31 14:08:01 domeee systemd[1]: Started Login Service.

Dec 31 14:08:01 domeee systemd[1]: Starting Network Manager Script Dispatcher Service...

Dec 31 14:08:01 domeee systemd[1]: Reached target Multi-User System.

Dec 31 14:08:01 domeee dbus-daemon[403]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2755] ifupdown:       interface-parser: parsing file /etc/network/interfaces

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2755] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*

Dec 31 14:08:01 domeee NetworkManager[408]: <warn>  [1546261681.2756] ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2757] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2757] ifupdown: management mode: unmanaged

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2757] settings: Loaded settings plugin: SettingsPluginIfupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.4/libnm-settings-plugin-ifupdown.so")

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2757] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2820] keyfile: new connection /etc/NetworkManager/system-connections/freebox_KFTLDQ.nmconnection (bed6b478-8705-4c08-b1e4-36b5f18339f6,"freebox_KFTLDQ")

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2836] keyfile: new connection /etc/NetworkManager/system-connections/Wired connection 1 (39c631af-4a77-48e4-8886-0c640d81c64a,"Wired connection 1")

Dec 31 14:08:01 domeee systemd[1]: Started Network Manager Script Dispatcher Service.

Dec 31 14:08:01 domeee systemd[1]: Created slice system-systemd\x2dbacklight.slice.

Dec 31 14:08:01 domeee systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2911] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2921] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file

Dec 31 14:08:01 domeee kernel: [    6.207764] input: FSPPS/2 Sentelic FingerSensingPad as /devices/platform/i8042/serio2/input/input6

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.2971] manager: Networking is enabled by state file

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3043] dhcp-init: Using DHCP client 'dhclient'

Dec 31 14:08:01 domeee nm-dispatcher: req:1 'hostname': new request (1 scripts)

Dec 31 14:08:01 domeee nm-dispatcher: req:1 'hostname': start running ordered scripts...

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3125] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.4/libnm-device-plugin-wwan.so)

Dec 31 14:08:01 domeee systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3209] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.4/libnm-device-plugin-team.so)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3323] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.4/libnm-device-plugin-bluetooth.so)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3343] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.4/libnm-device-plugin-wifi.so)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3353] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.4/libnm-device-plugin-adsl.so)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3376] device (lo): carrier: link connected

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3380] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3402] manager: (enp3s0f2): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.3440] device (enp3s0f2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

Dec 31 14:08:01 domeee kernel: [    6.259233] IPv6: ADDRCONF(NETDEV_UP): enp3s0f2: link is not ready

Dec 31 14:08:01 domeee kernel: [    6.260261] r8169 0000:03:00.2: firmware: direct-loading firmware rtl_nic/rtl8402-1.fw

Dec 31 14:08:01 domeee kernel: [    6.261699] Generic PHY r8169-302:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-302:00, irq=IGNORE)

Dec 31 14:08:01 domeee systemd[1]: Started Light Display Manager.

Dec 31 14:08:01 domeee systemd[1]: Reached target Graphical Interface.

Dec 31 14:08:01 domeee systemd[1]: Starting Update UTMP about System Runlevel Changes...

Dec 31 14:08:01 domeee systemd[1]: Started Update UTMP about System Runlevel Changes.

Dec 31 14:08:01 domeee systemd[1]: Startup finished in 3.071s (kernel) + 3.211s (userspace) = 6.283s.

Dec 31 14:08:01 domeee kernel: [    6.419625] IPv6: ADDRCONF(NETDEV_UP): enp3s0f2: link is not ready

Dec 31 14:08:01 domeee nm-dispatcher: req:2 'connectivity-change': new request (1 scripts)

Dec 31 14:08:01 domeee nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.5119] device (wlp2s0): driver supports Access Point (AP) mode

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.5128] manager: (wlp2s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.5153] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

Dec 31 14:08:01 domeee kernel: [    6.430191] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

Dec 31 14:08:01 domeee kernel: [    6.443954] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x0

Dec 31 14:08:01 domeee kernel: [    6.541698] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x0

Dec 31 14:08:01 domeee kernel: [    6.605677] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.7061] device (wlp2s0): set-hw-addr: set MAC address to 2A:11:31:DF:24:95 (scanning)

Dec 31 14:08:01 domeee kernel: [    6.633750] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x0

Dec 31 14:08:01 domeee kernel: [    6.729081] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x0

Dec 31 14:08:01 domeee kernel: [    6.789041] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.8839] bluez: use BlueZ version 5

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.8860] supplicant: wpa_supplicant running

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.8860] device (wlp2s0): supplicant interface state: init -> starting

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.8861] modem-manager: ModemManager available

Dec 31 14:08:01 domeee NetworkManager[408]: <info>  [1546261681.8880] bluez5: NAP: added interface 0C:D2:92:B8:60:6D

Dec 31 14:08:02 domeee systemd[1]: Created slice User Slice of UID 115.

Dec 31 14:08:02 domeee systemd[1]: Created slice system-user\x2druntime\x2ddir.slice.

Dec 31 14:08:02 domeee systemd[1]: Started /run/user/115 mount wrapper.

Dec 31 14:08:02 domeee systemd[1]: Starting User Manager for UID 115...

Dec 31 14:08:02 domeee systemd[1]: Started Session c1 of user lightdm.

Dec 31 14:08:02 domeee systemd[565]: Reached target Timers.

Dec 31 14:08:02 domeee systemd[565]: Listening on Sound System.

Dec 31 14:08:02 domeee systemd[565]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).

Dec 31 14:08:02 domeee systemd[565]: Listening on GnuPG network certificate management daemon.

Dec 31 14:08:02 domeee systemd[565]: Listening on GnuPG cryptographic agent and passphrase cache.

Dec 31 14:08:02 domeee systemd[565]: Listening on GnuPG cryptographic agent (ssh-agent emulation).

Dec 31 14:08:02 domeee systemd[565]: Starting D-Bus User Message Bus Socket.

Dec 31 14:08:02 domeee systemd[565]: Reached target Paths.

Dec 31 14:08:02 domeee systemd[565]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).

Dec 31 14:08:02 domeee systemd[565]: Listening on D-Bus User Message Bus Socket.

Dec 31 14:08:02 domeee systemd[565]: Reached target Sockets.

Dec 31 14:08:02 domeee systemd[565]: Reached target Basic System.

Dec 31 14:08:02 domeee systemd[565]: Reached target Default.

Dec 31 14:08:02 domeee systemd[565]: Startup finished in 89ms.

Dec 31 14:08:02 domeee systemd[1]: Started User Manager for UID 115.

Dec 31 14:08:02 domeee systemd[565]: Started D-Bus User Message Bus.

Dec 31 14:08:02 domeee dbus-daemon[579]: [session uid=115 pid=579] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.0' (uid=115 pid=576 comm="/usr/sbin/lightdm-gtk-greeter ")

Dec 31 14:08:02 domeee systemd[565]: Starting Accessibility services bus...

Dec 31 14:08:02 domeee dbus-daemon[579]: [session uid=115 pid=579] Successfully activated service 'org.a11y.Bus'

Dec 31 14:08:02 domeee systemd[565]: Started Accessibility services bus.

Dec 31 14:08:02 domeee at-spi-bus-launcher[580]: dbus-daemon[585]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=115 pid=576 comm="/usr/sbin/lightdm-gtk-greeter ")

Dec 31 14:08:02 domeee at-spi-bus-launcher[580]: dbus-daemon[585]: Successfully activated service 'org.a11y.atspi.Registry'

Dec 31 14:08:02 domeee at-spi-bus-launcher[580]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

Dec 31 14:08:02 domeee dbus-daemon[579]: [session uid=115 pid=579] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=115 pid=576 comm="/usr/sbin/lightdm-gtk-greeter ")

Dec 31 14:08:02 domeee systemd[565]: Starting Virtual filesystem service...

Dec 31 14:08:02 domeee dbus-daemon[579]: [session uid=115 pid=579] Successfully activated service 'org.gtk.vfs.Daemon'

Dec 31 14:08:02 domeee systemd[565]: Started Virtual filesystem service.

Dec 31 14:08:02 domeee ModemManager[428]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0': not supported by any plugin

Dec 31 14:08:02 domeee ModemManager[428]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.2': not supported by any plugin

Dec 31 14:08:13 domeee kernel: [   18.165616] random: crng init done

Dec 31 14:08:13 domeee kernel: [   18.165623] random: 7 urandom warning(s) missed due to ratelimiting

Dec 31 14:08:13 domeee NetworkManager[408]: <info>  [1546261693.2660] sup-iface[0x5577013e30b0,wlp2s0]: supports 5 scan SSIDs

Dec 31 14:08:13 domeee NetworkManager[408]: <info>  [1546261693.2680] device (wlp2s0): supplicant interface state: starting -> ready

Dec 31 14:08:13 domeee NetworkManager[408]: <info>  [1546261693.2681] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')

Dec 31 14:08:13 domeee kernel: [   18.182880] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

Dec 31 14:08:13 domeee NetworkManager[408]: <info>  [1546261693.7459] manager: startup complete

Dec 31 14:08:21 domeee systemd[1]: session-c1.scope: Killing process 561 (lightdm) with signal SIGTERM.

Dec 31 14:08:21 domeee systemd[1]: session-c1.scope: Killing process 576 (lightdm-gtk-gre) with signal SIGTERM.

Dec 31 14:08:21 domeee systemd[1]: Stopping Session c1 of user lightdm.

Dec 31 14:08:21 domeee systemd[1]: Stopped Session c1 of user lightdm.

Dec 31 14:08:21 domeee systemd[1]: user-runtime-dir@115.service: Unit not needed anymore. Stopping.

Dec 31 14:08:21 domeee systemd[1]: Stopping User Manager for UID 115...

Dec 31 14:08:21 domeee gvfsd[591]: A connection to the bus can't be made

Dec 31 14:08:22 domeee systemd[565]: Stopping D-Bus User Message Bus...

Dec 31 14:08:22 domeee systemd[565]: Stopping Virtual filesystem service...

Dec 31 14:08:22 domeee systemd[565]: Stopped target Default.

Dec 31 14:08:22 domeee systemd[565]: Stopping Accessibility services bus...

Dec 31 14:08:22 domeee systemd[565]: Stopped Virtual filesystem service.

Dec 31 14:08:22 domeee systemd[565]: Stopped D-Bus User Message Bus.

Dec 31 14:08:22 domeee systemd[565]: Stopped Accessibility services bus.

Dec 31 14:08:22 domeee systemd[565]: Stopped target Basic System.

Dec 31 14:08:22 domeee systemd[565]: Stopped target Sockets.

Dec 31 14:08:22 domeee systemd[565]: Closed GnuPG cryptographic agent and passphrase cache (restricted).

Dec 31 14:08:22 domeee systemd[565]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).

Dec 31 14:08:22 domeee systemd[565]: Closed GnuPG cryptographic agent (ssh-agent emulation).

Dec 31 14:08:22 domeee systemd[565]: Closed Sound System.

Dec 31 14:08:22 domeee systemd[565]: Closed GnuPG cryptographic agent and passphrase cache.

Dec 31 14:08:22 domeee systemd[565]: Closed GnuPG network certificate management daemon.

Dec 31 14:08:22 domeee systemd[565]: Stopped target Timers.

Dec 31 14:08:22 domeee systemd[565]: Stopped target Paths.

Dec 31 14:08:22 domeee systemd[565]: Closed D-Bus User Message Bus Socket.

Dec 31 14:08:22 domeee systemd[565]: Reached target Shutdown.

Dec 31 14:08:22 domeee systemd[565]: Starting Exit the Session...

Dec 31 14:08:22 domeee systemd[1]: Started /run/user/0 mount wrapper.

Dec 31 14:08:22 domeee systemd[1]: Created slice User Slice of UID 0.

Dec 31 14:08:22 domeee systemd[1]: Starting User Manager for UID 0...

Dec 31 14:08:22 domeee systemd[1]: Stopped User Manager for UID 115.

Dec 31 14:08:22 domeee systemd[1]: user-runtime-dir@115.service: Unit not needed anymore. Stopping.

Dec 31 14:08:22 domeee systemd[1]: Removed slice User Slice of UID 115.

Dec 31 14:08:22 domeee systemd[1]: Stopping /run/user/115 mount wrapper...

Dec 31 14:08:22 domeee systemd[1]: Started Session 2 of user root.

Dec 31 14:08:22 domeee systemd[1]: Stopped /run/user/115 mount wrapper.

Dec 31 14:08:22 domeee systemd[618]: Listening on GnuPG cryptographic agent and passphrase cache.

Dec 31 14:08:22 domeee systemd[618]: Reached target Paths.

Dec 31 14:08:22 domeee systemd[618]: Reached target Timers.

Dec 31 14:08:22 domeee systemd[618]: Listening on GnuPG network certificate management daemon.

Dec 31 14:08:22 domeee systemd[618]: Starting D-Bus User Message Bus Socket.

Dec 31 14:08:22 domeee systemd[618]: Listening on GnuPG cryptographic agent (ssh-agent emulation).

Dec 31 14:08:22 domeee systemd[618]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).

Dec 31 14:08:22 domeee systemd[618]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).

Dec 31 14:08:22 domeee systemd[618]: Listening on D-Bus User Message Bus Socket.

Dec 31 14:08:22 domeee systemd[618]: Reached target Sockets.

Dec 31 14:08:22 domeee systemd[618]: Reached target Basic System.

Dec 31 14:08:22 domeee systemd[618]: Reached target Default.

Dec 31 14:08:22 domeee systemd[618]: Startup finished in 67ms.

Dec 31 14:08:22 domeee systemd[1]: Started User Manager for UID 0.

Dec 31 14:08:22 domeee systemd[618]: Started D-Bus User Message Bus.

Dec 31 14:08:22 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.5' (uid=0 pid=635 comm="x-session-manager ")

Dec 31 14:08:22 domeee systemd[618]: Starting Accessibility services bus...

Dec 31 14:08:22 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.a11y.Bus'

Dec 31 14:08:22 domeee systemd[618]: Started Accessibility services bus.

Dec 31 14:08:22 domeee at-spi-bus-launcher[664]: dbus-daemon[669]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=0 pid=635 comm="x-session-manager ")

Dec 31 14:08:22 domeee at-spi-bus-launcher[664]: dbus-daemon[669]: Successfully activated service 'org.a11y.atspi.Registry'

Dec 31 14:08:22 domeee at-spi-bus-launcher[664]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

Dec 31 14:08:22 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating service name='ca.desrt.dconf' requested by ':1.7' (uid=0 pid=635 comm="x-session-manager ")

Dec 31 14:08:22 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'ca.desrt.dconf'

Dec 31 14:08:22 domeee x-session-manager[635]: WARNING: Unable to find provider '' of required component 'dock'

Dec 31 14:08:22 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.11' (uid=0 pid=684 comm="/usr/bin/mate-settings-daemon ")

Dec 31 14:08:22 domeee systemd[618]: Starting Virtual filesystem service...

Dec 31 14:08:22 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.gtk.vfs.Daemon'

Dec 31 14:08:22 domeee systemd[618]: Started Virtual filesystem service.

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.11' (uid=0 pid=684 comm="/usr/bin/mate-settings-daemon ")

Dec 31 14:08:23 domeee systemd[618]: Starting Virtual filesystem service - disk device monitor...

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'

Dec 31 14:08:23 domeee systemd[618]: Started Virtual filesystem service - disk device monitor.

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.11' (uid=0 pid=684 comm="/usr/bin/mate-settings-daemon ")

Dec 31 14:08:23 domeee systemd[618]: Starting Virtual filesystem service - GNOME Online Accounts monitor...

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'

Dec 31 14:08:23 domeee systemd[618]: Started Virtual filesystem service - GNOME Online Accounts monitor.

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.11' (uid=0 pid=684 comm="/usr/bin/mate-settings-daemon ")

Dec 31 14:08:23 domeee systemd[618]: Starting Virtual filesystem service - Apple File Conduit monitor...

Dec 31 14:08:23 domeee gvfs-afc-volume-monitor[726]: Volume monitor alive

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'

Dec 31 14:08:23 domeee systemd[618]: Started Virtual filesystem service - Apple File Conduit monitor.

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.11' (uid=0 pid=684 comm="/usr/bin/mate-settings-daemon ")

Dec 31 14:08:23 domeee systemd[618]: Starting Virtual filesystem service - digital camera monitor...

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'

Dec 31 14:08:23 domeee systemd[618]: Started Virtual filesystem service - digital camera monitor.

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.11' (uid=0 pid=684 comm="/usr/bin/mate-settings-daemon ")

Dec 31 14:08:23 domeee systemd[618]: Starting Virtual filesystem service - Media Transfer Protocol monitor...

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'

Dec 31 14:08:23 domeee systemd[618]: Started Virtual filesystem service - Media Transfer Protocol monitor.

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating service name='org.mate.panel.applet.WnckletFactory' requested by ':1.15' (uid=0 pid=700 comm="mate-panel ")

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating service name='org.mate.panel.applet.ClockAppletFactory' requested by ':1.15' (uid=0 pid=700 comm="mate-panel ")

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating service name='org.mate.panel.applet.NotificationAreaAppletFactory' requested by ':1.15' (uid=0 pid=700 comm="mate-panel ")

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.mate.panel.applet.NotificationAreaAppletFactory'

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.mate.panel.applet.WnckletFactory'

Dec 31 14:08:23 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.mate.panel.applet.ClockAppletFactory'

Dec 31 14:08:23 domeee dbus-daemon[403]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.33' (uid=0 pid=774 comm="mate-power-manager ")

Dec 31 14:08:23 domeee systemd[1]: Starting Daemon for power management...

Dec 31 14:08:23 domeee dbus-daemon[403]: [system] Activating service name='org.mate.SettingsDaemon.DateTimeMechanism' requested by ':1.34' (uid=0 pid=747 comm="/usr/lib/mate-panel/clock-applet ") (using servicehelper)

Dec 31 14:08:23 domeee dbus-daemon[403]: [system] Successfully activated service 'org.mate.SettingsDaemon.DateTimeMechanism'

Dec 31 14:08:24 domeee NetworkManager[408]: <info>  [1546261704.0100] agent-manager: req[0x55770145de00, :1.37/org.freedesktop.nm-applet/0]: agent registered

Dec 31 14:08:24 domeee dbus-daemon[403]: [system] Successfully activated service 'org.freedesktop.UPower'

Dec 31 14:08:24 domeee systemd[1]: Started Daemon for power management.

Dec 31 14:08:30 domeee dbus-daemon[643]: [session uid=0 pid=643] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.33' (uid=0 pid=832 comm="caja --no-desktop --browser ")

Dec 31 14:08:30 domeee systemd[618]: Starting Virtual filesystem metadata service...

Dec 31 14:08:30 domeee dbus-daemon[643]: [session uid=0 pid=643] Successfully activated service 'org.gtk.vfs.Metadata'

Dec 31 14:08:30 domeee systemd[618]: Started Virtual filesystem metadata service.

Dec 31 14:09:24 domeee systemd[1]: Stopping Session 2 of user root.

Dec 31 14:09:24 domeee systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.

Dec 31 14:09:24 domeee systemd[1]: Stopped target Sound Card.

Dec 31 14:09:24 domeee systemd[1]: Stopped target Timers.

Dec 31 14:09:24 domeee systemd[1]: Stopped Trigger anacron every hour.

Dec 31 14:09:24 domeee systemd[1]: Stopped Daily rotation of log files.

Dec 31 14:09:24 domeee systemd[1]: Stopping Authorization Manager...

Dec 31 14:09:24 domeee systemd[618]: Stopping Virtual filesystem service - Apple File Conduit monitor...

Dec 31 14:09:24 domeee systemd[618]: Stopped target Default.

Dec 31 14:09:24 domeee systemd[618]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...

Dec 31 14:09:24 domeee systemd[618]: Stopping Virtual filesystem service - disk device monitor...

Dec 31 14:09:24 domeee systemd[618]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...

Dec 31 14:09:24 domeee systemd[618]: Stopping Virtual filesystem service - digital camera monitor...

Dec 31 14:09:24 domeee systemd[618]: Stopping D-Bus User Message Bus...

Dec 31 14:09:24 domeee systemd[618]: Stopping Virtual filesystem metadata service...

Dec 31 14:09:24 domeee systemd[618]: Stopping Virtual filesystem service...

Dec 31 14:09:24 domeee systemd[618]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.

Dec 31 14:09:24 domeee systemd[618]: Stopped Virtual filesystem service - digital camera monitor.

Dec 31 14:09:24 domeee systemd[618]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.

Dec 31 14:09:24 domeee systemd[618]: Stopped Virtual filesystem metadata service.

Dec 31 14:09:24 domeee systemd[1]: user-runtime-dir@0.service: Unit not needed anymore. Stopping.

Dec 31 14:09:24 domeee systemd[1]: Stopping User Manager for UID 0...

Dec 31 14:09:24 domeee systemd[1]: Stopping Daemon for power management...

Dec 31 14:09:24 domeee systemd[1]: Stopped target Graphical Interface.

Dec 31 14:09:24 domeee ModemManager[428]: <info>  Caught signal, shutting down...

Dec 31 14:09:24 domeee systemd[1]: Stopping Accounts Service...

Dec 31 14:09:24 domeee systemd[1]: Stopped target Multi-User System.

Dec 31 14:09:24 domeee NetworkManager[408]: <info>  [1546261764.0792] modem-manager: ModemManager no longer available

Dec 31 14:09:24 domeee ModemManager[428]: <info>  ModemManager is shut down

Dec 31 14:09:24 domeee systemd[1]: Stopping Modem Manager...

Dec 31 14:09:24 domeee systemd[1]: Stopping Make remote CUPS printers available locally...

Dec 31 14:09:24 domeee systemd[1]: Stopped target Login Prompts.

Dec 31 14:10:04 domeee kernel: [    0.000000] Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22)

Dec 31 14:10:04 domeee kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-1-amd64 root=UUID=536c2b1f-d5b8-4ef5-a463-09da7c3dc3d6 ro quiet

Dec 31 14:10:04 domeee kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'

Dec 31 14:10:04 domeee kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'

Dec 31 14:10:04 domeee kernel: [    0.000000] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-provided physical RAM map:

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000040005000-0x0000000078ae1fff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000078ae2000-0x0000000078df4fff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000078df5000-0x0000000078e7efff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000078e7f000-0x0000000078f19fff] ACPI NVS

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000078f1a000-0x0000000079507fff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000079508000-0x0000000079508fff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000079509000-0x000000007954bfff] ACPI NVS

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x000000007954c000-0x0000000079c41fff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000079c42000-0x0000000079ff2fff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000079ff3000-0x0000000079ffffff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x000000007a800000-0x000000007e9fffff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved

Dec 31 14:10:04 domeee kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001005fffff] usable

Dec 31 14:10:04 domeee kernel: [    0.000000] NX (Execute Disable) protection: active

Dec 31 14:10:04 domeee kernel: [    0.000000] SMBIOS 2.7 present.

Dec 31 14:10:04 domeee kernel: [    0.000000] DMI: Notebook                        W310CZ/CZ-T      /W310CZ          , BIOS 4.6.5 12/24/2013

Dec 31 14:10:04 domeee kernel: [    0.000000] tsc: Fast TSC calibration using PIT

Dec 31 14:10:04 domeee kernel: [    0.000000] tsc: Detected 1795.924 MHz processor

Dec 31 14:10:04 domeee kernel: [    0.003506] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved

Dec 31 14:10:04 domeee kernel: [    0.003509] e820: remove [mem 0x000a0000-0x000fffff] usable

Dec 31 14:10:04 domeee kernel: [    0.003521] last_pfn = 0x100600 max_arch_pfn = 0x400000000

Dec 31 14:10:04 domeee kernel: [    0.003527] MTRR default type: uncachable

Dec 31 14:10:04 domeee kernel: [    0.003528] MTRR fixed ranges enabled:

Dec 31 14:10:04 domeee kernel: [    0.003530]   00000-9FFFF write-back

Dec 31 14:10:04 domeee kernel: [    0.003531]   A0000-BFFFF uncachable

Dec 31 14:10:04 domeee kernel: [    0.003532]   C0000-D3FFF write-protect

Dec 31 14:10:04 domeee kernel: [    0.003533]   D4000-E7FFF uncachable

Dec 31 14:10:04 domeee kernel: [    0.003534]   E8000-FFFFF write-protect

Dec 31 14:10:04 domeee kernel: [    0.003535] MTRR variable ranges enabled:

Dec 31 14:10:04 domeee kernel: [    0.003536]   0 base 000000000 mask F00000000 write-back

Dec 31 14:10:04 domeee kernel: [    0.003538]   1 base 100000000 mask FFFC00000 write-back

Dec 31 14:10:04 domeee kernel: [    0.003539]   2 base 100400000 mask FFFE00000 write-back

Dec 31 14:10:04 domeee kernel: [    0.003540]   3 base 080000000 mask F80000000 uncachable

Dec 31 14:10:04 domeee kernel: [    0.003541]   4 base 07C000000 mask FFC000000 uncachable

Dec 31 14:10:04 domeee kernel: [    0.003542]   5 base 07B000000 mask FFF000000 uncachable

Dec 31 14:10:04 domeee kernel: [    0.003543]   6 base 07A800000 mask FFF800000 uncachable

Dec 31 14:10:04 domeee kernel: [    0.003544]   7 disabled

Dec 31 14:10:04 domeee kernel: [    0.003545]   8 disabled

Dec 31 14:10:04 domeee kernel: [    0.003545]   9 disabled

Dec 31 14:10:04 domeee kernel: [    0.004273] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  

Dec 31 14:10:04 domeee kernel: [    0.004409] e820: update [mem 0x7a800000-0xffffffff] usable ==> reserved

Dec 31 14:10:04 domeee kernel: [    0.004415] last_pfn = 0x7a000 max_arch_pfn = 0x400000000

Dec 31 14:10:04 domeee kernel: [    0.018927] found SMP MP-table at [mem 0x000fd780-0x000fd78f] mapped at [(____ptrval____)]

Dec 31 14:10:04 domeee kernel: [    0.038537] Base memory trampoline at [(____ptrval____)] 97000 size 24576

Dec 31 14:10:04 domeee kernel: [    0.038542] BRK [0x52801000, 0x52801fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.038545] BRK [0x52802000, 0x52802fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.038546] BRK [0x52803000, 0x52803fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.038633] BRK [0x52804000, 0x52804fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.038636] BRK [0x52805000, 0x52805fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.038893] BRK [0x52806000, 0x52806fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.038969] BRK [0x52807000, 0x52807fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.039080] BRK [0x52808000, 0x52808fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.039082] BRK [0x52809000, 0x52809fff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.039204] BRK [0x5280a000, 0x5280afff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.039432] BRK [0x5280b000, 0x5280bfff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.039561] BRK [0x5280c000, 0x5280cfff] PGTABLE

Dec 31 14:10:04 domeee kernel: [    0.040141] RAMDISK: [mem 0x352df000-0x36966fff]

Dec 31 14:10:04 domeee kernel: [    0.040149] ACPI: Early table checksum verification disabled

Dec 31 14:10:04 domeee kernel: [    0.055921] ACPI: RSDP 0x00000000000F0490 000024 (v02 Intel )

Dec 31 14:10:04 domeee kernel: [    0.055925] ACPI: XSDT 0x0000000078F0A078 00006C (v01 Intel  CHIEF    01072009 AMI  00010013)

Dec 31 14:10:04 domeee kernel: [    0.055932] ACPI: FACP 0x0000000078F13F30 00010C (v05 Intel  CHIEF    01072009 AMI  00010013)

Dec 31 14:10:04 domeee kernel: [    0.055940] ACPI: DSDT 0x0000000078F0A178 009DB7 (v02 Intel  CHIEF    00000023 INTL 20051117)

Dec 31 14:10:04 domeee kernel: [    0.055944] ACPI: FACS 0x0000000078F18080 000040

Dec 31 14:10:04 domeee kernel: [    0.055948] ACPI: APIC 0x0000000078F14040 000062 (v03 Intel  CHIEF    01072009 AMI  00010013)

Dec 31 14:10:04 domeee kernel: [    0.055952] ACPI: FPDT 0x0000000078F140A8 000044 (v01 Intel  CHIEF    01072009 AMI  00010013)

Dec 31 14:10:04 domeee kernel: [    0.055956] ACPI: MCFG 0x0000000078F140F0 00003C (v01 Intel  CHIEF    01072009 MSFT 00000097)

Dec 31 14:10:04 domeee kernel: [    0.055960] ACPI: SSDT 0x0000000078F14130 000F92 (v01 TrmRef PtidDevc 00001000 INTL 20091112)

Dec 31 14:10:04 domeee kernel: [    0.055964] ACPI: HPET 0x0000000078F150C8 000038 (v01 Intel  CHIEF    01072009 AMI. 00000005)

Dec 31 14:10:04 domeee kernel: [    0.055968] ACPI: SSDT 0x0000000078F15100 000315 (v01 SataRe SataTabl 00001000 INTL 20091112)

Dec 31 14:10:04 domeee kernel: [    0.055973] ACPI: SSDT 0x0000000078F15418 000860 (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)

Dec 31 14:10:04 domeee kernel: [    0.055977] ACPI: SSDT 0x0000000078F15C78 000B22 (v01 PmRef  CpuPm    00003000 INTL 20051117)

sinon, on ne va pas se prendre trop le chou avec ça (sauf si y'a bug pas répertorié à corriger), ça devrait évoluer rapidement (le freeze est pour bientôt d'après ce que j'ai lu ?)

Antidentity · 12-01-2019 11:29:14

Ça a tout l'air d'un bug effectivement. Je n'utilise pas mate mais openbox, mais comme je suis en mono-utilisateur, je n'utilise pas de gestionnaire de connexion. Il y a toujours la possibilité d'utiliser systemd. Si tu es en mono-utilisateur et que tu veux te passer de lightdm, tu peux toujours le supprimer et suivre les indications ici:
https://debian-facile.org/viewtopic.php … 33#p236933

Debeee · 01-04-2019 12:54:05

Bonjour tout le monde,
je redéterre mon topic, j'ai eu plein d'embrouilles avec l'installation de la debian 10 testing.
Précédemment (voir posts ci-dessus), j'avais installé cette distro sur un portable LDLC (clevo w310cz en fait) : j'ai eu les galères de temps mort au boot.
J'ai voulu installer cette distro (plusieurs fois…) sur un eeepc 1011PX (intel atom n570, 2Go de RAM).
En premier, avec le HD d'origine : ça marchait bien, je n'avais pas la galère du clevo, boot en 55s environ (session à ouverture automatique, delai du Grub à 1s).
A partir de cet ordi, j'ai installé cette distro sur un SSD en externe avec une clé usb : aucun souci, boot (conditions idem précédemment) en 46s nickel.
Pb : quand j'ai voulu redémarrer le système interne du HD, 3mn de boot avec notamment une tâche sur un disque (nommé par son UUID) qui durait 1'30…
Perdu pour perdu, j'ai opéré mon ordi et mis le SSD (distro installée en externe donc) dans la machine : pareil qu'avec le HD, boot en 3mn avec des tâches bizarres.

Alors, j'ai trouvé des solutions et il me reste un problème.
1/ les solutions
a/ Tout d'abord, la tâche d'1'30 venait en fait du fstab : il y avait 2 swap de déclarés dedans, dont celui du disque interne de la machine quand j'ai installé la distro sur le disque externe. La machine recherchait désespérément ce swap pendant 1'30 (délai de time out je suppose) puis continuait le boot.
En nettoyant le fstab, j'ai éliminé ce délai.
b/ Ensuite, entre le chargement de l'image système et l'apparition du message me disant sdb2 clean (mon disque système), j'avais encore 30s de temps mort par rapport à un boot normal, avec le message "gave up waiting for suspend/resume device"
Explication de Pascal (merci à lui) ici : https://www.debian-fr.xyz/viewtopic.php?t=1095
J'ai appliqué et gratté mes 30s.

Reste le problème posé au début de ce fil : si je mets en login auto, ça part en vrille à la fin du boot.
Et j'ai découvert qu'en faisant la combinaison ctrl+C après le message sdb2 clean, ben je boot en 40s, sinon, écran noir pendant perpette. J'ai essayé la touche "entrée", ça ne marche pas. Je suppose qu'avec ctrl+C je tue une tâche parasite, mais laquelle ???

Infos supplémentaire : j'ai lu attentivement ce fil : http://debian-facile.org/viewtopic.php?id=22789 et passé les bonnes commandes : dans tous les cas de boot décrits ci-dessus que j'ai eus, aucune info sur mon temps d'attente, j'ai eu un truc du style temps total boot + bureau = 40s (le vrai temps de boot en fait) alors que j'avais poireauté 3mn…

Voilà, je ne sais donc toujours pas si c'est un bug de la debian 10 ou autre chose… Sachant que j'ai 2 machines différentes impactées de la même manière
Si quelqu'un a une idée, je prends !

Debeee · 15-04-2019 13:09:31

Bonjour à tout le monde,
ce matin, j'ai mis à jour le Clevo (pas fait de mise à jour depuis janvier, ça marchait à peu près, donc pas de risques...) et aussi l'eeepc.
Ben en fait ça y'est, le Clevo marche tout nickel, il boote en 25s en autologin sans aucun souci.
Y'avait bien une embrouille au niveau du système, les MAJ ont réglé le pb.
Par contre, avec l'eeepc 1011, y'a du progrès : plus besoin de faire un ctrl+C après le message disk clean (qui me mettait le souk une fois sur 2 d'ailleurs : pas de pad après démarrage, gênant...), juste en touchant le pad après le message disk clean ça marche. Sinon, ça reste écran noir...
Du progrès donc, mais il en manque...
A noter : le Clevo marche maintenant tout nickel, mais l'eeepc n'a toujours pas de gestion d'énergie ni de wifi, ni de son (enfin, les enceintes, la sortie casque marche) : ça doit être un hard assez spécifique à gérer et il est mal géré

(

Debeee · 22-09-2019 19:11:53

Bonjour tout le monde,
buster est passé en stable, mon clevo marche bien, RAS.
Par contre, pour l'eeepc, ça reste pareil : il faut toucher le pad à un moment précis du boot pour ne pas rester ad vitam sur un écran noir.
Pour info, à un moment des mises à jour, le boot était devenu très verbeux, j'ai donc viré plymouth radicalement, merci à anonyme (post #17) : https://debian-facile.org/viewtopic.php … 72#p306172
La mise à jour en stable, puis la 10.1 n'ont rien changé (ni non plus sur mes pb de gestion d'énergie et wifi, voir ici : https://debian-facile.org/viewtopic.php?id=24047) => j'ai à nouveau upgradé en testing. Le wifi et la gestion d'énergie marchent bien maintenant, mais le boot reste toujours pareil : si on ne touche pas le pad, on a un écran noir.
Je vis avec, mais si quelqu'un a le même problème et une solution, je ne dis pas non !

Debeee · 26-12-2019 15:14:03

Joyeuses fêtes à tou(te)s !

Fin de ma saga avec l'eeepc 1011px, très déconnant avec les Debian 9 et 10, et donc passé en testing à partir d'une version 10 avec succès pour deux problèmes majeurs (wifi, gestion de l'énergie), mais boot encore perfectible.
Pour résumer, le boot restait dans les choux si on ne touchait pas le pad vers la fin de la procédure.
J'ai fait une MAJ un peu avant noël, le noyau est passé en 5.3, et j'ai vu passer dans les commentaires entre autres des MAJ de Lightdm et systemd. Je ne sais pas si c'était un de ces deux composants qui mettait le binz, toujours est-il que maintenant, mon ordi boote sans aucune intervention extérieure.

Il est donc (presque) parfaitement fonctionnel !
Je clôture donc ce fil (résolu), ça fera plaisir à melissa6969 d'avoir la chute de l'histoire si elle passe par là

Dernière modification par Debeee (26-12-2019 15:15:31)

Debian-facile

#1 30-12-2018 16:58:40

[Résolu] auto login avec Debian 10 Mate

#2 31-12-2018 00:26:09

Re : [Résolu] auto login avec Debian 10 Mate

#3 31-12-2018 05:46:26

Re : [Résolu] auto login avec Debian 10 Mate

#4 31-12-2018 14:36:14

Re : [Résolu] auto login avec Debian 10 Mate

#5 31-12-2018 15:09:21

Re : [Résolu] auto login avec Debian 10 Mate

#6 31-12-2018 15:48:04

Re : [Résolu] auto login avec Debian 10 Mate

#7 12-01-2019 11:29:14

Re : [Résolu] auto login avec Debian 10 Mate

#8 01-04-2019 12:54:05

Re : [Résolu] auto login avec Debian 10 Mate

#9 15-04-2019 13:09:31

Re : [Résolu] auto login avec Debian 10 Mate

#10 22-09-2019 19:11:53

Re : [Résolu] auto login avec Debian 10 Mate

#11 26-12-2019 15:14:03

Re : [Résolu] auto login avec Debian 10 Mate

Pied de page des forums