[SOLVED - complete reinstall!]No GUI post Update (22/07/17)

johnh009 · July 23, 2017, 06:42:22 PM

Mate desktop, 64 bit.

Attempting to boot after the above update (upgrade-system), the system boots to a text (command) screen. Trying to start lightdm doesn't work, but it is installed. Have done todays update (upgrade-system) in the hope that it may have fixed the bug, but it has not. The following may give a clue (output from the command: systemctl status lightdm service)

Code Select


$ systemctl status lightdm service
Unit service.service could not be found
  lightdm.service - Light Display manager
   Loaded: loaded (/lib/systemd/system/lightdm.service: enabled: vendor: vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-07-23 17:17:00 CEST: 11min ago
     Docs: man:lightdm(1)
 Main PID: 1351 (code-exited, stats=1/FAILURE)

Jul 23 17:17:00 sparky systemd[1]: lightdm.service: Triggering OmFailure=  dependencies.
Jul 23 17:17:00 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 23 17:17:00 sparky systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 23 17:17:00 sparky systemd[1]: Stopped Light Display Manager.
Jul 23 17:17:00 sparky systemd[1]: lightdm.service: Start request repeated too quickly.
Jul 23 17:17:00 sparky systemd[1]: Failed to start Light Display Manager.
Jul 23 17:17:00 sparky systemd[1]: lightdm.service: Unit enetered failed state.
Jul 23 17:17:00 sparky systemd[1]: lightdm.service: Triggering OmFailure=  dependencies.
Jul 23 17:17:00 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
$

Any tips/hints/ suggestions gratefully received.

pavroo · July 24, 2017, 11:07:58 PM

Are you sure your last upgrade went well, with no issues?
If not, run: sudo dpkg --configure -a

johnh009 · July 25, 2017, 06:03:18 PM

Yes, the last update went OK as have the subsequent two. I ran the command you suggested - nothing appeared to happen, i.e. no text output was produced, and just the command line was returned.

pavroo · July 25, 2017, 09:01:25 PM

QuoteTrying to start lightdm doesn't work

Did you try to load the lightdm service manually?

Code Select

sudo systemctl enable lightdm
sudo systemctl start lightdm

and what about a log?

Code Select

sudo cat /var/log/lightdm/x-0-greeter.log

johnh009 · July 27, 2017, 09:39:27 PM

systemctl enable lightdm produces:

Code Select


Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable lightdm
The unit files have no installation config (WantedBy, RquiredByAlso, Alias
settings in the [install] section, and DefaultInstance for template units).
This means they are not to be anabled usingn systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being systemlinked from another unit's
   .wants/ or .requires directory.
2) A unit's purpose may be to act as a helper for some other which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

journalctl -xe produces the following (from where 'lightdm' first appears to the end):

Code Select


