Debian-facile

Anonyme-11

Invité

[résolu]Kern.log et sys.log de plusieurs Go

Bonjour,
suite a la remarque de raleur, j'ai fait ma petite investigation!
Je pense que la taille de mon kern.log n'a pas de rapport avec mon sys.log
Premièrement, je pense avoir fait une mauvaise utilisation de ces commande:

mount -t iso9660 IMAGE.iso REPERTOIRE -o ro
umount /home/jeff/toto.iso
rmdir /home/jeff/toto
rmmod loop

Sauf erreur de ma part, je n'ai pas utiliser la commande rmmod loop .
Est ce que j'aurai ainsi laisser allumer une boucle qui écrivait dans le log?

cat /var/log/kern.log | more

Oct  1 09:10:06 MSIA320MA10 kernel: [36283.267340] loop: module loaded
Oct  1 09:14:13 MSIA320MA10 kernel: [36530.432897] ISO 9660 Extensions: Microsoft Joliet Level 3
Oct  1 09:14:13 MSIA320MA10 kernel: [36530.476745] ISOFS: changing to secondary root
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453191] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453196] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453198] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453199] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453228] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453230] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453252] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453253] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453273] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453274] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453295] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453296] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453316] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453317] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453337] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453338] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453358] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453359] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453378] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453380] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453399] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453400] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453420] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453421] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453441] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453442] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453461] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453462] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453482] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453483] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453503] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453504] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453523] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453524] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453543] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453544] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453564] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453565] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453585] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453586] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453605] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453606] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453625] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453627] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453646] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453647] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453666] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453667] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453687] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453688] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453708] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453709] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453728] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453729] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453749] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453750] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453769] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453771] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453790] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453791] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453810] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453812] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453831] attempt to access beyond end of device
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453832] loop0: rw=0, want=7651592, limit=2259384
Oct  1 09:14:55 MSIA320MA10 kernel: [36572.453852] attempt to access beyond end of device

Deuxièmement, j'ai remarqué dans mon fichier syslog, qu'un service redémarre constamment!
plus de 1700 fois depuis que j'ai allumé mon pc (a 7h00).

cat /var/log/syslog | more

Oct  2 07:10:23 MSIA320MA10 rsyslogd:  [origin software="rsyslogd" swVersion="8.38.0" x-pid="527" x-info="http://www.rsyslog.com"] rsyslogd
was HUPed
Oct  2 07:10:23 MSIA320MA10 kernel: [    6.784837] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Oct  2 07:10:23 MSIA320MA10 systemd[1]: Started Rotate log files.
Oct  2 07:10:23 MSIA320MA10 NetworkManager[523]: <info>  [1538457023.6649] device (wlp4s0): set-hw-addr: set MAC address to BE:A1:BF:8E:ED:6
5 (scanning)
Oct  2 07:10:24 MSIA320MA10 kernel: [    7.524960] [drm:gfx_v8_0_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out.
Oct  2 07:10:24 MSIA320MA10 kernel: [    7.525045] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 9 (-110).
Oct  2 07:10:24 MSIA320MA10 kernel: [    7.541158] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Oct  2 07:10:24 MSIA320MA10 NetworkManager[523]: <info>  [1538457024.2495] supplicant: wpa_supplicant running
Oct  2 07:10:24 MSIA320MA10 NetworkManager[523]: <info>  [1538457024.2496] device (wlp4s0): supplicant interface state: init -> starting
Oct  2 07:10:24 MSIA320MA10 NetworkManager[523]: <info>  [1538457024.2497] modem-manager: ModemManager available
Oct  2 07:10:24 MSIA320MA10 kernel: [    7.657923] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110)
.
Oct  2 07:10:24 MSIA320MA10 NetworkManager[523]: <info>  [1538457024.3906] sup-iface[0x5611da72b0d0,wlp4s0]: supports 4 scan SSIDs
Oct  2 07:10:24 MSIA320MA10 NetworkManager[523]: <info>  [1538457024.3917] device (wlp4s0): supplicant interface state: starting -> ready
Oct  2 07:10:24 MSIA320MA10 NetworkManager[523]: <info>  [1538457024.3918] device (wlp4s0): state change: unavailable -> disconnected (reaso
n 'supplicant-available', sys-iface-state: 'managed')
Oct  2 07:10:24 MSIA320MA10 kernel: [    7.700322] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Oct  2 07:10:24 MSIA320MA10 ModemManager[514]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0'
: not supported by any plugin
Oct  2 07:10:24 MSIA320MA10 ModemManager[514]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.4/0000:05:00.2/
0000:16:04.0/0000:1b:00.0': not supported by any plugin
Oct  2 07:10:25 MSIA320MA10 dbus-daemon[608]: [session uid=115 pid=608] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbu
s-bus.service' requested by ':1.10' (uid=115 pid=621 comm="/usr/bin/gnome-shell ")
Oct  2 07:10:25 MSIA320MA10 systemd[595]: Starting Accessibility services bus...
Oct  2 07:10:25 MSIA320MA10 dbus-daemon[608]: [session uid=115 pid=608] Successfully activated service 'org.a11y.Bus'
Oct  2 07:10:25 MSIA320MA10 systemd[595]: Started Accessibility services bus.
Oct  2 07:10:25 MSIA320MA10 at-spi-bus-launcher[657]: dbus-daemon[662]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0
' (uid=115 pid=621 comm="/usr/bin/gnome-shell ")
Oct  2 07:10:25 MSIA320MA10 at-spi-bus-launcher[657]: dbus-daemon[662]: Successfully activated service 'org.a11y.atspi.Registry'
Oct  2 07:10:25 MSIA320MA10 at-spi-bus-launcher[657]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct  2 07:10:25 MSIA320MA10 systemd[595]: Starting Sound Service...
Oct  2 07:10:25 MSIA320MA10 rtkit-daemon[518]: Supervising 0 threads of 0 processes of 1 users.
Oct  2 07:10:25 MSIA320MA10 rtkit-daemon[518]: Supervising 0 threads of 0 processes of 1 users.
Oct  2 07:10:25 MSIA320MA10 rtkit-daemon[518]: Supervising 0 threads of 0 processes of 1 users.
Oct  2 07:10:25 MSIA320MA10 rtkit-daemon[518]: Supervising 0 threads of 0 processes of 1 users.
Oct  2 07:10:25 MSIA320MA10 rtkit-daemon[518]: Supervising 0 threads of 0 processes of 1 users.
Oct  2 07:10:25 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' reques
ted by ':1.59' (uid=115 pid=668 comm="/usr/bin/pulseaudio --daemonize=no ")
Oct  2 07:10:26 MSIA320MA10 systemd[595]: Started Sound Service.
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.0438] policy: auto-activating connection 'freebox_QTUHOB' (229ae45e-a72
8-4129-9978-e4ec185c82de)
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.0457] device (wlp4s0): Activation: starting connection 'freebox_QTUHOB'
 (229ae45e-a728-4129-9978-e4ec185c82de)
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.0461] device (wlp4s0): state change: disconnected -> prepare (reason 'n
one', sys-iface-state: 'managed')
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.0474] manager: NetworkManager state is now CONNECTING
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.0530] device (wlp4s0): set-hw-addr: reset MAC address to 50:3E:AA:64:6E
:F9 (preserve)
Oct  2 07:10:26 MSIA320MA10 kernel: [    9.927203] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6202] device (wlp4s0): supplicant interface state: ready -> disabled
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6203] device (wlp4s0): state change: prepare -> config (reason 'none',
sys-iface-state: 'managed')
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6207] device (wlp4s0): Activation: (wifi) access point 'freebox_QTUHOB'
 has security, but secrets are required.
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6207] device (wlp4s0): state change: config -> need-auth (reason 'none'
, sys-iface-state: 'managed')
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6232] device (wlp4s0): state change: need-auth -> prepare (reason 'none
', sys-iface-state: 'managed')
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6239] device (wlp4s0): state change: prepare -> config (reason 'none',
sys-iface-state: 'managed')
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6243] device (wlp4s0): Activation: (wifi) connection 'freebox_QTUHOB' h
as security, and secrets exist.  No new secrets needed.
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6244] Config: added 'ssid' value 'freebox_QTUHOB'
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6244] Config: added 'scan_ssid' value '1'
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6244] Config: added 'bgscan' value 'simple:30:-80:86400'
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6244] Config: added 'key_mgmt' value 'WPA-PSK'
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6244] Config: added 'psk' value '<hidden>'
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6528] device (wlp4s0): supplicant interface state: disabled -> inactive
Oct  2 07:10:26 MSIA320MA10 NetworkManager[523]: <info>  [1538457026.6708] device (wlp4s0): supplicant interface state: inactive -> scanning
Oct  2 07:10:27 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedes
ktop.locale1.service' requested by ':1.24' (uid=115 pid=621 comm="/usr/bin/gnome-shell ")
Oct  2 07:10:27 MSIA320MA10 systemd[1]: Starting Locale Service...
Oct  2 07:10:27 MSIA320MA10 gnome-shell[621]: Failed to launch ibus-daemon: L’exécution du processus fils « ibus-daemon » a échoué (Aucun fi
chier ou dossier de ce type)
Oct  2 07:10:27 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct  2 07:10:27 MSIA320MA10 systemd[1]: Started Locale Service.
Oct  2 07:10:27 MSIA320MA10 wpa_supplicant[522]: wlp4s0: SME: Trying to authenticate with d2:d4:2a:d3:d2:68 (SSID='freebox_QTUHOB' freq=2412
 MHz)