-- 
-- The start-up result is done.
Jul 26 19:17:05 sparky systemd[1]: Starting Light Display Manager...
-- Subject: Unit lightdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has begun starting up.
Jul 26 19:17:05 sparky acpi-support[590]: Enabling power management...done.
Jul 26 19:17:05 sparky systemd[1]: Started LSB: Start some power management scripts.
-- Subject: Unit acpi-support.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit acpi-support.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:05 sparky NetworkManager[530]: <info>  [1501089425.3258] keyfile: new connection /etc/NetworkManager/system-connections/Jetnet_John 2 (cb9da3aa-1391-4dc0-b62b-bb5ac068e508,"Jetnet_John 2")
Jul 26 19:17:05 sparky NetworkManager[530]: <info>  [1501089425.5034] keyfile: new connection /etc/NetworkManager/system-connections/Jetnet_John 1 (460417f6-9ec8-496a-97da-40c76d9231fe,"Jetnet_John 1")
Jul 26 19:17:05 sparky colord[537]: failed to get session [pid 511]: No data available
Jul 26 19:17:05 sparky NetworkManager[530]: <info>  [1501089425.5639] keyfile: new connection /etc/NetworkManager/system-connections/Jetnet_John (d51664c8-0635-49c3-9397-95b4e7f26a29,"Jetnet_John")
Jul 26 19:17:05 sparky ntpd[562]: ntpd 4.2.8p10@1.3728-o (1): Starting
Jul 26 19:17:05 sparky ntpd[562]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 119:130
Jul 26 19:17:05 sparky systemd[1]: Started Network Time Service.
-- Subject: Unit ntp.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit ntp.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:05 sparky systemd[1]: Received SIGRTMIN+21 from PID 426 (plymouthd).
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 26 19:17:05 sparky systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 19:17:05 sparky colord[537]: failed to get session [pid 511]: No data available
Jul 26 19:17:05 sparky ntpd[613]: proto: precision = 0.098 usec (-23)
Jul 26 19:17:05 sparky ntpd[613]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
Jul 26 19:17:05 sparky ntpd[613]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2017-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Jul 26 19:17:05 sparky ntpd[613]: Listen and drop on 0 v6wildcard [::]:123
Jul 26 19:17:05 sparky ntpd[613]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jul 26 19:17:05 sparky ntpd[613]: Listen normally on 2 lo 127.0.0.1:123
Jul 26 19:17:05 sparky ntpd[613]: Listen normally on 3 lo [::1]:123
Jul 26 19:17:05 sparky ntpd[613]: Listening on routing socket on fd #20 for interface updates
Jul 26 19:17:05 sparky NetworkManager[530]: <info>  [1501089425.7820] get unmanaged devices count: 0
Jul 26 19:17:05 sparky dbus[516]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 26 19:17:05 sparky systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Failed to schedule restart job: Transaction is destructive.
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 19:17:05 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 19:17:05 sparky systemd[1]: Starting Hostname Service...
-- Subject: Unit systemd-hostnamed.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-hostnamed.service has begun starting up.
Jul 26 19:17:05 sparky dbus[516]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jul 26 19:17:05 sparky systemd[1]: Started Hostname Service.
-- Subject: Unit systemd-hostnamed.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-hostnamed.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:05 sparky NetworkManager[530]: <info>  [1501089425.9946] settings: hostname: using hostnamed
Jul 26 19:17:05 sparky NetworkManager[530]: <info>  [1501089425.9947] settings: hostname changed from (none) to "sparky"
Jul 26 19:17:05 sparky nm-dispatcher[569]: req:1 'hostname': new request (2 scripts)
Jul 26 19:17:05 sparky nm-dispatcher[569]: req:1 'hostname': start running ordered scripts...
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.0656] dhcp-init: Using DHCP client 'dhclient'
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.0657] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.0657] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.0658] manager: Networking is enabled by state file
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1613] Loaded device plugin: NMBondDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1614] Loaded device plugin: NMBridgeDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1614] Loaded device plugin: NMDummyDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1615] Loaded device plugin: NMEthernetDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1615] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1615] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1616] Loaded device plugin: NMMacsecDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1616] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1623] Loaded device plugin: NMTunDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1623] Loaded device plugin: NMVethDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1623] Loaded device plugin: NMVlanDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.1624] Loaded device plugin: NMVxlanDeviceFactory (internal)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.2023] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-team.so)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.2031] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.2305] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3405] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3575] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3769] device (lo): link connected
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3778] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3793] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3804] keyfile: add connection in-memory (4ec72e48-3749-3fea-997d-3213befc5194,"Wired connection 1")
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3811] settings: (eth0): created default wired connection 'Wired connection 1'
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.3822] device (eth0): state change: unmanaged -> unavailable (reason 'managed', internal state 'external')
Jul 26 19:17:06 sparky kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 26 19:17:06 sparky kernel: r8169 0000:04:00.0: firmware: direct-loading firmware rtl_nic/rtl8168e-3.fw
Jul 26 19:17:06 sparky kernel: r8169 0000:04:00.0 eth0: link down
Jul 26 19:17:06 sparky kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.5401] wifi-nl80211: (wlan0): using nl80211 for WiFi device control
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.5403] device (wlan0): driver supports Access Point (AP) mode
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.5411] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.5418] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', internal state 'external')
Jul 26 19:17:06 sparky kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 26 19:17:06 sparky ntpd[613]: error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
Jul 26 19:17:06 sparky kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 26 19:17:06 sparky NetworkManager[530]: <info>  [1501089426.7330] device (wlan0): set-hw-addr: set MAC address to 92:5F:CD:D2:B6:1B (scanning)
Jul 26 19:17:06 sparky kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 26 19:17:06 sparky loadcpufreq[589]: Loading cpufreq kernel modules...done (acpi-cpufreq).
Jul 26 19:17:06 sparky systemd[1]: Started LSB: Load kernel modules needed to enable cpufreq scaling.
-- Subject: Unit loadcpufreq.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit loadcpufreq.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:06 sparky systemd[1]: Starting LSB: set CPUFreq kernel parameters...
-- Subject: Unit cpufrequtils.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit cpufrequtils.service has begun starting up.
Jul 26 19:17:06 sparky cpufrequtils[676]: CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...done.
Jul 26 19:17:06 sparky systemd[1]: Started LSB: set CPUFreq kernel parameters.
-- Subject: Unit cpufrequtils.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit cpufrequtils.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:07 sparky dbus[516]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jul 26 19:17:07 sparky NetworkManager[530]: <info>  [1501089427.0988] ModemManager available in the bus
Jul 26 19:17:07 sparky freshclam[508]: ClamAV update process started at Wed Jul 26 19:17:07 2017
Jul 26 19:17:07 sparky freshclam[508]: WARNING: Can't query current.cvd.clamav.net
Jul 26 19:17:07 sparky freshclam[508]: WARNING: Invalid DNS reply. Falling back to HTTP mode.
Jul 26 19:17:07 sparky ModemManager[509]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.5/0000:04:00.0': not supported by any plugin
Jul 26 19:17:07 sparky ModemManager[509]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5': not supported by any plugin
Jul 26 19:17:07 sparky freshclam[508]: Reading CVD header (main.cvd): WARNING: Can't get information about db.local.clamav.net: Name or service not known
Jul 26 19:17:07 sparky freshclam[508]: WARNING: Can't read main.cvd header from db.local.clamav.net (IP: )
Jul 26 19:17:07 sparky systemd[1]: Starting WPA supplicant...
-- Subject: Unit wpa_supplicant.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit wpa_supplicant.service has begun starting up.
Jul 26 19:17:07 sparky freshclam[508]: Trying again in 5 secs...
Jul 26 19:17:07 sparky ntpd[613]: error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
Jul 26 19:17:07 sparky dbus[516]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Jul 26 19:17:07 sparky systemd[1]: Started WPA supplicant.
-- Subject: Unit wpa_supplicant.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit wpa_supplicant.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:07 sparky wpa_supplicant[685]: Successfully initialized wpa_supplicant
Jul 26 19:17:07 sparky NetworkManager[530]: <info>  [1501089427.7247] supplicant: wpa_supplicant running
Jul 26 19:17:07 sparky NetworkManager[530]: <info>  [1501089427.7248] device (wlan0): supplicant interface state: init -> starting
Jul 26 19:17:07 sparky NetworkManager[530]: <info>  [1501089427.8716] sup-iface[0x5637741d3180,wlan0]: supports 4 scan SSIDs
Jul 26 19:17:07 sparky NetworkManager[530]: <info>  [1501089427.8726] device (wlan0): supplicant interface state: starting -> ready
Jul 26 19:17:07 sparky NetworkManager[530]: <info>  [1501089427.8727] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', internal state 'managed')
Jul 26 19:17:07 sparky kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 26 19:17:08 sparky ntpd[613]: error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)
Jul 26 19:17:09 sparky NetworkManager[530]: <info>  [1501089429.0981] device (wlan0): supplicant interface state: ready -> inactive
Jul 26 19:17:09 sparky ntpd[613]: error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.3923] policy: auto-activating connection 'Jetnet_John 8'
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.3933] device (wlan0): Activation: starting connection 'Jetnet_John 8' (ebc6b9d4-1d2c-4fc4-aef6-b741911978a1)
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.3934] device (wlan0): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.3935] manager: NetworkManager state is now CONNECTING
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.4933] device (wlan0): set-hw-addr: reset MAC address to A0:F3:C1:2F:DE:0A (preserve)
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6804] device (wlan0): supplicant interface state: inactive -> disabled
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6806] device (wlan0): state change: prepare -> config (reason 'none', internal state 'managed')
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6808] device (wlan0): Activation: (wifi) access point 'Jetnet_John 8' has security, but secrets are required.
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6808] device (wlan0): state change: config -> need-auth (reason 'none', internal state 'managed')
Jul 26 19:17:10 sparky kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6853] device (wlan0): state change: need-auth -> prepare (reason 'none', internal state 'managed')
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6855] device (wlan0): state change: prepare -> config (reason 'none', internal state 'managed')
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6856] device (wlan0): Activation: (wifi) connection 'Jetnet_John 8' has security, and secrets exist.  No new secrets needed.
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6856] Config: added 'ssid' value 'Jetnet_John'
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6856] Config: added 'scan_ssid' value '1'
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6857] Config: added 'key_mgmt' value 'WPA-PSK'
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6857] Config: added 'auth_alg' value 'OPEN'
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.6858] Config: added 'psk' value '<hidden>'
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.7041] device (wlan0): supplicant interface state: disabled -> inactive
Jul 26 19:17:10 sparky wpa_supplicant[685]: wlan0: SME: Trying to authenticate with 00:21:f2:05:2a:00 (SSID='Jetnet_John' freq=2412 MHz)
Jul 26 19:17:10 sparky kernel: wlan0: authenticate with 00:21:f2:05:2a:00
Jul 26 19:17:10 sparky kernel: wlan0: send auth to 00:21:f2:05:2a:00 (try 1/3)
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.8596] device (wlan0): supplicant interface state: inactive -> authenticating
Jul 26 19:17:10 sparky wpa_supplicant[685]: wlan0: Trying to associate with 00:21:f2:05:2a:00 (SSID='Jetnet_John' freq=2412 MHz)
Jul 26 19:17:10 sparky kernel: wlan0: authenticated
Jul 26 19:17:10 sparky kernel: wlan0: associate with 00:21:f2:05:2a:00 (try 1/3)
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.8670] device (wlan0): supplicant interface state: authenticating -> associating
Jul 26 19:17:10 sparky kernel: wlan0: RX AssocResp from 00:21:f2:05:2a:00 (capab=0x431 status=0 aid=1)
Jul 26 19:17:10 sparky wpa_supplicant[685]: wlan0: Associated with 00:21:f2:05:2a:00
Jul 26 19:17:10 sparky wpa_supplicant[685]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jul 26 19:17:10 sparky kernel: wlan0: associated
Jul 26 19:17:10 sparky kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 26 19:17:10 sparky NetworkManager[530]: <info>  [1501089430.8817] device (wlan0): supplicant interface state: associating -> associated
Jul 26 19:17:11 sparky wpa_supplicant[685]: wlan0: WPA: Key negotiation completed with 00:21:f2:05:2a:00 [PTK=CCMP GTK=TKIP]
Jul 26 19:17:11 sparky wpa_supplicant[685]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:21:f2:05:2a:00 completed [id=0 id_str=]
Jul 26 19:17:11 sparky NetworkManager[530]: <info>  [1501089431.4407] device (wlan0): supplicant interface state: associated -> completed
Jul 26 19:17:11 sparky NetworkManager[530]: <info>  [1501089431.4407] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Jetnet_John'.
Jul 26 19:17:11 sparky NetworkManager[530]: <info>  [1501089431.4407] device (wlan0): state change: config -> ip-config (reason 'none', internal state 'managed')
Jul 26 19:17:11 sparky NetworkManager[530]: <info>  [1501089431.4496] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jul 26 19:17:11 sparky NetworkManager[530]: <info>  [1501089431.7455] dhcp4 (wlan0): dhclient started with pid 700
Jul 26 19:17:12 sparky freshclam[508]: ClamAV update process started at Wed Jul 26 19:17:12 2017
Jul 26 19:17:12 sparky freshclam[508]: WARNING: Can't query current.cvd.clamav.net
Jul 26 19:17:12 sparky freshclam[508]: WARNING: Invalid DNS reply. Falling back to HTTP mode.
Jul 26 19:17:12 sparky freshclam[508]: Reading CVD header (main.cvd): WARNING: Can't get information about db.local.clamav.net: Name or service not known
Jul 26 19:17:12 sparky freshclam[508]: WARNING: Can't read main.cvd header from db.local.clamav.net (IP: )
Jul 26 19:17:12 sparky freshclam[508]: Trying again in 5 secs...
Jul 26 19:17:12 sparky dhclient[700]: DHCPREQUEST of 192.168.1.56 on wlan0 to 255.255.255.255 port 67
Jul 26 19:17:12 sparky dhclient[700]: DHCPACK of 192.168.1.56 from 192.168.1.1
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4719] dhcp4 (wlan0):   address 192.168.1.56
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4719] dhcp4 (wlan0):   plen 24 (255.255.255.0)
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4719] dhcp4 (wlan0):   gateway 192.168.1.1
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4719] dhcp4 (wlan0):   lease time 86400
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4719] dhcp4 (wlan0):   nameserver '8.8.8.8'
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4720] dhcp4 (wlan0):   nameserver '8.8.4.4'
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4720] dhcp4 (wlan0): state changed unknown -> bound
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4730] device (wlan0): state change: ip-config -> ip-check (reason 'none', internal state 'managed')
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4733] device (wlan0): state change: ip-check -> secondaries (reason 'none', internal state 'managed')
Jul 26 19:17:12 sparky avahi-daemon[514]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.56.
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4735] device (wlan0): state change: secondaries -> activated (reason 'none', internal state 'managed')
Jul 26 19:17:12 sparky avahi-daemon[514]: New relevant interface wlan0.IPv4 for mDNS.
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.4736] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 26 19:17:12 sparky avahi-daemon[514]: Registering new address record for 192.168.1.56 on wlan0.IPv4.
Jul 26 19:17:12 sparky dhclient[700]: bound to 192.168.1.56 -- renewal in 39555 seconds.
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.6058] manager: NetworkManager state is now CONNECTED_SITE
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.6059] policy: set 'Jetnet_John 8' (wlan0) as default for IPv4 routing and DNS
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.6064] device (wlan0): Activation: successful, device activated.
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.6072] manager: startup complete
Jul 26 19:17:12 sparky nm-dispatcher[569]: req:2 'up' [wlan0]: new request (2 scripts)
Jul 26 19:17:12 sparky nm-dispatcher[569]: req:2 'up' [wlan0]: start running ordered scripts...
Jul 26 19:17:12 sparky NetworkManager[530]: <info>  [1501089432.6104] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 26 19:17:12 sparky nm-dispatcher[569]: req:3 'connectivity-change': new request (2 scripts)
Jul 26 19:17:12 sparky systemd[1]: Started Network Manager Wait Online.
-- Subject: Unit NetworkManager-wait-online.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit NetworkManager-wait-online.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Reached target Network is Online.
-- Subject: Unit network-online.target has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit network-online.target has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Starting LSB: exim Mail Transport Agent...
-- Subject: Unit exim4.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit exim4.service has begun starting up.
Jul 26 19:17:12 sparky systemd[1]: Starting LSB: Brings up/down network automatically...
-- Subject: Unit ifplugd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit ifplugd.service has begun starting up.
Jul 26 19:17:12 sparky systemd[1]: Starting Automounts filesystems on demand...
-- Subject: Unit autofs.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit autofs.service has begun starting up.
Jul 26 19:17:12 sparky systemd[1]: Starting /etc/rc.local Compatibility...
-- Subject: Unit rc-local.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit rc-local.service has begun starting up.
Jul 26 19:17:12 sparky systemd[1]: Starting keep memory of all UPnP devices that announced themselves...
-- Subject: Unit minissdpd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit minissdpd.service has begun starting up.
Jul 26 19:17:12 sparky systemd[1]: Started Daily apt download activities.
-- Subject: Unit apt-daily.timer has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit apt-daily.timer has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Started Daily apt upgrade and clean activities.
-- Subject: Unit apt-daily-upgrade.timer has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit apt-daily-upgrade.timer has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Reached target Timers.
-- Subject: Unit timers.target has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit timers.target has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Started LSB: Brings up/down network automatically.
-- Subject: Unit ifplugd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit ifplugd.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Started /etc/rc.local Compatibility.
-- Subject: Unit rc-local.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit rc-local.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Starting Hold until boot process finishes up...
-- Subject: Unit plymouth-quit-wait.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit-wait.service has begun starting up.
Jul 26 19:17:12 sparky systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has begun starting up.
Jul 26 19:17:12 sparky systemd[1]: Started Hold until boot process finishes up.
-- Subject: Unit plymouth-quit-wait.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit-wait.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Started Getty on tty1.
-- Subject: Unit getty@tty1.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit getty@tty1.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Reached target Login Prompts.
-- Subject: Unit getty.target has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit getty.target has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:12 sparky systemd[1]: Started keep memory of all UPnP devices that announced themselves.
-- Subject: Unit minissdpd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit minissdpd.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:13 sparky systemd[1]: Started Automounts filesystems on demand.
-- Subject: Unit autofs.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit autofs.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:13 sparky avahi-daemon[514]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::f3d:c123:e762:545a.
Jul 26 19:17:13 sparky avahi-daemon[514]: New relevant interface wlan0.IPv6 for mDNS.
Jul 26 19:17:13 sparky avahi-daemon[514]: Registering new address record for fe80::f3d:c123:e762:545a on wlan0.*.
Jul 26 19:17:13 sparky nm-dispatcher[569]: req:3 'connectivity-change': start running ordered scripts...
Jul 26 19:17:15 sparky ntpd[613]: Listen normally on 4 wlan0 192.168.1.56:123
Jul 26 19:17:15 sparky ntpd[613]: Listen normally on 5 wlan0 [fe80::f3d:c123:e762:545a%3]:123
Jul 26 19:17:15 sparky ntpd[613]: new interface(s) found: waking up resolver
Jul 26 19:17:17 sparky freshclam[508]: ClamAV update process started at Wed Jul 26 19:17:17 2017
Jul 26 19:17:17 sparky freshclam[508]: main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Jul 26 19:17:17 sparky clamd[549]: Limits: Global size limit set to 104857600 bytes.
Jul 26 19:17:17 sparky clamd[549]: Limits: File size limit set to 26214400 bytes.
Jul 26 19:17:17 sparky clamd[549]: Limits: Recursion level limit set to 16.
Jul 26 19:17:17 sparky clamd[549]: Limits: Files limit set to 10000.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxEmbeddedPE limit set to 10485760 bytes.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxHTMLNormalize limit set to 10485760 bytes.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxHTMLNoTags limit set to 2097152 bytes.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxScriptNormalize limit set to 5242880 bytes.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxZipTypeRcg limit set to 1048576 bytes.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxPartitions limit set to 50.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxIconsPE limit set to 100.
Jul 26 19:17:17 sparky clamd[549]: Limits: MaxRecHWP3 limit set to 16.
Jul 26 19:17:17 sparky clamd[549]: Limits: PCREMatchLimit limit set to 10000.
Jul 26 19:17:17 sparky clamd[549]: Limits: PCRERecMatchLimit limit set to 5000.
Jul 26 19:17:17 sparky clamd[549]: Limits: PCREMaxFileSize limit set to 26214400.
Jul 26 19:17:17 sparky clamd[549]: Archive support enabled.
Jul 26 19:17:17 sparky clamd[549]: Algorithmic detection enabled.
Jul 26 19:17:17 sparky clamd[549]: Portable Executable support enabled.
Jul 26 19:17:17 sparky clamd[549]: ELF support enabled.
Jul 26 19:17:17 sparky clamd[549]: Mail files support enabled.
Jul 26 19:17:17 sparky clamd[549]: OLE2 support enabled.
Jul 26 19:17:17 sparky clamd[549]: PDF support enabled.
Jul 26 19:17:17 sparky clamd[549]: SWF support enabled.
Jul 26 19:17:17 sparky clamd[549]: HTML support enabled.
Jul 26 19:17:17 sparky clamd[549]: XMLDOCS support enabled.
Jul 26 19:17:17 sparky clamd[549]: HWP3 support enabled.
Jul 26 19:17:17 sparky clamd[549]: Self checking every 3600 seconds.
Jul 26 19:17:17 sparky freshclam[508]: Downloading daily-23599.cdiff [100%]
Jul 26 19:17:19 sparky freshclam[508]: daily.cld updated (version: 23599, sigs: 1740744, f-level: 63, builder: neo)
Jul 26 19:17:20 sparky exim4[721]: Starting MTA: exim4.
Jul 26 19:17:20 sparky freshclam[508]: Downloading bytecode-307.cdiff [100%]
Jul 26 19:17:20 sparky systemd[1]: Started LSB: exim Mail Transport Agent.
-- Subject: Unit exim4.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit exim4.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:20 sparky systemd[1]: Reached target Multi-User System.
-- Subject: Unit multi-user.target has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit multi-user.target has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:20 sparky systemd[1]: Reached target Graphical Interface.
-- Subject: Unit graphical.target has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit graphical.target has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:20 sparky systemd[1]: Starting Update UTMP about System Runlevel Changes...
-- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-update-utmp-runlevel.service has begun starting up.
Jul 26 19:17:20 sparky systemd[1]: Started Update UTMP about System Runlevel Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 19:17:21 sparky freshclam[508]: bytecode.cld updated (version: 307, sigs: 68, f-level: 63, builder: anvilleg)
Jul 26 19:17:22 sparky freshclam[508]: Database updated (6307061 signatures) from db.local.clamav.net (IP: 130.59.113.36)
Jul 26 19:17:22 sparky freshclam[508]: Clamd successfully notified about the update.
Jul 26 19:17:23 sparky clamd[549]: Reading databases from /var/lib/clamav
Jul 26 19:17:29 sparky clamd[549]: Database correctly reloaded (6301447 signatures)
Jul 26 19:18:13 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:18:13 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:18:14 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:18:15 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:19:17 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:19:17 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:19:20 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:19:21 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:20:22 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:20:23 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:20:24 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:20:25 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:21:27 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:21:27 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:21:29 sparky ntpd[613]: Soliciting pool server 185.132.136.32
Jul 26 19:21:30 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:21:32 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:22:29 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:22:32 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:22:34 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:22:34 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:23:36 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:23:38 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:23:39 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:23:41 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:24:41 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:24:44 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:24:45 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:24:49 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:25:48 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:25:51 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:25:51 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:25:55 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:26:55 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:26:55 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:26:56 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:27:04 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:27:59 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:28:02 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:28:02 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:28:10 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:29:06 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:29:08 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:29:09 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:29:16 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:30:12 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:30:14 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:30:25 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:31:17 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:31:19 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:31:19 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:31:33 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:32:23 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:32:25 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:32:25 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:32:42 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:33:27 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:33:31 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:33:31 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:33:51 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:34:34 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:34:35 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:34:58 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:35:38 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:35:40 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:35:45 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:36:03 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:36:45 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:36:46 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:36:50 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:37:07 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:37:50 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:37:50 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:37:54 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:38:13 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:38:54 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:38:54 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:39:00 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:39:18 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:39:59 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:40:00 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:40:05 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:40:24 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:41:03 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:41:05 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:41:11 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:41:29 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:42:10 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:42:11 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:42:17 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:42:35 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:43:16 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:43:23 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:43:39 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:44:21 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:44:23 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:44:30 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:44:44 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:45:26 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:45:28 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:45:36 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:45:49 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:46:31 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:46:32 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:46:43 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:46:53 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:47:38 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:47:50 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:47:57 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:48:41 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:48:44 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:48:57 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:49:03 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:49:48 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:49:50 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:50:02 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:50:09 sparky ntpd[613]: Soliciting pool server 95.81.173.155
Jul 26 19:50:52 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:50:54 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:51:06 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:51:15 sparky ntpd[613]: Soliciting pool server 148.252.105.132
Jul 26 19:51:16 sparky ntpd[613]: Soliciting pool server 86.59.13.46
Jul 26 19:51:58 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:51:59 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:52:22 sparky ntpd[613]: Soliciting pool server 45.76.244.193
Jul 26 19:53:04 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:53:06 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:53:18 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:53:31 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:54:10 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:54:11 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:54:24 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:54:38 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:55:15 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:55:15 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:55:31 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:55:42 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:56:22 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:56:36 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:56:48 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 19:57:26 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:57:27 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:57:43 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:57:54 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:58:32 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:58:33 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 19:58:47 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 19:59:00 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 19:59:36 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:59:39 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 19:59:52 sparky wpa_supplicant[685]: wlan0: WPA: Group rekeying completed with 00:21:f2:05:2a:00 [GTK=TKIP]
Jul 26 19:59:53 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:00:09 sparky ntpd[613]: Soliciting pool server 85.236.191.80
Jul 26 20:00:43 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:00:45 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:01:00 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:01:14 sparky ntpd[613]: Soliciting pool server 122.252.184.186
Jul 26 20:01:15 sparky ntpd[613]: Soliciting pool server 78.46.93.106
Jul 26 20:01:16 sparky ntpd[613]: Soliciting pool server 87.124.126.49
Jul 26 20:01:17 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 20:01:50 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:01:50 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:02:04 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:02:23 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:02:46 sparky systemd[1]: Started Run anacron jobs.
-- Subject: Unit anacron.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit anacron.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:02:46 sparky anacron[1291]: Anacron 2.3 started on 2017-07-26
Jul 26 20:02:46 sparky anacron[1291]: Normal exit (0 jobs run)
Jul 26 20:02:56 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:02:57 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:03:08 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:03:32 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:04:00 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:04:03 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:04:13 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:04:39 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:05:07 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:05:08 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:05:20 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:05:48 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:06:14 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:06:14 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:06:25 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:06:56 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 20:07:20 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:07:20 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:07:29 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:08:05 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:08:24 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:08:25 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:08:33 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:09:11 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:09:28 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:09:32 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:09:37 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:10:18 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:10:33 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:10:39 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:10:43 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:11:25 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:11:38 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:11:43 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:11:48 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:12:33 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 20:12:42 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:12:47 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:12:55 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:13:40 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:13:49 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:13:51 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:14:01 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:14:49 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:14:55 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:14:57 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:15:05 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:15:56 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:16:01 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:16:02 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:16:12 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:17:01 sparky CRON[1359]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 26 20:17:01 sparky CRON[1360]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 26 20:17:01 sparky CRON[1359]: pam_unix(cron:session): session closed for user root
Jul 26 20:17:04 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:17:05 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:17:08 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:17:18 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:17:20 sparky freshclam[508]: Received signal: wake up
Jul 26 20:17:20 sparky freshclam[508]: ClamAV update process started at Wed Jul 26 20:17:20 2017
Jul 26 20:17:20 sparky freshclam[508]: main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Jul 26 20:17:20 sparky freshclam[508]: daily.cld is up to date (version: 23599, sigs: 1740744, f-level: 63, builder: neo)
Jul 26 20:17:20 sparky freshclam[508]: bytecode.cld is up to date (version: 307, sigs: 68, f-level: 63, builder: anvilleg)
Jul 26 20:18:09 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:18:13 sparky ntpd[613]: Soliciting pool server 2a02:8106:1:8800::3
Jul 26 20:18:15 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:18:23 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:19:15 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:19:21 sparky ntpd[613]: Soliciting pool server 2001:470:0:2c8::2
Jul 26 20:19:21 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:19:30 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:20:20 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:20:27 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:20:30 sparky ntpd[613]: Soliciting pool server 2001:418:8405:4002::3
Jul 26 20:20:34 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:21:25 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:21:32 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:21:38 sparky ntpd[613]: Soliciting pool server 2001:67c:24c:1::20
Jul 26 20:21:40 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:22:30 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:22:36 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:22:44 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:22:47 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:23:37 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:23:43 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:23:51 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:23:54 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:24:27 sparky login[743]: pam_unix(login:session): session opened for user john by LOGIN(uid=0)
Jul 26 20:24:27 sparky systemd[1]: Created slice User Slice of john.
-- Subject: Unit user-1000.slice has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit user-1000.slice has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1]: Starting User Manager for UID 1000...
-- Subject: Unit user@1000.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit user@1000.service has begun starting up.
Jul 26 20:24:27 sparky systemd-logind[504]: New session 3 of user john.
-- Subject: A new session 3 has been created for user john
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
-- 
-- A new session with the ID 3 has been created for the user john.
-- 
-- The leading process of the session is 743.
Jul 26 20:24:27 sparky systemd[1]: Started Session 3 of user john.
-- Subject: Unit session-3.scope has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit session-3.scope has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: pam_unix(systemd-user:session): session opened for user john by (uid=0)
Jul 26 20:24:27 sparky systemd[1392]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Listening on GnuPG cryptographic agent and passphrase cache.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Reached target Timers.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Listening on GnuPG network certificate management daemon.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Reached target Paths.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Listening on GnuPG cryptographic agent (access for web browsers).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Starting D-Bus User Message Bus Socket.
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has begun starting up.
Jul 26 20:24:27 sparky systemd[1392]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Listening on D-Bus User Message Bus Socket.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky systemd[1392]: Startup finished in 201ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The user manager instance for user 1000 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
-- 
-- Startup of the manager took 201443 microseconds.
Jul 26 20:24:27 sparky systemd[1]: Started User Manager for UID 1000.
-- Subject: Unit user@1000.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit user@1000.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky dbus[516]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Jul 26 20:24:27 sparky systemd[1]: Starting Console Manager...
-- Subject: Unit console-kit-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit console-kit-daemon.service has begun starting up.
Jul 26 20:24:27 sparky udev-acl.ck[1461]: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul 26 20:24:27 sparky console-kit-daemon[1398]: missing action
Jul 26 20:24:27 sparky dbus[516]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jul 26 20:24:27 sparky systemd[1]: Started Console Manager.
-- Subject: Unit console-kit-daemon.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit console-kit-daemon.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:27 sparky udev-acl.ck[1470]: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul 26 20:24:41 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:24:43 sparky sudo[1480]:     john : TTY=tty1 ; PWD=/home/john ; USER=root ; COMMAND=/bin/systemctl start lightdm
Jul 26 20:24:43 sparky sudo[1480]: pam_unix(sudo:session): session opened for user root by john(uid=0)
Jul 26 20:24:43 sparky systemd[1]: Starting Light Display Manager...
-- Subject: Unit lightdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has begun starting up.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 26 20:24:43 sparky systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 20:24:43 sparky systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has begun starting up.
Jul 26 20:24:43 sparky sudo[1480]: pam_unix(sudo:session): session closed for user root
Jul 26 20:24:43 sparky systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 26 20:24:43 sparky systemd[1]: Stopped Light Display Manager.
-- Subject: Unit lightdm.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has finished shutting down.
Jul 26 20:24:43 sparky systemd[1]: Starting Light Display Manager...
-- Subject: Unit lightdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has begun starting up.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 26 20:24:43 sparky systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 20:24:43 sparky systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has begun starting up.
Jul 26 20:24:43 sparky systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 26 20:24:43 sparky systemd[1]: Stopped Light Display Manager.
-- Subject: Unit lightdm.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has finished shutting down.
Jul 26 20:24:43 sparky systemd[1]: Starting Light Display Manager...
-- Subject: Unit lightdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has begun starting up.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 26 20:24:43 sparky systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 20:24:43 sparky systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has begun starting up.
Jul 26 20:24:43 sparky systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 26 20:24:43 sparky systemd[1]: Stopped Light Display Manager.
-- Subject: Unit lightdm.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has finished shutting down.
Jul 26 20:24:43 sparky systemd[1]: Starting Light Display Manager...
-- Subject: Unit lightdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has begun starting up.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 26 20:24:43 sparky systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 20:24:43 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 20:24:43 sparky systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has begun starting up.
Jul 26 20:24:43 sparky systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 26 20:24:44 sparky systemd[1]: Stopped Light Display Manager.
-- Subject: Unit lightdm.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has finished shutting down.
Jul 26 20:24:44 sparky systemd[1]: Starting Light Display Manager...
-- Subject: Unit lightdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has begun starting up.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 26 20:24:44 sparky systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 20:24:44 sparky systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has begun starting up.
Jul 26 20:24:44 sparky systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 26 20:24:44 sparky systemd[1]: Stopped Light Display Manager.
-- Subject: Unit lightdm.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has finished shutting down.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Start request repeated too quickly.
Jul 26 20:24:44 sparky systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Unit entered failed state.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jul 26 20:24:44 sparky systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 26 20:24:44 sparky systemd[1]: plymouth-quit.service: Start request repeated too quickly.
Jul 26 20:24:44 sparky systemd[1]: Failed to start Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plymouth-quit.service has failed.
-- 
-- The result is failed.
Jul 26 20:24:44 sparky systemd[1]: plymouth-quit.service: Unit entered failed state.
Jul 26 20:24:44 sparky systemd[1]: plymouth-quit.service: Failed with result 'start-limit-hit'.
Jul 26 20:24:49 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:24:58 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:25:00 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:25:04 sparky sudo[1536]:     john : TTY=tty1 ; PWD=/home/john ; USER=root ; COMMAND=/bin/journalctl -xe
Jul 26 20:25:04 sparky sudo[1536]: pam_unix(sudo:session): session opened for user root by john(uid=0)
Jul 26 20:25:48 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:25:56 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:26:05 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:26:05 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:26:53 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:27:01 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:27:12 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:27:14 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 20:27:59 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:28:08 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:28:16 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:28:20 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:29:04 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:29:12 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:29:21 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:29:28 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:30:11 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:30:17 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:30:27 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:30:36 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:31:16 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:31:21 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:31:42 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:32:20 sparky ntpd[613]: Soliciting pool server 193.145.15.15
Jul 26 20:32:28 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:32:39 sparky ntpd[613]: Soliciting pool server 5.148.175.134
Jul 26 20:32:51 sparky ntpd[613]: Soliciting pool server 2001:720:1410:101f::15
Jul 26 20:33:27 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:33:35 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:33:42 sparky ntpd[613]: Soliciting pool server 80.241.208.120
Jul 26 20:34:00 sparky ntpd[613]: Soliciting pool server 213.251.52.234
Jul 26 20:34:32 sparky ntpd[613]: Soliciting pool server 81.19.96.148
Jul 26 20:34:42 sparky ntpd[613]: Soliciting pool server 158.227.98.15
Jul 26 20:34:46 sparky ntpd[613]: Soliciting pool server 5.200.6.34
Jul 26 20:59:53 sparky wpa_supplicant[685]: wlan0: WPA: Group rekeying completed with 00:21:f2:05:2a:00 [GTK=TKIP]
Jul 26 21:00:46 sparky systemd[1]: Started Run anacron jobs.
-- Subject: Unit anacron.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit anacron.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 21:00:46 sparky anacron[1677]: Anacron 2.3 started on 2017-07-26
Jul 26 21:00:46 sparky anacron[1677]: Normal exit (0 jobs run)
Jul 26 21:17:01 sparky CRON[1730]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 26 21:17:01 sparky CRON[1731]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 26 21:17:01 sparky CRON[1730]: pam_unix(cron:session): session closed for user root
Jul 26 21:17:20 sparky freshclam[508]: Received signal: wake up
Jul 26 21:17:20 sparky freshclam[508]: ClamAV update process started at Wed Jul 26 21:17:20 2017
Jul 26 21:17:21 sparky freshclam[508]: main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Jul 26 21:17:21 sparky freshclam[508]: daily.cld is up to date (version: 23599, sigs: 1740744, f-level: 63, builder: neo)
Jul 26 21:17:21 sparky freshclam[508]: bytecode.cld is up to date (version: 307, sigs: 68, f-level: 63, builder: anvilleg)
Jul 26 21:17:27 sparky clamd[549]: SelfCheck: Database status OK.
Jul 26 21:59:54 sparky wpa_supplicant[685]: wlan0: WPA: Group rekeying completed with 00:21:f2:05:2a:00 [GTK=TKIP]
Jul 26 22:02:46 sparky systemd[1]: Started Run anacron jobs.
-- Subject: Unit anacron.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit anacron.service has finished starting up.
-- 
-- The start-up result is done.
Jul 26 22:02:46 sparky anacron[1887]: Anacron 2.3 started on 2017-07-26
Jul 26 22:02:46 sparky anacron[1887]: Normal exit (0 jobs run)
Jul 26 22:17:01 sparky CRON[1939]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 26 22:17:01 sparky CRON[1940]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 26 22:17:01 sparky CRON[1939]: pam_unix(cron:session): session closed for user root
Jul 26 22:17:21 sparky freshclam[508]: Received signal: wake up
Jul 26 22:17:21 sparky freshclam[508]: ClamAV update process started at Wed Jul 26 22:17:21 2017
Jul 26 22:17:21 sparky freshclam[508]: main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Jul 26 22:17:21 sparky freshclam[508]: daily.cld is up to date (version: 23599, sigs: 1740744, f-level: 63, builder: neo)
Jul 26 22:17:21 sparky freshclam[508]: bytecode.cld is up to date (version: 307, sigs: 68, f-level: 63, builder: anvilleg)
Jul 26 22:17:27 sparky clamd[549]: SelfCheck: Database status OK.
Jul 26 22:58:18 sparky sudo[1536]: pam_unix(sudo:session): session closed for user root
Jul 26 22:58:45 sparky sudo[2072]:     john : TTY=tty1 ; PWD=/home/john ; USER=root ; COMMAND=/bin/journalctl -xe
Jul 26 22:58:45 sparky sudo[2072]: pam_unix(sudo:session): session opened for user root by john(uid=0)

The is no /var/log/lightdm/x-0-greeter.log. The files in that directory (/var/log/lightdm/) are as follows:

lightdm.log
lightdm.log.old
seat0-greeter.log
seat0-greeter.log.old
x-0.log
x-0.log.old

pavroo · July 30, 2017, 02:21:11 PM

Reinstall lightdm:

Code Select

sudo install --reinstall lightdm
If still no luck, install different login manager, slim for example:

Code Select

sudo apt update
sudo apt install slim

and choose slim as default.

johnh009 · July 30, 2017, 07:02:04 PM

Thank you for your response.

I had tried reinstalling lightdm previously, but that didn't work. I tried again, in the hope that something may have changed in the meantime, but still no luck.

I executed the last two commands as requested, but trying to start slim produces the same errors as trying to start lightdm.

Code Select


sudo systemctl status slim.service

produces the same output as for lightdm (except for the login manager name).

johnh009 · August 05, 2017, 12:26:59 PM

A bit more info that may - hopefully - give someone a clue as to what has gone wrong.

1. The /dev and /sys directories/folders are completely empty; nothing, not a sausage, nada, bugger all. The same folders on my xubuntu system have 198 & 11 entries respectively, so it seems as though at some point the contents of this directories/folders have been deleted.

I'm coming round to thinking that I need to reinstall the whole system again, which I hate doing, as I nearly always manage to lose some vital file! (I know, it's my own fault for not doing rigorous back-ups). Unless, of course, a Sparky genius - and I know there are plenty out there - can suggest something else. Please!

paxmark1 · August 07, 2017, 04:41:56 AM

You don't need a gui to backup . Lots of info out there, rsync scripts, etc.

https://wiki.archlinux.org/index.php/Rsync#As_a_backup_utility

and from a decades long debian dev
https://obnam.org very detailed man page. lots of python dependencies..

Myself, I just use Spideroak

edit later. obnam is being slowly deprecated by the dev. Should still be good for stable debian. I still use spideroak myself.

johnh009 · September 25, 2017, 01:20:40 PM

OK, guys, thanks for your efforts and suggestions. I think something serious went wrong due to the empty file system directories, though I haven't a clue as to what! A HDD check has not revealed any errors at all, which I suspected, so I'm baffled.

Anyway, the upshot is that I had to reinstall the system and all is honk dory once more.

Thanks again.