Oct  2 07:10:27 MSIA320MA10 kernel: [   11.021383] wlp4s0: authenticate with d2:d4:2a:d3:d2:68
Oct  2 07:10:27 MSIA320MA10 NetworkManager[523]: <info>  [1538457027.7452] device (wlp4s0): supplicant interface state: scanning -> authenti
cating
Oct  2 07:10:27 MSIA320MA10 kernel: [   11.052850] wlp4s0: send auth to d2:d4:2a:d3:d2:68 (try 1/3)
Oct  2 07:10:27 MSIA320MA10 wpa_supplicant[522]: wlp4s0: Trying to associate with d2:d4:2a:d3:d2:68 (SSID='freebox_QTUHOB' freq=2412 MHz)
Oct  2 07:10:27 MSIA320MA10 kernel: [   11.068369] wlp4s0: authenticated
Oct  2 07:10:27 MSIA320MA10 kernel: [   11.072105] wlp4s0: associate with d2:d4:2a:d3:d2:68 (try 1/3)
Oct  2 07:10:27 MSIA320MA10 NetworkManager[523]: <info>  [1538457027.7663] device (wlp4s0): supplicant interface state: authenticating -> as
sociating
Oct  2 07:10:27 MSIA320MA10 kernel: [   11.170876] wlp4s0: RX AssocResp from d2:d4:2a:d3:d2:68 (capab=0x411 status=0 aid=3)
Oct  2 07:10:27 MSIA320MA10 wpa_supplicant[522]: wlp4s0: Associated with d2:d4:2a:d3:d2:68
Oct  2 07:10:27 MSIA320MA10 wpa_supplicant[522]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct  2 07:10:27 MSIA320MA10 kernel: [   11.176373] wlp4s0: associated
Oct  2 07:10:27 MSIA320MA10 NetworkManager[523]: <info>  [1538457027.8742] device (wlp4s0): supplicant interface state: associating -> assoc
iated
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' r
equested by ':1.24' (uid=115 pid=621 comm="/usr/bin/gnome-shell ")
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Starting Daemon for power management...
Oct  2 07:10:28 MSIA320MA10 gnome-shell[621]: g_dir_open_with_errno: assertion 'path != NULL' failed
Oct  2 07:10:28 MSIA320MA10 gnome-shell[621]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Oct  2 07:10:28 MSIA320MA10 gnome-shell[621]: g_dir_open_with_errno: assertion 'path != NULL' failed
Oct  2 07:10:28 MSIA320MA10 gnome-shell[621]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service
' requested by ':1.24' (uid=115 pid=621 comm="/usr/bin/gnome-shell ")
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Starting Location Lookup Service...
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.se
rvice' requested by ':1.24' (uid=115 pid=621 comm="/usr/bin/gnome-shell ")
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Starting PackageKit Daemon...
Oct  2 07:10:28 MSIA320MA10 PackageKit: daemon start
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.UPower'
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Started Daemon for power management.
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Started Location Lookup Service.
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Started PackageKit Daemon.
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.realmd' unit='realmd.service' r
equested by ':1.24' (uid=115 pid=621 comm="/usr/bin/gnome-shell ")
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Starting Realm and Domain Configuration...
Oct  2 07:10:28 MSIA320MA10 gnome-shell[621]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.freedesktop.impl.portal.PermissionStore was not provided by any .service files
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.realmd'
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Started Realm and Domain Configuration.
Oct  2 07:10:28 MSIA320MA10 NetworkManager[523]: <info>  [1538457028.6342] device (wlp4s0): supplicant interface state: associated -> 4-way
handshake
Oct  2 07:10:28 MSIA320MA10 NetworkManager[523]: <info>  [1538457028.6586] device (wlp4s0): supplicant interface state: 4-way handshake -> g
roup handshake
Oct  2 07:10:28 MSIA320MA10 gnome-shell[621]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1573]: reference to undefined pro
perty "MetaWindowXwayland"
Oct  2 07:10:28 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.serv
ice' requested by ':1.104' (uid=115 pid=704 comm="/usr/lib/gnome-settings-daemon/gsd-color ")
Oct  2 07:10:28 MSIA320MA10 systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct  2 07:10:29 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct  2 07:10:29 MSIA320MA10 systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct  2 07:10:29 MSIA320MA10 gnome-session-binary[610]: Entering running state
Oct  2 07:10:29 MSIA320MA10 xbrlapi.desktop[860]: openConnection: connect: Aucun fichier ou dossier de ce type
Oct  2 07:10:29 MSIA320MA10 xbrlapi.desktop[860]: cannot connect to braille devices daemon brltty at :0
Oct  2 07:10:31 MSIA320MA10 wpa_supplicant[522]: wlp4s0: WPA: Key negotiation completed with d2:d4:2a:d3:d2:68 [PTK=CCMP GTK=TKIP]
Oct  2 07:10:31 MSIA320MA10 wpa_supplicant[522]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to d2:d4:2a:d3:d2:68 completed [id=0 id_str=]
Oct  2 07:10:31 MSIA320MA10 wpa_supplicant[522]: bgscan simple: Failed to enable signal strength monitoring
Oct  2 07:10:31 MSIA320MA10 kernel: [   14.960828] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.6610] device (wlp4s0): supplicant interface state: group handshake -> c
ompleted
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.6611] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configur
e) successful.  Connected to wireless network 'freebox_QTUHOB'.
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.6613] device (wlp4s0): state change: config -> ip-config (reason 'none'
, sys-iface-state: 'managed')
Oct  2 07:10:31 MSIA320MA10 avahi-daemon[516]: Joining mDNS multicast group on interface wlp4s0.IPv6 with address fe80::523e:aaff:fe64:6ef9.
Oct  2 07:10:31 MSIA320MA10 avahi-daemon[516]: New relevant interface wlp4s0.IPv6 for mDNS.
Oct  2 07:10:31 MSIA320MA10 avahi-daemon[516]: Registering new address record for fe80::523e:aaff:fe64:6ef9 on wlp4s0.*.
Oct  2 07:10:31 MSIA320MA10 avahi-daemon[516]: Joining mDNS multicast group on interface wlp4s0.IPv4 with address 192.168.0.22.
Oct  2 07:10:31 MSIA320MA10 avahi-daemon[516]: New relevant interface wlp4s0.IPv4 for mDNS.
Oct  2 07:10:31 MSIA320MA10 avahi-daemon[516]: Registering new address record for 192.168.0.22 on wlp4s0.IPv4.
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.6645] device (wlp4s0): state change: ip-config -> ip-check (reason 'non
e', sys-iface-state: 'managed')
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.6664] device (wlp4s0): state change: ip-check -> secondaries (reason 'n
one', sys-iface-state: 'managed')
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.6668] device (wlp4s0): state change: secondaries -> activated (reason '
none', sys-iface-state: 'managed')
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.6672] manager: NetworkManager state is now CONNECTED_LOCAL
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.7432] manager: NetworkManager state is now CONNECTED_SITE
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.7436] policy: set 'freebox_QTUHOB' (wlp4s0) as default for IPv4 routing
 and DNS
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.7439] device (wlp4s0): Activation: successful, device activated.
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.7449] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct  2 07:10:31 MSIA320MA10 NetworkManager[523]: <info>  [1538457031.7454] manager: startup complete
Oct  2 07:10:31 MSIA320MA10 nm-dispatcher: req:3 'up' [wlp4s0]: new request (1 scripts)
Oct  2 07:10:31 MSIA320MA10 nm-dispatcher: req:3 'up' [wlp4s0]: start running ordered scripts...
Oct  2 07:10:31 MSIA320MA10 nm-dispatcher: req:4 'connectivity-change': new request (1 scripts)
Oct  2 07:10:31 MSIA320MA10 systemd[1]: Started Network Manager Wait Online.
Oct  2 07:10:31 MSIA320MA10 systemd[1]: Reached target Network is Online.
Oct  2 07:10:31 MSIA320MA10 systemd[1]: Starting keep memory of all UPnP devices that announced themselves...
Oct  2 07:10:31 MSIA320MA10 systemd[1]: Starting Daily apt download activities...
Oct  2 07:10:31 MSIA320MA10 systemd[1]: Starting LSB: exim Mail Transport Agent...
Oct  2 07:10:31 MSIA320MA10 nm-dispatcher[583]: grep: /etc/resolv.conf: No such file or directory
Oct  2 07:10:31 MSIA320MA10 systemd[1]: minissdpd.service: Can't open PID file /var/run/minissdpd.pid (yet?) after start: No such file or di
rectory
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 systemd[1]: Started keep memory of all UPnP devices that announced themselves.
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:10:31 MSIA320MA10 nm-dispatcher[583]: grep: /etc/resolv.conf: No such file or directory
Oct  2 07:10:31 MSIA320MA10 nm-dispatcher: req:4 'connectivity-change': start running ordered scripts...
Oct  2 07:10:32 MSIA320MA10 exim4[877]: Starting MTA: exim4.
Oct  2 07:10:32 MSIA320MA10 systemd[1]: Started LSB: exim Mail Transport Agent.
Oct  2 07:10:32 MSIA320MA10 systemd[1]: Reached target Multi-User System.
Oct  2 07:10:32 MSIA320MA10 systemd[1]: Reached target Graphical Interface.
Oct  2 07:10:32 MSIA320MA10 systemd[1]: Starting Update UTMP about System Runlevel Changes...
Oct  2 07:10:32 MSIA320MA10 systemd[1]: Started Update UTMP about System Runlevel Changes.
Oct  2 07:10:33 MSIA320MA10 avahi-daemon[516]: Leaving mDNS multicast group on interface wlp4s0.IPv6 with address fe80::523e:aaff:fe64:6ef9.
Oct  2 07:10:33 MSIA320MA10 avahi-daemon[516]: Joining mDNS multicast group on interface wlp4s0.IPv6 with address 2a01:e34:ee5d:2e70:523e:aa
ff:fe64:6ef9.
Oct  2 07:10:33 MSIA320MA10 NetworkManager[523]: <info>  [1538457033.6999] policy: set 'freebox_QTUHOB' (wlp4s0) as default for IPv6 routing
 and DNS
Oct  2 07:10:33 MSIA320MA10 avahi-daemon[516]: Registering new address record for 2a01:e34:ee5d:2e70:523e:aaff:fe64:6ef9 on wlp4s0.*.
Oct  2 07:10:33 MSIA320MA10 avahi-daemon[516]: Withdrawing address record for fe80::523e:aaff:fe64:6ef9 on wlp4s0.
Oct  2 07:10:35 MSIA320MA10 avahi-daemon[516]: Registering new address record for 2a01:e34:ee5d:2e70:6c53:cb9f:adf1:ed7a on wlp4s0.*.
Oct  2 07:10:50 MSIA320MA10 pulseaudio[668]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the r
eply, the reply timeout expired, or the network connection was broken.
Oct  2 07:10:51 MSIA320MA10 systemd-timesyncd[479]: Synchronized to time server [2a00:1080:807:200::5:1]:123 (2.debian.pool.ntp.org).
Oct  2 07:10:59 MSIA320MA10 kernel: [   44.290013] random: crng init done
Oct  2 07:10:59 MSIA320MA10 kernel: [   44.290018] random: 7 urandom warning(s) missed due to ratelimiting
Oct  2 07:11:20 MSIA320MA10 systemd[1]: Started Daily apt download activities.
Oct  2 07:11:20 MSIA320MA10 systemd[1]: Starting Daily apt upgrade and clean activities...
Oct  2 07:11:33 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:36633 is not from a LAN
Oct  2 07:11:34 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:36633 is not from a LAN
Oct  2 07:11:35 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:36633 is not from a LAN
Oct  2 07:11:36 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:36633 is not from a LAN
Oct  2 07:11:41 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:52594 is not from a LAN
Oct  2 07:11:42 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:52594 is not from a LAN
Oct  2 07:11:43 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:52594 is not from a LAN
Oct  2 07:11:44 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:52594 is not from a LAN
Oct  2 07:11:47 MSIA320MA10 systemd[1]: Started Daily apt upgrade and clean activities.
Oct  2 07:11:47 MSIA320MA10 systemd[1]: Startup finished in 3.400s (kernel) + 1min 28.615s (userspace) = 1min 32.016s.
Oct  2 07:13:33 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:47584 is not from a LAN
Oct  2 07:13:34 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:47584 is not from a LAN
Oct  2 07:13:35 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:47584 is not from a LAN
Oct  2 07:13:36 MSIA320MA10 minissdpd[880]: peer 192.168.0.21:47584 is not from a LAN
Oct  2 07:13:41 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:56708 is not from a LAN
Oct  2 07:13:42 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:56708 is not from a LAN
Oct  2 07:13:43 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:56708 is not from a LAN
Oct  2 07:13:44 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:56708 is not from a LAN
Oct  2 07:15:20 MSIA320MA10 anacron[528]: Job `cron.daily' started
Oct  2 07:15:20 MSIA320MA10 anacron[2190]: Updated timestamp for job `cron.daily' to 2018-10-02
Oct  2 07:15:20 MSIA320MA10 cracklib: no dictionary update necessary.
Oct  2 07:15:21 MSIA320MA10 anacron[528]: Job `cron.daily' terminated
Oct  2 07:15:21 MSIA320MA10 anacron[528]: Normal exit (1 job run)
Oct  2 07:15:41 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60357 is not from a LAN
Oct  2 07:15:42 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60357 is not from a LAN
Oct  2 07:15:43 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60357 is not from a LAN
Oct  2 07:15:44 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60357 is not from a LAN
Oct  2 07:17:01 MSIA320MA10 CRON[2300]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:22 MSIA320MA10 minissdpd[880]: peer 192.168.0.254:1900 is not from a LAN
Oct  2 07:17:41 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47273 is not from a LAN
Oct  2 07:17:42 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47273 is not from a LAN
Oct  2 07:17:43 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47273 is not from a LAN
Oct  2 07:17:44 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47273 is not from a LAN
Oct  2 07:18:32 MSIA320MA10 kernel: [  497.424181] usb 4-3: new full-speed USB device number 2 using xhci_hcd
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.685528] usb 4-3: New USB device found, idVendor=062a, idProduct=4101, bcdDevice= 1.02
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.685534] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.685537] usb 4-3: Product: 2.4G Keyboard Mouse
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.685539] usb 4-3: Manufacturer: MOSART Semi.
Oct  2 07:18:33 MSIA320MA10 mtp-probe: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:02.4/0000:05:00.0/usb4/4-3"
Oct  2 07:18:33 MSIA320MA10 mtp-probe: bus: 4, device: 2 was not an MTP device
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.731933] hidraw: raw HID events driver (C) Jiri Kosina
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.773717] usbcore: registered new interface driver usbhid
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.773720] usbhid: USB HID core driver
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.778233] input: MOSART Semi. 2.4G Keyboard Mouse as /devices/pci0000:00/0000:00:02.4/0000:05:00.0/
usb4/4-3/4-3:1.0/0003:062A:4101.0001/input/input10
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.835857] hid-generic 0003:062A:4101.0001: input,hidraw0: USB HID v1.10 Keyboard [MOSART Semi. 2.4G
 Keyboard Mouse] on usb-0000:05:00.0-3/input0
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.836556] input: MOSART Semi. 2.4G Keyboard Mouse Mouse as /devices/pci0000:00/0000:00:02.4/0000:05
:00.0/usb4/4-3/4-3:1.1/0003:062A:4101.0002/input/input11
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.836763] input: MOSART Semi. 2.4G Keyboard Mouse Consumer Control as /devices/pci0000:00/0000:00:0
2.4/0000:05:00.0/usb4/4-3/4-3:1.1/0003:062A:4101.0002/input/input12
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.895544] input: MOSART Semi. 2.4G Keyboard Mouse System Control as /devices/pci0000:00/0000:00:02.
4/0000:05:00.0/usb4/4-3/4-3:1.1/0003:062A:4101.0002/input/input13
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.895679] input: MOSART Semi. 2.4G Keyboard Mouse as /devices/pci0000:00/0000:00:02.4/0000:05:00.0/
usb4/4-3/4-3:1.1/0003:062A:4101.0002/input/input14
Oct  2 07:18:33 MSIA320MA10 kernel: [  497.895892] hid-generic 0003:062A:4101.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi.
 2.4G Keyboard Mouse] on usb-0000:05:00.0-3/input1
Oct  2 07:19:09 MSIA320MA10 kernel: [  534.303670] usb 4-6: new high-speed USB device number 3 using xhci_hcd
Oct  2 07:19:10 MSIA320MA10 kernel: [  534.459774] usb 4-6: New USB device found, idVendor=1908, idProduct=0226, bcdDevice= 1.11
Oct  2 07:19:10 MSIA320MA10 kernel: [  534.459780] usb 4-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  2 07:19:10 MSIA320MA10 mtp-probe: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:02.4/0000:05:00.0/usb4/4-6"
Oct  2 07:19:10 MSIA320MA10 mtp-probe: bus: 4, device: 3 was not an MTP device
Oct  2 07:19:10 MSIA320MA10 kernel: [  534.483662] usb-storage 4-6:1.0: USB Mass Storage device detected
Oct  2 07:19:10 MSIA320MA10 kernel: [  534.484049] scsi host9: usb-storage 4-6:1.0
Oct  2 07:19:10 MSIA320MA10 kernel: [  534.484164] usbcore: registered new interface driver usb-storage
Oct  2 07:19:10 MSIA320MA10 kernel: [  534.485860] usbcore: registered new interface driver uas
Oct  2 07:19:11 MSIA320MA10 kernel: [  535.507017] scsi 9:0:0:0: Direct-Access     Generic  Mass-Storage     1.11 PQ: 0 ANSI: 2
Oct  2 07:19:11 MSIA320MA10 kernel: [  535.539363] sd 9:0:0:0: Attached scsi generic sg2 type 0
Oct  2 07:19:11 MSIA320MA10 kernel: [  536.243830] sd 9:0:0:0: [sdc] 62521344 512-byte logical blocks: (32.0 GB/29.8 GiB)
Oct  2 07:19:11 MSIA320MA10 kernel: [  536.246324] sd 9:0:0:0: [sdc] Write Protect is off
Oct  2 07:19:11 MSIA320MA10 kernel: [  536.246329] sd 9:0:0:0: [sdc] Mode Sense: 03 00 00 00
Oct  2 07:19:11 MSIA320MA10 kernel: [  536.248052] sd 9:0:0:0: [sdc] No Caching mode page found
Oct  2 07:19:11 MSIA320MA10 kernel: [  536.248062] sd 9:0:0:0: [sdc] Assuming drive cache: write through
Oct  2 07:19:11 MSIA320MA10 kernel: [  536.254582]  sdc: sdc1 sdc2
Oct  2 07:19:11 MSIA320MA10 kernel: [  536.261139] sd 9:0:0:0: [sdc] Attached SCSI removable disk
Oct  2 07:19:32 MSIA320MA10 systemd[1]: Started /run/user/1000 mount wrapper.
Oct  2 07:19:32 MSIA320MA10 systemd[1]: Created slice User Slice of UID 1000.
Oct  2 07:19:32 MSIA320MA10 systemd[1]: Starting User Manager for UID 1000...
Oct  2 07:19:32 MSIA320MA10 systemd[1]: Started Session 3 of user dimitri.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Listening on GnuPG network certificate management daemon.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Reached target Paths.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Listening on Sound System.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Starting D-Bus User Message Bus Socket.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Reached target Timers.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Listening on D-Bus User Message Bus Socket.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Reached target Sockets.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Reached target Basic System.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Reached target Default.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Startup finished in 72ms.
Oct  2 07:19:32 MSIA320MA10 systemd[1]: Started User Manager for UID 1000.
Oct  2 07:19:32 MSIA320MA10 systemd[2371]: Started D-Bus User Message Bus.
Oct  2 07:19:32 MSIA320MA10 gnome-keyring-ssh.desktop[2417]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct  2 07:19:32 MSIA320MA10 gnome-keyring-secrets.desktop[2419]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct  2 07:19:33 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='g
vfs-daemon.service' requested by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:33 MSIA320MA10 systemd[2371]: Starting Virtual filesystem service...
Oct  2 07:19:33 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gtk.vfs.Daemon'
Oct  2 07:19:33 MSIA320MA10 systemd[2371]: Started Virtual filesystem service.
Oct  2 07:19:33 MSIA320MA10 kernel: [  557.732810] fuse init (API version 7.27)
Oct  2 07:19:33 MSIA320MA10 systemd[1]: Mounting FUSE Control File System...
Oct  2 07:19:33 MSIA320MA10 systemd[1]: Mounted FUSE Control File System.
Oct  2 07:19:33 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-
dbus-bus.service' requested by ':1.13' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:33 MSIA320MA10 systemd[2371]: Starting Accessibility services bus...
Oct  2 07:19:33 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.a11y.Bus'
Oct  2 07:19:33 MSIA320MA10 systemd[2371]: Started Accessibility services bus.
Oct  2 07:19:33 MSIA320MA10 at-spi-bus-launcher[2473]: dbus-daemon[2478]: Activating service name='org.a11y.atspi.Registry' requested by ':1
.0' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:33 MSIA320MA10 at-spi-bus-launcher[2473]: dbus-daemon[2478]: Successfully activated service 'org.a11y.atspi.Registry'
Oct  2 07:19:33 MSIA320MA10 at-spi-bus-launcher[2473]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct  2 07:19:33 MSIA320MA10 systemd[2371]: Starting Sound Service...
Oct  2 07:19:33 MSIA320MA10 rtkit-daemon[518]: Successfully made thread 2484 of process 2484 (n/a) owned by '1000' high priority at nice lev
el -11.
Oct  2 07:19:33 MSIA320MA10 rtkit-daemon[518]: Supervising 1 threads of 1 processes of 1 users.
Oct  2 07:19:33 MSIA320MA10 rtkit-daemon[518]: Supervising 1 threads of 1 processes of 1 users.
Oct  2 07:19:33 MSIA320MA10 rtkit-daemon[518]: Successfully made thread 2485 of process 2484 (n/a) owned by '1000' RT at priority 5.
Oct  2 07:19:33 MSIA320MA10 rtkit-daemon[518]: Supervising 2 threads of 1 processes of 1 users.
Oct  2 07:19:33 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' reques
ted by ':1.301' (uid=1000 pid=2484 comm="/usr/bin/pulseaudio --daemonize=no ")
Oct  2 07:19:33 MSIA320MA10 systemd[2371]: Started Sound Service.
Oct  2 07:19:34 MSIA320MA10 gnome-shell[2424]: Failed to launch ibus-daemon: L’exécution du processus fils « ibus-daemon » a échoué (Aucun f
ichier ou dossier de ce type)
Oct  2 07:19:34 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='org.gnome.Shell.CalendarServer' requeste
d by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:34 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gnome.evolution.dataser
ver.Sources5' unit='evolution-source-registry.service' requested by ':1.17' (uid=1000 pid=2496 comm="/usr/lib/gnome-shell/gnome-shell-calend
ar-server ")
Oct  2 07:19:34 MSIA320MA10 systemd[2371]: Starting Evolution source registry...
Oct  2 07:19:34 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='org.gnome.OnlineAccounts' requested by '
:1.18' (uid=1000 pid=2500 comm="/usr/lib/evolution/evolution-source-registry ")
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.evolution.dataserver.So
urces5'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Evolution source registry.
Oct  2 07:19:35 MSIA320MA10 gnome-shell[2424]: g_dir_open_with_errno: assertion 'path != NULL' failed
Oct  2 07:19:35 MSIA320MA10 gnome-shell[2424]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Oct  2 07:19:35 MSIA320MA10 gnome-shell[2424]: g_dir_open_with_errno: assertion 'path != NULL' failed
Oct  2 07:19:35 MSIA320MA10 gnome-shell[2424]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.Shell.CalendarServer'
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service
' requested by ':1.235' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 systemd[1]: Starting Location Lookup Service...
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='ca.desrt.dconf' requested by ':1.10' (ui
d=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'ca.desrt.dconf'
Oct  2 07:19:35 MSIA320MA10 goa-daemon[2506]: goa-daemon version 3.30.0 starting
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='org.gnome.Identity' requested by ':1.20'
 (uid=1000 pid=2506 comm="/usr/lib/gnome-online-accounts/goa-daemon ")
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.Identity'
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.OnlineAccounts'
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.freedesktop.Telepathy.A
ccountManager' unit='telepathy-mission-control-5.service' requested by ':1.22' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Oct  2 07:19:35 MSIA320MA10 systemd[1]: Started Location Lookup Service.
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Telepathy Mission Control service...
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMo
nitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Virtual filesystem service - disk device monitor...
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Virtual filesystem service - disk device monitor.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.freedesktop.Telepathy.Account
Manager'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Telepathy Mission Control service.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonito
r' unit='gvfs-goa-volume-monitor.service' requested by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='org.freedesktop.Telepathy.Client.Vino' r
equested by ':1.23' (uid=1000 pid=2527 comm="/usr/lib/telepathy/mission-control-5 ")
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonito
r' unit='gvfs-afc-volume-monitor.service' requested by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Virtual filesystem service - Apple File Conduit monitor...
Oct  2 07:19:35 MSIA320MA10 org.freedesktop.Telepathy.Client.Vino[2390]: Unknown option --tube
Oct  2 07:19:35 MSIA320MA10 org.freedesktop.Telepathy.Client.Vino[2390]: Run 'vino-server --help' to see a full list of available command li
ne options
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activated service 'org.freedesktop.Telepathy.Client.Vino' failed:
 Process org.freedesktop.Telepathy.Client.Vino exited with status 1
Oct  2 07:19:35 MSIA320MA10 gvfs-afc-volume-monitor[2542]: Volume monitor alive
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Virtual filesystem service - Apple File Conduit monitor.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMo
nitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Virtual filesystem service - digital camera monitor...
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Virtual filesystem service - digital camera monitor.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonito
r' unit='gvfs-mtp-volume-monitor.service' requested by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gnome.evolution.dataser
ver.Calendar7' unit='evolution-calendar-factory.service' requested by ':1.17' (uid=1000 pid=2496 comm="/usr/lib/gnome-shell/gnome-shell-cale
ndar-server ")
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freed
esktop.hostname1.service' requested by ':1.346' (uid=1000 pid=2560 comm="/usr/lib/gnome-settings-daemon/gsd-rfkill ")
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Evolution calendar service...
Oct  2 07:19:35 MSIA320MA10 systemd[1]: Starting Hostname Service...
Oct  2 07:19:35 MSIA320MA10 gsd-sharing[2565]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remot
e-desktop.service not loaded.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.evolution.dataserver.Ca
lendar7'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Evolution calendar service.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gnome.evolution.dataser
ver.AddressBook9' unit='evolution-addressbook-factory.service' requested by ':1.41' (uid=1000 pid=2613 comm="/usr/lib/evolution/evolution-ca
lendar-factory ")
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Starting Evolution address book service...
Oct  2 07:19:35 MSIA320MA10 gnome-shell[2424]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.evolution.dataserver.Ad
dressBook9'
Oct  2 07:19:35 MSIA320MA10 systemd[2371]: Started Evolution address book service.
Oct  2 07:19:35 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct  2 07:19:35 MSIA320MA10 systemd[1]: Started Hostname Service.
Oct  2 07:19:35 MSIA320MA10 kernel: [  560.397868] rfkill: input handler disabled
Oct  2 07:19:36 MSIA320MA10 kernel: [  560.788924] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)
Oct  2 07:19:36 MSIA320MA10 systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice.
Oct  2 07:19:36 MSIA320MA10 systemd[1]: Started Clean the /media/dimitri/retropie mount point.
Oct  2 07:19:36 MSIA320MA10 udisksd[525]: Mounted /dev/sdc2 at /media/dimitri/retropie on behalf of uid 1000
Oct  2 07:19:36 MSIA320MA10 systemd[1]: Started Clean the /media/dimitri/boot mount point.
Oct  2 07:19:36 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedes
ktop.locale1.service' requested by ':1.412' (uid=1000 pid=2599 comm="/usr/lib/gnome-settings-daemon/gsd-keyboard ")
Oct  2 07:19:36 MSIA320MA10 systemd[1]: Starting Locale Service...
Oct  2 07:19:36 MSIA320MA10 udisksd[525]: Mounted /dev/sdc1 at /media/dimitri/boot on behalf of uid 1000
Oct  2 07:19:36 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.freedesktop.Tracker1' u
nit='tracker-store.service' requested by ':1.50' (uid=1000 pid=2766 comm="gdbus call -e -d org.freedesktop.DBus -o /org/free")
Oct  2 07:19:36 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:19:36 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='org.gnome.Shell.HotplugSniffer' requeste
d by ':1.10' (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:36 MSIA320MA10 gsd-color[704]: failed to set screen _ICC_PROFILE: L’ouverture du fichier « /home/dimitri/.local/share/icc/edid-
362f69ca4ec5318518fa76ae2ef7d616.icc » a échoué : Permission non accordée
Oct  2 07:19:36 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
Oct  2 07:19:36 MSIA320MA10 gnome-session-binary[2392]: Entering running state
Oct  2 07:19:36 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.freedesktop.Tracker1'
Oct  2 07:19:36 MSIA320MA10 tracker-store.desktop[2766]: (uint32 1,)
Oct  2 07:19:36 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:19:36 MSIA320MA10 gnome-shell[2424]: GNOME Shell started at Tue Oct 02 2018 07:19:35 GMT+0200 (CEST)
Oct  2 07:19:36 MSIA320MA10 gsd-color[704]: failed to set screen _ICC_PROFILE: L’ouverture du fichier « /home/dimitri/.local/share/icc/edid-
362f69ca4ec5318518fa76ae2ef7d616.icc » a échoué : Permission non accordée
Oct  2 07:19:36 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct  2 07:19:36 MSIA320MA10 systemd[1]: Started Locale Service.
Oct  2 07:19:40 MSIA320MA10 gnome-software[2791]: plugin appstream took 2,9 seconds to do setup
Oct  2 07:19:40 MSIA320MA10 gnome-software[2791]: enabled plugins: packagekit-url-to-app, shell-extensions, packagekit-local, fwupd, desktop
-categories, packagekit-offline, packagekit-proxy, packagekit-upgrade, os-release, packagekit, packagekit-refine-repos, systemd-updates, pac
kagekit-refresh, appstream, odrs, hardcoded-popular, desktop-menu-path, hardcoded-blacklist, steam, packagekit-refine, modalias, rewrite-res
ource, hardcoded-featured, generic-updates, packagekit-history, provenance, icons, key-colors, provenance-license, key-colors-metadata
Oct  2 07:19:40 MSIA320MA10 gnome-software[2791]: disabled plugins: dpkg, dummy, repos, epiphany
Oct  2 07:19:40 MSIA320MA10 gnome-software[2791]: not GsPlugin error from plugin fwupd FwupdError:10: The name org.freedesktop.fwupd was not
 provided by any .service files
Oct  2 07:19:40 MSIA320MA10 gnome-software[2791]: failed to call gs_plugin_refresh on fwupd: The name org.freedesktop.fwupd was not provided
 by any .service files
Oct  2 07:19:40 MSIA320MA10 gnome-software[2791]: failed to call gs_plugin_add_updates_historical on fwupd: The name org.freedesktop.fwupd w
as not provided by any .service files
Oct  2 07:19:41 MSIA320MA10 PackageKit: get-updates transaction /355_cbcdcdae from uid 1000 finished with success after 789ms
Oct  2 07:19:41 MSIA320MA10 gnome-software[2791]: failed to call gs_plugin_add_updates on fwupd: The name org.freedesktop.fwupd was not prov
ided by any .service files
Oct  2 07:19:41 MSIA320MA10 gnome-software[2791]: hiding category games featured applications: found only 0 to show, need at least 9
Oct  2 07:19:41 MSIA320MA10 gnome-software[2791]: hiding category productivity featured applications: found only 0 to show, need at least 9
Oct  2 07:19:41 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='org.gnome.Nautilus' requested by ':1.10'
 (uid=1000 pid=2424 comm="/usr/bin/gnome-shell ")
Oct  2 07:19:41 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47694 is not from a LAN
Oct  2 07:19:42 MSIA320MA10 PackageKit: resolve transaction /356_baaceeab from uid 1000 finished with success after 513ms
Oct  2 07:19:42 MSIA320MA10 gnome-shell[621]: Connection to xwayland lost
Oct  2 07:19:42 MSIA320MA10 at-spi-bus-launcher[657]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1024"
Oct  2 07:19:42 MSIA320MA10 at-spi-bus-launcher[657]:       after 21 requests (21 known processed) with 0 events remaining.
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.deskt
op' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Clipboard.desktop'
 killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' kil
led by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Datetime.desktop'
killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.deskt
op' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop'
killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Mouse.desktop' kil
led by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' kil
led by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.PrintNotifications
.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Rfkill.desktop' ki
lled by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.d
esktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' k
illed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Smartcard.desktop'
 killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Sound.desktop' kil
led by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by signal
 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Clipboard.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Datetime.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.desktop' killed by signal
 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Mouse.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.PrintNotifications.desktop' killed by
signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Rfkill.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.desktop' killed by si
gnal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Smartcard.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Sound.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop'
 killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop'
 killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gsd-smartcard[2887]: Unable to register client: GDBus.Error:org.gnome.SessionManager.NotInRunning: Unable to reg
ister client
Oct  2 07:19:42 MSIA320MA10 gsd-color[2589]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/
devices/xrandr_Iiyama_North_America_17JN1_30017892_Debian_gdm_115
Oct  2 07:19:42 MSIA320MA10 gsd-print-notif[2885]: Unable to register client: GDBus.Error:org.gnome.SessionManager.NotInRunning: Unable to r
egister client
Oct  2 07:19:42 MSIA320MA10 gsd-sharing[2894]: Unable to register client: GDBus.Error:org.gnome.SessionManager.NotInRunning: Unable to regis
ter client
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' kil
led by signal 15
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' killed by signal 15
Oct  2 07:19:42 MSIA320MA10 gsd-a11y-settin[2889]: Unable to register client: GDBus.Error:org.gnome.SessionManager.NotInRunning: Unable to r
egister client
Oct  2 07:19:42 MSIA320MA10 gnome-session[610]: gnome-session-binary[610]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct  2 07:19:42 MSIA320MA10 gnome-session-binary[610]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Oct  2 07:19:42 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47694 is not from a LAN
Oct  2 07:19:42 MSIA320MA10 systemd[1]: user-runtime-dir@115.service: Unit not needed anymore. Stopping.
Oct  2 07:19:42 MSIA320MA10 systemd[1]: Stopping User Manager for UID 115...
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopping D-Bus User Message Bus...
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped target Default.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopping Accessibility services bus...
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopping Sound Service...
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped D-Bus User Message Bus.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped Accessibility services bus.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped Sound Service.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped target Basic System.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped target Timers.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped target Paths.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Stopped target Sockets.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Closed GnuPG cryptographic agent and passphrase cache.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Closed D-Bus User Message Bus Socket.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Closed GnuPG network certificate management daemon.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Closed Sound System.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Reached target Shutdown.
Oct  2 07:19:42 MSIA320MA10 systemd[595]: Starting Exit the Session...
Oct  2 07:19:42 MSIA320MA10 systemd[1]: user-runtime-dir@115.service: Unit not needed anymore. Stopping.
Oct  2 07:19:42 MSIA320MA10 systemd[1]: Stopped User Manager for UID 115.
Oct  2 07:19:42 MSIA320MA10 systemd[1]: user-runtime-dir@115.service: Unit not needed anymore. Stopping.
Oct  2 07:19:42 MSIA320MA10 systemd[1]: Removed slice User Slice of UID 115.
Oct  2 07:19:42 MSIA320MA10 systemd[1]: Stopping /run/user/115 mount wrapper...
Oct  2 07:19:42 MSIA320MA10 gdm3: Child process -606 was already dead.
Oct  2 07:19:42 MSIA320MA10 systemd[1]: Stopped /run/user/115 mount wrapper.
Oct  2 07:19:42 MSIA320MA10 PackageKit: resolve transaction /357_aaebdabe from uid 1000 finished with success after 577ms
Oct  2 07:19:42 MSIA320MA10 gnome-software[2791]: Only 8 apps for popular list, hiding
Oct  2 07:19:43 MSIA320MA10 PackageKit: resolve transaction /358_adcdcedd from uid 1000 finished with success after 557ms
Oct  2 07:19:43 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47694 is not from a LAN
Oct  2 07:19:43 MSIA320MA10 PackageKit: resolve transaction /359_bcceaccc from uid 1000 finished with success after 564ms
Oct  2 07:19:44 MSIA320MA10 PackageKit: search-file transaction /360_cdbabbce from uid 1000 finished with success after 583ms
Oct  2 07:19:44 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:47694 is not from a LAN
Oct  2 07:19:45 MSIA320MA10 PackageKit: search-file transaction /361_edeccede from uid 1000 finished with success after 600ms
Oct  2 07:19:46 MSIA320MA10 PackageKit: search-file transaction /362_ededeaea from uid 1000 finished with success after 610ms
Oct  2 07:19:46 MSIA320MA10 PackageKit: search-file transaction /363_ddedabce from uid 1000 finished with success after 610ms
Oct  2 07:19:47 MSIA320MA10 PackageKit: search-file transaction /364_cdadebec from uid 1000 finished with success after 593ms
Oct  2 07:19:48 MSIA320MA10 PackageKit: get-details transaction /365_bdaadbbc from uid 1000 finished with success after 546ms
Oct  2 07:19:58 MSIA320MA10 pulseaudio[2484]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply:
 Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken.
Oct  2 07:20:45 MSIA320MA10 gnome-software[2791]: not GsPlugin error from plugin fwupd FwupdError:10: The name org.freedesktop.fwupd was not
 provided by any .service files
Oct  2 07:20:45 MSIA320MA10 gnome-software[2791]: failed to call gs_plugin_refresh on fwupd: The name org.freedesktop.fwupd was not provided
 by any .service files
Oct  2 07:20:46 MSIA320MA10 PackageKit: get-updates transaction /366_adedabaa from uid 1000 finished with success after 715ms
Oct  2 07:20:48 MSIA320MA10 gnome-software[2791]: failed to call gs_plugin_add_updates on fwupd: The name org.freedesktop.fwupd was not prov
ided by any .service files
Oct  2 07:21:19 MSIA320MA10 tracker-store[2776]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:21:19 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:21:19 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:21:19 MSIA320MA10 nautilus[2871]: Error on getting connection: Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBus.Err
or.NoReply: Message recipient disconnected from message bus without replying
Oct  2 07:21:19 MSIA320MA10 tracker-extract[2770]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' faile
d
Oct  2 07:21:19 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.freedesktop.Tracker1' u
nit='tracker-store.service' requested by ':1.59' (uid=1000 pid=2871 comm="/usr/bin/nautilus --gapplication-service ")
Oct  2 07:21:19 MSIA320MA10 tracker-extract[2770]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct  2 07:21:19 MSIA320MA10 tracker-extract[2770]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct  2 07:21:19 MSIA320MA10 tracker-extract[2770]: Could not create notifier: Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBu
s.Error.NoReply: Message recipient disconnected from message bus without replying
Oct  2 07:21:19 MSIA320MA10 tracker-extract[2770]: invalid (NULL) pointer instance
Oct  2 07:21:19 MSIA320MA10 tracker-extract[2770]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Oct  2 07:21:19 MSIA320MA10 [2769]: Couldn't create new applications miner, 'Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBus
.Error.NoReply: Message recipient disconnected from message bus without replying'
Oct  2 07:21:19 MSIA320MA10 tracker-miner-f[2765]: Couldn't create new Files miner: 'Failed to load SPARQL backend: GDBus.Error:org.freedesk
top.DBus.Error.NoReply: Message recipient disconnected from message bus without replying'
Oct  2 07:21:19 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:21:19 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 1.
Oct  2 07:21:19 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:21:19 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:21:19 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.freedesktop.Tracker1'
Oct  2 07:21:19 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:21:37 MSIA320MA10 tracker-store[2948]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:21:37 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:21:37 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:21:37 MSIA320MA10 nautilus[2871]: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct  2 07:21:37 MSIA320MA10 nautilus[2871]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct  2 07:21:37 MSIA320MA10 nautilus[2871]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct  2 07:21:37 MSIA320MA10 nautilus[2871]: invalid (NULL) pointer instance
Oct  2 07:21:37 MSIA320MA10 nautilus[2871]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Oct  2 07:21:37 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.Nautilus'
Oct  2 07:21:37 MSIA320MA10 tracker-extract[2770]: Could not start decorator: Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBu
s.Error.NoReply: Message recipient disconnected from message bus without replying
Oct  2 07:21:37 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:21:37 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 2.
Oct  2 07:21:37 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:21:37 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:21:37 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:21:38 MSIA320MA10 dbus-daemon[521]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freed
esktop.hostname1.service' requested by ':1.534' (uid=1000 pid=2871 comm="/usr/bin/nautilus --gapplication-service ")
Oct  2 07:21:38 MSIA320MA10 systemd[1]: Starting Hostname Service...
Oct  2 07:21:38 MSIA320MA10 dbus-daemon[521]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct  2 07:21:38 MSIA320MA10 systemd[1]: Started Hostname Service.
Oct  2 07:21:41 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60263 is not from a LAN
Oct  2 07:21:42 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating via systemd: service name='org.gtk.vfs.Metadata' unit=
'gvfs-metadata.service' requested by ':1.59' (uid=1000 pid=2871 comm="/usr/bin/nautilus --gapplication-service ")
Oct  2 07:21:42 MSIA320MA10 systemd[2371]: Starting Virtual filesystem metadata service...
Oct  2 07:21:42 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gtk.vfs.Metadata'
Oct  2 07:21:42 MSIA320MA10 systemd[2371]: Started Virtual filesystem metadata service.
Oct  2 07:21:42 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60263 is not from a LAN
Oct  2 07:21:43 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60263 is not from a LAN
Oct  2 07:21:44 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:60263 is not from a LAN
Oct  2 07:21:55 MSIA320MA10 tracker-store[2961]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:21:55 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:21:55 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:21:55 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:21:55 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 3.
Oct  2 07:21:55 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:21:55 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:21:55 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:22:13 MSIA320MA10 tracker-store[2988]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:22:13 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:22:13 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:22:13 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:22:13 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 4.
Oct  2 07:22:13 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:22:13 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:22:13 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:22:22 MSIA320MA10 nautilus[2871]: ../../../../../gdk/wayland/gdkselection-wayland.c:261: error reading selection buffer: L’opérati
on a été annulée
Oct  2 07:22:29 MSIA320MA10 org.gnome.Shell.desktop[2424]: libinput error: client bug: timer event11 debounce short: offset negative (-0ms)
Oct  2 07:22:29 MSIA320MA10 firefox-esr[3021]: Theme parsing error: <data>:1:34: Expected ')' in color definition
Oct  2 07:22:29 MSIA320MA10 firefox-esr[3021]: Theme parsing error: <data>:1:77: Expected ')' in color definition
Oct  2 07:22:32 MSIA320MA10 tracker-store[3007]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:22:32 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:22:32 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:22:32 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:22:32 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 5.
Oct  2 07:22:32 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:22:32 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:22:32 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:22:51 MSIA320MA10 tracker-store[3179]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:22:51 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:22:51 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:22:51 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:22:51 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 6.
Oct  2 07:22:51 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:22:51 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:22:51 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:23:09 MSIA320MA10 tracker-store[3221]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:23:09 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:23:09 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:23:10 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:23:10 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 7.
Oct  2 07:23:10 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:23:10 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:23:10 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:23:17 MSIA320MA10 nautilus[2871]: ../../../../../gdk/wayland/gdkselection-wayland.c:261: error reading selection buffer: L’opérati
on a été annulée
Oct  2 07:23:17 MSIA320MA10 nautilus[2871]: ../../../../../gdk/wayland/gdkselection-wayland.c:261: error reading selection buffer: L’opérati
on a été annulée
Oct  2 07:23:17 MSIA320MA10 nautilus[2871]: ../../../../../gdk/wayland/gdkselection-wayland.c:261: error reading selection buffer: L’opérati
on a été annulée
Oct  2 07:23:19 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Activating service name='org.gnome.gedit' requested by ':1.59' (u
id=1000 pid=2871 comm="/usr/bin/nautilus --gapplication-service ")
Oct  2 07:23:19 MSIA320MA10 dbus-daemon[2390]: [session uid=1000 pid=2390] Successfully activated service 'org.gnome.gedit'
Oct  2 07:23:28 MSIA320MA10 tracker-store[3230]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:23:28 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:23:28 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:23:28 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:23:28 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 8.
Oct  2 07:23:28 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:23:28 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:23:28 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:23:31 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: last_user_time (796446) is greater than comparison timest
amp (796443).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to w
ork around...
Oct  2 07:23:31 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: 0x1800010 (Linux Mint) appears to be one of the offending
 windows with a timestamp of 796446.  Working around...
Oct  2 07:23:32 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: last_user_time (796476) is greater than comparison timest
amp (796474).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to w
ork around...
Oct  2 07:23:32 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: 0x1800010 (Linux Mint) appears to be one of the offending
 windows with a timestamp of 796476.  Working around...
Oct  2 07:23:32 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: last_user_time (796506) is greater than comparison timest
amp (796504).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to w
ork around...
Oct  2 07:23:32 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: 0x1800010 (Linux Mint) appears to be one of the offending
 windows with a timestamp of 796506.  Working around...
Oct  2 07:23:32 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: last_user_time (796566) is greater than comparison timest
amp (796565).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to w
ork around...
Oct  2 07:23:32 MSIA320MA10 org.gnome.Shell.desktop[2424]: Window manager warning: 0x1800010 (Linux Mint) appears to be one of the offending
 windows with a timestamp of 796566.  Working around...
Oct  2 07:23:41 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:51539 is not from a LAN
Oct  2 07:23:42 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:51539 is not from a LAN
Oct  2 07:23:43 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:51539 is not from a LAN
Oct  2 07:23:44 MSIA320MA10 minissdpd[880]: peer 192.168.0.14:51539 is not from a LAN
Oct  2 07:23:46 MSIA320MA10 tracker-store[3256]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:23:47 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:23:47 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:23:47 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:23:47 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 9.
Oct  2 07:23:47 MSIA320MA10 systemd[2371]: Stopped Tracker metadata database store and lookup manager.
Oct  2 07:23:47 MSIA320MA10 systemd[2371]: Starting Tracker metadata database store and lookup manager...
Oct  2 07:23:47 MSIA320MA10 systemd[2371]: Started Tracker metadata database store and lookup manager.
Oct  2 07:24:04 MSIA320MA10 tracker-store[3264]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Oct  2 07:24:04 MSIA320MA10 systemd[2371]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Oct  2 07:24:04 MSIA320MA10 systemd[2371]: tracker-store.service: Failed with result 'exit-code'.
Oct  2 07:24:05 MSIA320MA10 systemd[2371]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 07:24:05 MSIA320MA10 systemd[2371]: tracker-store.service: Scheduled restart job, restart counter is at 10.
 

zcat /var/log/syslog.2.gz | more

Sep 30 00:00:06 MSIA320MA10 rsyslogd:  [origin software="rsyslogd" swVersion="8.38.0" x-pid="524" x-info="http://www.rsyslog.com"] rsyslogd
was HUPed
Sep 30 00:00:06 MSIA320MA10 rsyslogd:  [origin software="rsyslogd" swVersion="8.38.0" x-pid="524" x-info="http://www.rsyslog.com"] rsyslogd
was HUPed
Sep 30 00:00:06 MSIA320MA10 systemd[1]: Started Rotate log files.
Sep 30 00:00:24 MSIA320MA10 tracker-store[2946]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Sep 30 00:00:24 MSIA320MA10 systemd[1184]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Sep 30 00:00:24 MSIA320MA10 systemd[1184]: tracker-store.service: Failed with result 'exit-code'.
Sep 30 00:00:24 MSIA320MA10 systemd[1184]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Sep 30 00:00:24 MSIA320MA10 systemd[1184]: tracker-store.service: Scheduled restart job, restart counter is at 82.
Sep 30 00:00:24 MSIA320MA10 systemd[1184]: Stopped Tracker metadata database store and lookup manager.
Sep 30 00:00:24 MSIA320MA10 systemd[1184]: Starting Tracker metadata database store and lookup manager...
Sep 30 00:00:24 MSIA320MA10 systemd[1184]: Started Tracker metadata database store and lookup manager.
Sep 30 00:00:42 MSIA320MA10 tracker-store[2963]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElem
ent_nie:keyword_TEMP (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type)
Sep 30 00:00:42 MSIA320MA10 systemd[1184]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
Sep 30 00:00:42 MSIA320MA10 systemd[1184]: tracker-store.service: Failed with result 'exit-code'.
Sep 30 00:00:43 MSIA320MA10 systemd[1184]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart.
Sep 30 00:00:43 MSIA320MA10 systemd[1184]: tracker-store.service: Scheduled restart job, restart counter is at 83.
Sep 30 00:00:43 MSIA320MA10 systemd[1184]: Stopped Tracker metadata database store and lookup manager.
Sep 30 00:00:43 MSIA320MA10 systemd[1184]: Starting Tracker metadata database store and lookup manager...
Sep 30 00:00:43 MSIA320MA10 systemd[1184]: Started Tracker metadata database store and lookup manager.
Sep 30 00:01:00 MSIA320MA10 tracker-store[2971]: Cannot initialize database: error in view fts_view: no such ta

Ça me parait cohérent comme explication, cependant, comment retirer toute ces écritures sur le syslog?
Merci d'avance!

Dernière modification par Anonyme-11 (03-10-2018 08:47:31)

raleur

Membre

Inscription : 03-10-2014

Re : [résolu]Kern.log et sys.log de plusieurs Go

Je pense que la taille de mon kern.log n'a pas de rapport avec mon sys.log

Sans connaître au moins les tailles de ces fichiers, on ne pourra pas te le confirmer.
Les messages du noyau sont enregistrés à la fois dans kern.log, syslog et messages. Si ces trois fichiers ont des tailles similaires et plusieurs ordre de grandeur supérieures à leurs tailles normales, alors on peut en déduire sans grand risque de se tromper qu'ils contiennent les même messages répétitifs qui proviennent du noyau. Sinon, c'est autre chose.

Premièrement, je pense avoir fait une mauvaise utilisation de ces commande:

Cet ensemble de commandes manque de cohérence.
La première monte une image ISO IMAGE.iso sur le répertoire REPERTOIRE, tous deux situés dans le répertoire courant.
La seconde démonte l'image /home/jeff/toto.iso et non IMAGE.iso.
La troisième supprime le répertoire /home/jeff/toto et non REPERTOIRE.

Sauf erreur de ma part, je n'ai pas utiliser la commande rmmod loop.

Ce n'était pas utile mais pas bien grave. Le module loop peut être rechargé avec modprobe. En aucun cas cela ne peut avoir causé les messages d'erreur du noyau. Si le module avait encore été en cours d'utilisation, le déchargement aurait échoué.
Les messages d'erreur rapportent une tentative d'accès au-delà de la fin de l'image, ce qui pourrait indiquer que l'image ISO est corrompue ou tronquée.

Je suppose que les messages ont dû s'arrêter après que tu as démonté l'image ?

Deuxièmement, j'ai remarqué dans mon fichier syslog, qu'un service redémarre constamment!

Je suppose que tu veux parler de tracker-store.service ? Je ne connais pas du tout ce service.

comment retirer toute ces écritures sur le syslog?

Pour les anciens fichiers log (.1, .*.gz) il suffit de les supprimer.
Pour les fichiers logs courants qui sont ouverts, les supprimer ne libèrera l'espace qu'ils occupent que lorsqu'ils seront fermés (arrêt ou redémarrage de rsyslogd). On peut les vider en remplaçant leur contenu par rien ou pas grand-chose.

echo "vidé par l'admin" > /var/log/sylog

Dernière modification par raleur (02-10-2018 16:56:11)

---

Il vaut mieux montrer que raconter.

Anonyme-11

Invité

Re : [résolu]Kern.log et sys.log de plusieurs Go

Cet ensemble de commandes manque de cohérence.
La première monte une image ISO IMAGE.iso sur le répertoire REPERTOIRE, tous deux situés dans le répertoire courant.
La seconde démonte l'image /home/jeff/toto.iso et non IMAGE.iso.
La troisième supprime le répertoire /home/jeff/toto et non REPERTOIRE.

En fait, si, elles sont tout a fait cohérentes.
Mais ce sont les commandes telle que montré dans le tuto dont je me suis servi.
Bien sur, je remplace par le chemin de mon point de montage, et je désigne mon iso a chaque fois.
En réalité, ce que je tape comme commande ressemble a ca :

mount -t iso9660 /home/dimitri/Documents/Iso/rl.iso /home/dimitri/Documents/Iso/point-montage -o ro
umount /home/dimitri/Documents/Iso/rl.iso
rmdir /home/dimitri/Documents/Iso/point-montage
rmmod loop

Dernière modification par Anonyme-11 (02-10-2018 17:05:21)

Anonyme-11

Invité

Re : [résolu]Kern.log et sys.log de plusieurs Go

https://www.linux.com/forums/system-man … nating-cpu

By what I have found at https://admin.fedoraproject.org/pkgdb/applications , tracker-store is Metadata database store and lookup manager. So that means that it is utilizing more resources now to index the files on your computer for a quick lookup. Depending on the amount of hdd space you have and the quantity of files it may take quite a while to complete, but it should throttle down once the initial index database has been created.

D'après ce que j'ai trouvé sur https://admin.fedoraproject.org/pkgdb/applications, tracker-store est un magasin de base de données de métadonnées et un gestionnaire de recherche. Cela signifie donc qu’il utilise plus de ressources maintenant pour indexer les fichiers sur votre ordinateur pour une recherche rapide. En fonction de la quantité d'espace disque disponible et de la quantité de fichiers, son achèvement peut prendre un certain temps, mais il devrait être réduit une fois que la base de données d'index initiale a été créée.

Dernière modification par Anonyme-11 (02-10-2018 17:21:02)

raleur

Membre

Inscription : 03-10-2014

Re : [résolu]Kern.log et sys.log de plusieurs Go

tracker-store.service fait partie du paquet "tracker", mais je n'en sais pas plus. Il n'est pas installé sur mes machines.

---

Il vaut mieux montrer que raconter.

Anonyme-11

Invité

Re : [résolu]Kern.log et sys.log de plusieurs Go

tracker-store.service fait partie du paquet "tracker", mais je n'en sais pas plus. Il n'est pas installé sur mes machines.

Pour être franc, j'ai supprimé le problème à la source avec :

apt-get remove tracker

Je n'aime pas ce genre de méthode, mais mon ordinateur ne s'en porte que mieux.
Ça réglé le problème du sys.log.