[1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

winux · Le 24/04/2019, à 20:02

Je pense que les réponses vont être décevantes car fort de ta commande

sudo rm -v /var/crash/*

comme l'erreur logiciel était revenue, je l'ai virée pour le prochain démarrage.

A chacune de tes commandes, j'ai eu le message "aucun fichier ou dossier de ce type"
Voici l'ensemble

gerard@PC-MSI:~$ /usr/share/apport/apport-gtk -c /var/crash/_usr_bin_pcmanfm.1000.crash

(apport-gtk:1539): dbind-WARNING **: 20:43:38.022: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Gtk-Message: 20:43:39.735: GtkDialog mapped without a transient parent. This is discouraged.
gerard@PC-MSI:~$ /usr/share/apport/apport-gtk -c /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash

(apport-gtk:1547): dbind-WARNING **: 20:43:57.830: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Gtk-Message: 20:43:59.553: GtkDialog mapped without a transient parent. This is discouraged.
gerard@PC-MSI:~$ /usr/share/apport/apport-gtk -c /var/crash/_sbin_plymouthd.0.crash

(apport-gtk:1551): dbind-WARNING **: 20:44:20.475: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Gtk-Message: 20:44:22.208: GtkDialog mapped without a transient parent. This is discouraged.

nany · Le 24/04/2019, à 20:12

Pas grave.

winux · Le 24/04/2019, à 21:36

je vais attendre le prochain passage de l'erreur logicielle, en principe à la prochaine mise à jour.
Passe une bonne nuit

winux · Le 25/04/2019, à 09:36

Bonjour nany
Ca y est après une mise à jour logicielle, l'erreur logiciel est revenue, je puis donc retenter tes commandes avec je l'espère plus de succès ! en fait bof !

gerard@PC-MSI:~$ /usr/share/apport/apport-gtk -c /var/crash/_usr_bin_pcmanfm.1000.crash
(apport-gtk:1404): dbind-WARNING **: 10:27:06.137: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Gtk-Message: 10:27:08.037: GtkDialog mapped without a transient parent. This is discouraged.

gerard@PC-MSI:~$ /usr/share/apport/apport-gtk -c /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
(apport-gtk:1409): dbind-WARNING **: 10:27:47.533: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Gtk-Message: 10:27:49.250: GtkDialog mapped without a transient parent. This is discouraged.

gerard@PC-MSI:~$ sudo /usr/share/apport/apport-gtk -c /var/crash/_sbin_plymouthd.0.crash
[sudo] Mot de passe de gerard : 
(apport-gtk:1415): dbind-WARNING **: 10:28:19.688: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

Le 3e a généré la fenêtre

Désolé, Ubuntu 18.04 a rencontré une erreur interne

Voilà, cette fois je ne prends aucune initiative en termes de ligne de commande, j'attends le diagnostic préalable du médecin !!

nany · Le 25/04/2019, à 11:09

On laisse tomber les deux premières commandes qui n’étaient valables qu’avec la présence des rapports.

En revanche, comme prévu, plymouth a réapparu.

winux a écrit :

Le 3e a généré la fenêtre
Désolé, Ubuntu 18.04 a rencontré une erreur interne

Dans cette fenêtre, il y a certainement le bouton Afficher les détails. Clique dessus pour voir ci cette fois-ci ça affiche quelque chose et, si oui, montre le résultat.

ylag · Le 25/04/2019, à 11:33

Salut,

Je ne sais si c'est pertinent sous Lubuntu, mais concernant les messages d'erreurs du type de:

The name org.a11y.Bus was not provided by any .service files

...il semblerait que l'installation du paquet at-spi2-core (si pas déjà présent) puisse aider à la résolution du problème.

Voir ces discussions (en anglais, par contre...) à ce sujet:
[solved ]Warning **: Error retrieving accessibility bus address

bug#28088: "The name org.a11y.Bus was not provided by any .service files

A+

Dernière modification par ylag (Le 25/04/2019, à 11:34)

nany · Le 25/04/2019, à 12:25

ylag a écrit :

Je ne sais si c'est pertinent sous Lubuntu

Je ne sais pas non plus. A priori, je dirais que non mais je garde tes liens sous le coude au cas où.

winux · Le 25/04/2019, à 14:21

J'ai relancé ta commande, mais afficher les détails n'a rien donné, juste une fenêtre qui s'ouvre 1/10e de seconde et se referme. Cette piste va être difficilement exploitable, désolé.

nany · Le 25/04/2019, à 19:41

Bien, puisque cette ficelle ne donne rien, on va essayer d’en tirer d’autres. Commence par donner les retours de :

sudo grep -i "plymouth" /var/log/boot.log

grep -i "plymouth" /var/log/kern.log

winux · Le 25/04/2019, à 20:45

Voilà voilà
Beaucoup plus bavard cette fois,

gerard@PC-MSI:~$ sudo grep -i "plymouth" /var/log/boot.log
[sudo] Mot de passe de gerard : 
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
gerard@PC-MSI:~$ grep -i "plymouth" /var/log/kern.log
gerard@PC-MSI:~$

Dernière modification par winux (Le 25/04/2019, à 20:48)

nany · Le 26/04/2019, à 15:18

Bon, continuons de tirer les ficelles. Donne le retour de :

cat /var/log/syslog

winux · Le 26/04/2019, à 16:56

Ah cette fois il y a de quoi lire !!
Au passage, j'ai vu ta photo dans Télé-7jours avec pour titre de l'émission Nanny avec 2 n !! Tu es partout !!
Bref, revenons aux choses sérieuses

Apr 26 17:38:21 PC-MSI kernel: [    1.790117] NET: Registered protocol family 10
Apr 26 17:38:21 PC-MSI kernel: [    1.804843] Segment Routing with IPv6
Apr 26 17:38:21 PC-MSI kernel: [    1.804917] NET: Registered protocol family 17
Apr 26 17:38:21 PC-MSI kernel: [    1.805082] Key type dns_resolver registered
Apr 26 17:38:21 PC-MSI kernel: [    1.805992] RAS: Correctable Errors collector initialized.
Apr 26 17:38:21 PC-MSI kernel: [    1.806089] microcode: sig=0x106ca, pf=0x4, revision=0x107
Apr 26 17:38:21 PC-MSI kernel: [    1.806250] microcode: Microcode Update Driver: v2.2.
Apr 26 17:38:21 PC-MSI kernel: [    1.806763] registered taskstats version 1
Apr 26 17:38:21 PC-MSI kernel: [    1.806792] Loading compiled-in X.509 certificates
Apr 26 17:38:21 PC-MSI kernel: [    1.811319] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
Apr 26 17:38:21 PC-MSI kernel: [    1.819567] random: fast init done
Apr 26 17:38:21 PC-MSI kernel: [    1.819730] Loaded X.509 cert 'Build time autogenerated kernel key: e7056c016f846647db0f624c10ce588fee742707'
Apr 26 17:38:21 PC-MSI kernel: [    1.819810] zswap: loaded using pool lzo/zbud
Apr 26 17:38:21 PC-MSI kernel: [    1.832443] ACPI: Battery Slot [BAT1] (battery present)
Apr 26 17:38:21 PC-MSI kernel: [    1.836940] Key type big_key registered
Apr 26 17:38:21 PC-MSI kernel: [    1.836952] Key type trusted registered
Apr 26 17:38:21 PC-MSI kernel: [    1.843371] Key type encrypted registered
Apr 26 17:38:21 PC-MSI kernel: [    1.843384] AppArmor: AppArmor sha1 policy hashing enabled
Apr 26 17:38:21 PC-MSI kernel: [    1.843390] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
Apr 26 17:38:21 PC-MSI kernel: [    1.843406] ima: Allocated hash algorithm: sha1
Apr 26 17:38:21 PC-MSI kernel: [    1.843465] evm: HMAC attrs: 0x1
Apr 26 17:38:21 PC-MSI kernel: [    1.844160]   Magic number: 15:114:640
Apr 26 17:38:21 PC-MSI kernel: [    1.844460] rtc_cmos 00:02: setting system clock to 2019-04-26 15:38:13 UTC (1556293093)
Apr 26 17:38:21 PC-MSI kernel: [    1.845816] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Apr 26 17:38:21 PC-MSI kernel: [    1.845819] EDD information not available.
Apr 26 17:38:21 PC-MSI kernel: [    1.856265] Freeing unused kernel image memory: 2408K
Apr 26 17:38:21 PC-MSI kernel: [    1.872166] Write protecting the kernel read-only data: 20480k
Apr 26 17:38:21 PC-MSI kernel: [    1.874598] Freeing unused kernel image memory: 2008K
Apr 26 17:38:21 PC-MSI kernel: [    1.876413] Freeing unused kernel image memory: 1868K
Apr 26 17:38:21 PC-MSI kernel: [    1.909053] x86/mm: Checked W+X mappings: passed, no W+X pages found.
Apr 26 17:38:21 PC-MSI kernel: [    1.956704] random: systemd-udevd: uninitialized urandom read (16 bytes read)
Apr 26 17:38:21 PC-MSI systemd[1]: Starting Network Manager...
Apr 26 17:38:21 PC-MSI kernel: [    1.957349] random: systemd-udevd: uninitialized urandom read (16 bytes read)
Apr 26 17:38:21 PC-MSI kernel: [    1.957391] random: systemd-udevd: uninitialized urandom read (16 bytes read)
Apr 26 17:38:21 PC-MSI kernel: [    2.300096] usb 5-2: new full-speed USB device number 2 using uhci_hcd
Apr 26 17:38:21 PC-MSI kernel: [    2.409717] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Apr 26 17:38:21 PC-MSI kernel: [    2.410911] r8169 0000:02:00.0 eth0: RTL8102e at 0x        (ptrval), 40:61:86:1b:5e:b6, XID 04c00000 IRQ 26
Apr 26 17:38:21 PC-MSI kernel: [    2.425446] ahci 0000:00:1f.2: version 3.0
Apr 26 17:38:21 PC-MSI kernel: [    2.425940] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
Apr 26 17:38:21 PC-MSI kernel: [    2.425948] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
Apr 26 17:38:21 PC-MSI kernel: [    2.432788] scsi host0: ahci
Apr 26 17:38:21 PC-MSI kernel: [    2.436865] scsi host1: ahci
Apr 26 17:38:21 PC-MSI kernel: [    2.437478] scsi host2: ahci
Apr 26 17:38:21 PC-MSI kernel: [    2.438104] scsi host3: ahci
Apr 26 17:38:21 PC-MSI kernel: [    2.438383] ata1: SATA max UDMA/133 abar m1024@0xfeb04000 port 0xfeb04100 irq 27
Apr 26 17:38:21 PC-MSI kernel: [    2.438390] ata2: SATA max UDMA/133 abar m1024@0xfeb04000 port 0xfeb04180 irq 27
Apr 26 17:38:21 PC-MSI kernel: [    2.438397] ata3: SATA max UDMA/133 abar m1024@0xfeb04000 port 0xfeb04200 irq 27
Apr 26 17:38:21 PC-MSI kernel: [    2.438403] ata4: SATA max UDMA/133 abar m1024@0xfeb04000 port 0xfeb04280 irq 27
Apr 26 17:38:21 PC-MSI kernel: [    2.506140] usb 5-2: New USB device found, idVendor=046d, idProduct=c52f
Apr 26 17:38:21 PC-MSI kernel: [    2.506148] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 26 17:38:21 PC-MSI kernel: [    2.506153] usb 5-2: Product: USB Receiver
Apr 26 17:38:21 PC-MSI kernel: [    2.506158] usb 5-2: Manufacturer: Logitech
Apr 26 17:38:21 PC-MSI kernel: [    2.586770] r8169 0000:02:00.0 enp2s0: renamed from eth0
Apr 26 17:38:21 PC-MSI kernel: [    2.611423] hidraw: raw HID events driver (C) Jiri Kosina
Apr 26 17:38:21 PC-MSI kernel: [    2.629701] usbcore: registered new interface driver usbhid
Apr 26 17:38:21 PC-MSI kernel: [    2.629705] usbhid: USB HID core driver
Apr 26 17:38:21 PC-MSI kernel: [    2.642370] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/0003:046D:C52F.0001/input/input7
Apr 26 17:38:21 PC-MSI kernel: [    2.643668] hid-generic 0003:046D:C52F.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.3-2/input0
Apr 26 17:38:21 PC-MSI kernel: [    2.645100] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/0003:046D:C52F.0002/input/input8
Apr 26 17:38:21 PC-MSI kernel: [    2.705559] hid-generic 0003:046D:C52F.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.3-2/input1
Apr 26 17:38:21 PC-MSI kernel: [    2.716257] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x18bab35c2cc, max_idle_ns: 440795238627 ns
Apr 26 17:38:21 PC-MSI kernel: [    2.748674] ata3: SATA link down (SStatus 0 SControl 300)
Apr 26 17:38:21 PC-MSI kernel: [    2.749454] ata2: SATA link down (SStatus 0 SControl 300)
Apr 26 17:38:21 PC-MSI kernel: [    2.749547] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 26 17:38:21 PC-MSI kernel: [    2.749947] ata1.00: ATA-9: SanDisk SSD PLUS 120GB, UE4500RL, max UDMA/133
Apr 26 17:38:21 PC-MSI kernel: [    2.749954] ata1.00: 234455040 sectors, multi 1: LBA48 NCQ (depth 31/32)
Apr 26 17:38:21 PC-MSI kernel: [    2.755018] ata1.00: configured for UDMA/133
Apr 26 17:38:21 PC-MSI kernel: [    2.755570] scsi 0:0:0:0: Direct-Access     ATA      SanDisk SSD PLUS 00RL PQ: 0 ANSI: 5
Apr 26 17:38:21 PC-MSI kernel: [    2.756547] ata4: SATA link down (SStatus 0 SControl 300)
Apr 26 17:38:21 PC-MSI kernel: [    2.756730] sd 0:0:0:0: Attached scsi generic sg0 type 0
Apr 26 17:38:21 PC-MSI kernel: [    2.757534] sd 0:0:0:0: [sda] 234455040 512-byte logical blocks: (120 GB/112 GiB)
Apr 26 17:38:21 PC-MSI kernel: [    2.757600] sd 0:0:0:0: [sda] Write Protect is off
Apr 26 17:38:21 PC-MSI kernel: [    2.757607] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Apr 26 17:38:21 PC-MSI kernel: [    2.757742] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 26 17:38:21 PC-MSI kernel: [    2.760060]  sda: sda1 sda2 sda3 sda4 < sda5 >
Apr 26 17:38:21 PC-MSI kernel: [    2.761891] sd 0:0:0:0: [sda] Attached SCSI disk
Apr 26 17:38:21 PC-MSI kernel: [    3.164381] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
Apr 26 17:38:21 PC-MSI kernel: [    3.169812] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Apr 26 17:38:21 PC-MSI kernel: [    3.639016] psmouse serio1: sentelic: Finger Sensing Pad, hw: 12.1.1, sn: 0, sw: 1.1.0-K
Apr 26 17:38:21 PC-MSI kernel: [    3.644951] ip_tables: (C) 2000-2006 Netfilter Core Team
Apr 26 17:38:21 PC-MSI kernel: [    3.686107] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
Apr 26 17:38:21 PC-MSI kernel: [    3.704351] systemd[1]: Detected architecture x86-64.
Apr 26 17:38:21 PC-MSI kernel: [    3.711719] systemd[1]: Set hostname to <PC-MSI>.
Apr 26 17:38:21 PC-MSI kernel: [    4.526124] input: FSPPS/2 Sentelic FingerSensingPad as /devices/platform/i8042/serio1/input/input6
Apr 26 17:38:21 PC-MSI kernel: [    5.252455] systemd[1]: Created slice System Slice.
Apr 26 17:38:21 PC-MSI kernel: [    5.253064] systemd[1]: Listening on udev Control Socket.
Apr 26 17:38:21 PC-MSI kernel: [    5.253604] systemd[1]: Listening on Journal Audit Socket.
Apr 26 17:38:21 PC-MSI kernel: [    5.254294] systemd[1]: Created slice User and Session Slice.
Apr 26 17:38:21 PC-MSI kernel: [    5.254366] systemd[1]: Reached target Slices.
Apr 26 17:38:21 PC-MSI kernel: [    5.254997] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Apr 26 17:38:21 PC-MSI kernel: [    5.255326] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Apr 26 17:38:21 PC-MSI kernel: [    5.318614] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
Apr 26 17:38:21 PC-MSI kernel: [    5.508916] lp: driver loaded but no devices found
Apr 26 17:38:21 PC-MSI kernel: [    5.567060] ppdev: user-space parallel port driver
Apr 26 17:38:21 PC-MSI kernel: [    6.226064] systemd-journald[246]: Received request to flush runtime journal from PID 1
Apr 26 17:38:21 PC-MSI kernel: [    7.074028] audit: type=1400 audit(1556293098.724:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=336 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.074050] audit: type=1400 audit(1556293098.724:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=336 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.074062] audit: type=1400 audit(1556293098.724:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=336 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.074076] audit: type=1400 audit(1556293098.724:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=336 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.091357] audit: type=1400 audit(1556293098.740:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=335 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.091376] audit: type=1400 audit(1556293098.740:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=335 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.168189] audit: type=1400 audit(1556293098.816:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=339 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.168209] audit: type=1400 audit(1556293098.820:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=339 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.168221] audit: type=1400 audit(1556293098.820:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=339 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    7.221376] audit: type=1400 audit(1556293098.872:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=341 comm="apparmor_parser"
Apr 26 17:38:21 PC-MSI kernel: [    8.271495] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Apr 26 17:38:21 PC-MSI kernel: [    8.489431] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Apr 26 17:38:21 PC-MSI kernel: [    8.526099] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Apr 26 17:38:21 PC-MSI kernel: [    8.774037] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC662 rev1: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:speaker
Apr 26 17:38:21 PC-MSI kernel: [    8.774047] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Apr 26 17:38:21 PC-MSI kernel: [    8.774055] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x14/0x0/0x0/0x0/0x0)
Apr 26 17:38:21 PC-MSI kernel: [    8.774060] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Apr 26 17:38:21 PC-MSI kernel: [    8.774065] snd_hda_codec_realtek hdaudioC0D0:    inputs:
Apr 26 17:38:21 PC-MSI kernel: [    8.774073] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x19
Apr 26 17:38:21 PC-MSI kernel: [    8.774080] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
Apr 26 17:38:21 PC-MSI kernel: [    8.790169] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
Apr 26 17:38:21 PC-MSI kernel: [    8.790518] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Apr 26 17:38:21 PC-MSI kernel: [    8.945304] Adding 2150396k swap on /dev/sda2.  Priority:-2 extents:1 across:2150396k SSFS
Apr 26 17:38:21 PC-MSI systemd[1]: Starting Accounts Service...
Apr 26 17:38:21 PC-MSI systemd[1]: Starting Disk Manager...
Apr 26 17:38:21 PC-MSI systemd[1]: Started System Logging Service.
Apr 26 17:38:21 PC-MSI systemd[1]: Started Detect the available GPUs and deal with any system changes.
Apr 26 17:38:21 PC-MSI smartd[416]: smartd 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-48-generic] (local build)
Apr 26 17:38:21 PC-MSI smartd[416]: Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Apr 26 17:38:21 PC-MSI smartd[416]: Opened configuration file /etc/smartd.conf
Apr 26 17:38:21 PC-MSI smartd[416]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Apr 26 17:38:21 PC-MSI smartd[416]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Apr 26 17:38:21 PC-MSI udisksd[434]: udisks daemon version 2.7.6 starting
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Apr 26 17:38:21 PC-MSI systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], opened
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], SanDisk SSD PLUS 120GB, S/N:183234801488, WWN:5-001b44-8b949755b, FW:UE4500RL, 120 GB
Apr 26 17:38:21 PC-MSI udisksd[434]: failed to load module crypto: libbd_crypto.so.2: cannot open shared object file: No such file or directory
Apr 26 17:38:21 PC-MSI udisksd[434]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Apr 26 17:38:21 PC-MSI systemd[1]: Started Save/Restore Sound Card State.
Apr 26 17:38:21 PC-MSI udisksd[434]: Failed to load the 'mdraid' libblockdev plugin
Apr 26 17:38:21 PC-MSI udisksd[434]: Failed to load the 'crypto' libblockdev plugin
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], not found in smartd database.
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SanDisk_SSD_PLUS_120GB-183234801488.ata.state
Apr 26 17:38:21 PC-MSI smartd[416]: Monitoring 1 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 61 to 80
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], previous self-test was interrupted by the host with a reset
Apr 26 17:38:21 PC-MSI smartd[416]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SanDisk_SSD_PLUS_120GB-183234801488.ata.state
Apr 26 17:38:21 PC-MSI apport[381]:  * Starting automatic crash report generation: apport
Apr 26 17:38:21 PC-MSI NetworkManager[432]: <info>  [1556293101.8074] NetworkManager (version 1.10.6) is starting... (for the first time)
Apr 26 17:38:21 PC-MSI grub-common[425]:  * Recording successful boot for GRUB
Apr 26 17:38:21 PC-MSI NetworkManager[432]: <info>  [1556293101.8232] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)
Apr 26 17:38:21 PC-MSI apport[381]:    ...done.
Apr 26 17:38:21 PC-MSI systemd[1]: Started LSB: automatic crash report generation.
Apr 26 17:38:21 PC-MSI kernel: [   10.195720] intel_powerclamp: No package C-state available
Apr 26 17:38:21 PC-MSI grub-common[425]:    ...done.
Apr 26 17:38:21 PC-MSI systemd[1]: Started LSB: Record successful boot for GRUB.
Apr 26 17:38:21 PC-MSI NetworkManager[432]: <info>  [1556293101.8853] manager[0x5604a0d47060]: monitoring kernel firmware directory '/lib/firmware'.
Apr 26 17:38:21 PC-MSI NetworkManager[432]: <info>  [1556293101.8880] monitoring ifupdown state file '/run/network/ifstate'.
Apr 26 17:38:21 PC-MSI dbus-daemon[405]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.9' (uid=0 pid=432 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 26 17:38:21 PC-MSI kernel: [   10.262519] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3071, rev 0213 detected
Apr 26 17:38:21 PC-MSI kernel: [   10.268906] intel_powerclamp: No package C-state available
Apr 26 17:38:21 PC-MSI kernel: [   10.279468] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
Apr 26 17:38:21 PC-MSI systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Apr 26 17:38:22 PC-MSI systemd[1]: Started WPA supplicant.
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Hostname Service...
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Authorization Manager...
Apr 26 17:38:22 PC-MSI systemd[1]: Started Run anacron jobs.
Apr 26 17:38:22 PC-MSI kernel: [   10.418376] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Apr 26 17:38:22 PC-MSI anacron[459]: Anacron 2.3 started on 2019-04-26
Apr 26 17:38:22 PC-MSI anacron[459]: Normal exit (0 jobs run)
Apr 26 17:38:22 PC-MSI polkitd[458]: started daemon version 0.105 using authority implementation `local' version `0.105'
Apr 26 17:38:22 PC-MSI dbus-daemon[405]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Apr 26 17:38:22 PC-MSI systemd[1]: Started Authorization Manager.
Apr 26 17:38:22 PC-MSI accounts-daemon[433]: started daemon version 0.6.45
Apr 26 17:38:22 PC-MSI systemd[1]: Started Accounts Service.
Apr 26 17:38:22 PC-MSI avahi-daemon[419]: Server startup complete. Host name is PC-MSI.local. Local service cookie is 3024462852.
Apr 26 17:38:22 PC-MSI systemd[1]: Started Modem Manager.
Apr 26 17:38:22 PC-MSI dbus-daemon[405]: [system] Successfully activated service 'org.freedesktop.hostname1'
Apr 26 17:38:22 PC-MSI systemd[1]: Started Hostname Service.
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.3216] hostname: hostname: using hostnamed
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.3218] hostname: hostname changed from (none) to "PC-MSI"
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.3260] dns-mgr[0x5604a0d63170]: init: dns=systemd-resolved, rc-manager=symlink, plugin=systemd-resolved
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.3361] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ieee80211/phy0/rfkill0) (driver rt2800pci)
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.3380] manager[0x5604a0d47060]: rfkill: WiFi hardware radio set enabled
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.3391] manager[0x5604a0d47060]: rfkill: WWAN hardware radio set enabled
Apr 26 17:38:22 PC-MSI systemd-udevd[269]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 26 17:38:22 PC-MSI systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Apr 26 17:38:22 PC-MSI dbus-daemon[405]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=432 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 26 17:38:22 PC-MSI systemd[1]: Started Network Manager.
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 26 17:38:22 PC-MSI systemd[1]: Reached target Network.
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Permit User Sessions...
Apr 26 17:38:22 PC-MSI systemd[1]: Reached target Network is Online.
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Tool to automatically collect and submit kernel crash signatures...
Apr 26 17:38:22 PC-MSI systemd[1]: Started crash report submission daemon.
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Postfix Mail Transport Agent (instance -)...
Apr 26 17:38:22 PC-MSI systemd[1]: Starting OpenBSD Secure Shell server...
Apr 26 17:38:22 PC-MSI kernel: [   10.920296] msi_laptop: Identified laptop model 'MSI N014'
Apr 26 17:38:22 PC-MSI systemd[1]: Started Permit User Sessions.
Apr 26 17:38:22 PC-MSI systemd[1]: kerneloops.service: Found left-over process 476 (kerneloops) in control group while starting unit. Ignoring.
Apr 26 17:38:22 PC-MSI systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 26 17:38:22 PC-MSI dbus-daemon[405]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6668] init!
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6673]       interface-parser: parsing file /etc/network/interfaces
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6675]       interface-parser: finished parsing file /etc/network/interfaces
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6678] management mode: unmanaged
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6707] devices added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/wlan0, iface: wlan0)
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6708] device added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6712] devices added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/net/enp2s0, iface: enp2s0)
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6712] device added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/net/enp2s0, iface: enp2s0): no ifupdown configuration found.
Apr 26 17:38:22 PC-MSI systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6715] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6807] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6808] end _init.
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6809] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so)
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6812] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6813] (-1596449664) ... get_connections.
Apr 26 17:38:22 PC-MSI NetworkManager[432]: <info>  [1556293102.6814] (-1596449664) ... get_connections (managed=false): return empty list.
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Hold until boot process finishes up...
Apr 26 17:38:22 PC-MSI configure-instance.sh[473]: postconf: fatal: open /etc/postfix/main.cf: No such file or directory
Apr 26 17:38:22 PC-MSI systemd[1]: Starting Light Display Manager...
Apr 26 17:38:22 PC-MSI systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Apr 26 17:38:22 PC-MSI kernel: [   11.223213] input: MSI Laptop hotkeys as /devices/virtual/input/input11
Apr 26 17:38:22 PC-MSI whoopsie[472]: [17:38:22] Using lock path: /var/lock/whoopsie/lock
Apr 26 17:38:22 PC-MSI kernel: [   11.240450] msi_laptop: driver 0.5 successfully loaded
Apr 26 17:38:22 PC-MSI systemd[1]: Started OpenBSD Secure Shell server.
Apr 26 17:38:23 PC-MSI NetworkManager[432]: <info>  [1556293103.0027] keyfile: new connection /etc/NetworkManager/system-connections/GS7-GG 4 (481b6825-a443-45ce-a575-74faa1ccf77d,"GS7-GG 4")
Apr 26 17:38:23 PC-MSI systemd[1]: Started Disk Manager.
Apr 26 17:38:23 PC-MSI udisksd[434]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Apr 26 17:38:23 PC-MSI NetworkManager[432]: <info>  [1556293103.1813] keyfile: new connection /etc/NetworkManager/system-connections/GS7-GG 3 (02f9ecf6-df23-4e4d-8538-e68e0fb6efa1,"GS7-GG 3")
Apr 26 17:38:23 PC-MSI NetworkManager[432]: <info>  [1556293103.3056] keyfile: new connection /etc/NetworkManager/system-connections/GS7-GG 2 (fe2867a6-b4fc-4502-9a28-f72676426eeb,"GS7-GG 2")
Apr 26 17:38:23 PC-MSI networkd-dispatcher[429]: WARNING: systemd-networkd is not running, output will be incomplete.
Apr 26 17:38:23 PC-MSI systemd[1]: Started Dispatcher daemon for systemd-networkd.
Apr 26 17:38:23 PC-MSI NetworkManager[432]: <info>  [1556293103.5546] keyfile: new connection /etc/NetworkManager/system-connections/GS4-AC (5d6e38ae-267f-49c4-8343-ae28b7bff839,"GS4-AC")
Apr 26 17:38:23 PC-MSI NetworkManager[432]: <info>  [1556293103.7396] keyfile: new connection /etc/NetworkManager/system-connections/Freebox-8A8DC1 (da30a314-9647-461a-9ff3-c86b3eae59a5,"Freebox-8A8DC1")
Apr 26 17:38:23 PC-MSI configure-instance.sh[473]: postconf: fatal: open /etc/postfix/main.cf: No such file or directory
Apr 26 17:38:23 PC-MSI kernel: [   12.188830] pci 0000:00:00.0: Intel GMA3150 Chipset
Apr 26 17:38:23 PC-MSI kernel: [   12.188919] pci 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
Apr 26 17:38:23 PC-MSI kernel: [   12.189066] pci 0000:00:00.0: detected 8192K stolen memory
Apr 26 17:38:23 PC-MSI kernel: [   12.189125] [drm] Memory usable by graphics device = 512M
Apr 26 17:38:23 PC-MSI kernel: [   12.189135] checking generic (d0000000 130000) vs hw (d0000000 10000000)
Apr 26 17:38:23 PC-MSI kernel: [   12.189138] fb: switching to inteldrmfb from VESA VGA
Apr 26 17:38:23 PC-MSI kernel: [   12.189246] Console: switching to colour dummy device 80x25
Apr 26 17:38:23 PC-MSI kernel: [   12.204255] [drm] Replacing VGA console driver
Apr 26 17:38:23 PC-MSI kernel: [   12.219884] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Apr 26 17:38:23 PC-MSI kernel: [   12.219889] [drm] Driver supports precise vblank timestamp query.
Apr 26 17:38:23 PC-MSI NetworkManager[432]: <info>  [1556293103.9090] keyfile: new connection /etc/NetworkManager/system-connections/GS7-GG 1 (84ca827d-a36e-4503-92c9-634d42560815,"GS7-GG 1")
Apr 26 17:38:23 PC-MSI kernel: [   12.328283] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Apr 26 17:38:24 PC-MSI systemd[1]: Received SIGRTMIN+20 from PID 286 (plymouthd).
Apr 26 17:38:24 PC-MSI systemd[1]: Received SIGRTMIN+21 from PID 286 (plymouthd).
Apr 26 17:38:24 PC-MSI systemd[1]: Started Hold until boot process finishes up.
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.0862] keyfile: new connection /etc/NetworkManager/system-connections/GS7-GG (9db2ebbd-27a2-4fba-b6b1-320e443fc8a2,"GS7-GG")
Apr 26 17:38:24 PC-MSI systemd[1]: Starting Set console scheme...
Apr 26 17:38:24 PC-MSI systemd[1]: Started Set console scheme.
Apr 26 17:38:24 PC-MSI systemd[1]: Started Light Display Manager.
Apr 26 17:38:24 PC-MSI systemd[1]: Created slice system-getty.slice.
Apr 26 17:38:24 PC-MSI systemd[1]: Started Getty on tty1.
Apr 26 17:38:24 PC-MSI systemd[1]: Reached target Login Prompts.
Apr 26 17:38:24 PC-MSI kernel: [   12.520193] [drm] RC6 disabled, disabling runtime PM support
Apr 26 17:38:24 PC-MSI kernel: [   12.520229] [drm] initialized overlay support
Apr 26 17:38:24 PC-MSI kernel: [   12.522822] [drm] Initialized i915 1.6.0 20171023 for 0000:00:02.0 on minor 0
Apr 26 17:38:24 PC-MSI kernel: [   12.562645] input: MSI WMI hotkeys as /devices/virtual/input/input12
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.2470] keyfile: new connection /etc/NetworkManager/system-connections/Livebox-GG_EXT (c1517e1b-7487-4f04-a64c-1d0e256e1c4c,"Livebox-GG_EXT")
Apr 26 17:38:24 PC-MSI acpid: client connected from 529[0:0]
Apr 26 17:38:24 PC-MSI acpid: 1 client rule loaded
Apr 26 17:38:24 PC-MSI kernel: [   12.666343] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.3643] keyfile: new connection /etc/NetworkManager/system-connections/WiFiExtender-30d32d3b2578 (66f9dd1f-e59f-4ab1-a658-06210ff21a49,"WiFiExtender-30d32d3b2578")
Apr 26 17:38:24 PC-MSI systemd[1]: Reached target Sound Card.
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.4768] keyfile: new connection /etc/NetworkManager/system-connections/Livebox-GG (8240d6bc-68ae-4e0e-a119-7c17b41d4a30,"Livebox-GG")
Apr 26 17:38:24 PC-MSI kernel: [   12.821790] acpi device:1f: registered as cooling_device2
Apr 26 17:38:24 PC-MSI kernel: [   12.822177] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input13
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5245] get unmanaged devices count: 0
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5249] manager: rfkill: WiFi disabled by radio killswitch; enabled by state file
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5253] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Apr 26 17:38:24 PC-MSI kernel: [   12.868118] fbcon: inteldrmfb (fb0) is primary device
Apr 26 17:38:24 PC-MSI kernel: [   12.868457] Console: switching to colour frame buffer device 128x37
Apr 26 17:38:24 PC-MSI kernel: [   12.868488] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5254] manager: Networking is enabled by state file
Apr 26 17:38:24 PC-MSI nm-dispatcher: req:1 'hostname': new request (1 scripts)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5284] dhcp-init: Using DHCP client 'dhclient'
Apr 26 17:38:24 PC-MSI nm-dispatcher: req:1 'hostname': start running ordered scripts...
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5287] Loaded device plugin: NMBondDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI kernel: [   12.885853] gpio_ich: GPIO from 462 to 511 on gpio_ich
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5289] Loaded device plugin: NMBridgeDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5290] Loaded device plugin: NMDummyDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5292] Loaded device plugin: NMEthernetDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5293] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5295] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5296] Loaded device plugin: NMMacsecDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5297] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5318] Loaded device plugin: NMPppDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5320] Loaded device plugin: NMTunDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5321] Loaded device plugin: NMVethDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5322] Loaded device plugin: NMVlanDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5323] Loaded device plugin: NMVxlanDeviceFactory (internal)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5360] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5482] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5500] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5514] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5640] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-team.so)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5728] device (lo): carrier: link connected
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5818] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.5959] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.6092] keyfile: add connection in-memory (965620d5-49f3-3f8f-bb99-f3d612dc4121,"Connexion filaire 1")
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.6158] settings: (enp2s0): created default wired connection 'Connexion filaire 1'
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.6267] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 26 17:38:24 PC-MSI kernel: [   12.973045] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Apr 26 17:38:24 PC-MSI kernel: [   13.012176] r8169 0000:02:00.0 enp2s0: link down
Apr 26 17:38:24 PC-MSI kernel: [   13.012398] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.6769] wifi-nl80211: (wlan0): using nl80211 for WiFi device control
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.6790] device (wlan0): driver supports Access Point (AP) mode
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.6937] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <warn>  [1556293104.7000] Error: failed to open /run/network/ifstate
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.7268] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.7279] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.7585] modem-manager: ModemManager available
Apr 26 17:38:24 PC-MSI systemd[1]: postfix@-.service: Control process exited, code=exited status=1
Apr 26 17:38:24 PC-MSI systemd[1]: postfix@-.service: Failed with result 'exit-code'.
Apr 26 17:38:24 PC-MSI systemd[1]: Failed to start Postfix Mail Transport Agent (instance -).
Apr 26 17:38:24 PC-MSI systemd[1]: Reached target Multi-User System.
Apr 26 17:38:24 PC-MSI systemd[1]: Reached target Graphical Interface.
Apr 26 17:38:24 PC-MSI systemd[1]: Started Stop ureadahead data collection 45s after completed startup.
Apr 26 17:38:24 PC-MSI systemd[1]: Starting Update UTMP about System Runlevel Changes...
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.8563] supplicant: wpa_supplicant running
Apr 26 17:38:24 PC-MSI whoopsie[472]: [17:38:24] offline
Apr 26 17:38:24 PC-MSI systemd-udevd[268]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 26 17:38:24 PC-MSI systemd[1]: Started Update UTMP about System Runlevel Changes.
Apr 26 17:38:24 PC-MSI kernel: [   13.239520] rt2800pci 0000:01:00.0 wlp1s0: renamed from wlan0
Apr 26 17:38:24 PC-MSI NetworkManager[432]: <info>  [1556293104.9834] rfkill2: found WiFi radio killswitch (at /sys/devices/platform/msi-laptop-pf/rfkill/rfkill2) (platform driver msi-laptop-pf)
Apr 26 17:38:25 PC-MSI systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 26 17:38:25 PC-MSI systemd[1]: Startup finished in 3.520s (kernel) + 9.875s (userspace) = 13.396s.
Apr 26 17:38:25 PC-MSI set-cpufreq[386]: Setting ondemand scheduler for all CPUs
Apr 26 17:38:25 PC-MSI systemd[1]: Created slice system-systemd\x2dbacklight.slice.
Apr 26 17:38:25 PC-MSI systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
Apr 26 17:38:25 PC-MSI NetworkManager[432]: <info>  [1556293105.1740] devices added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/wlp1s0, iface: wlp1s0)
Apr 26 17:38:25 PC-MSI NetworkManager[432]: <info>  [1556293105.1742] device added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/wlp1s0, iface: wlp1s0): no ifupdown configuration found.
Apr 26 17:38:25 PC-MSI NetworkManager[432]: <info>  [1556293105.1782] device (wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 26 17:38:25 PC-MSI kernel: [   13.524322] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
Apr 26 17:38:25 PC-MSI systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Apr 26 17:38:25 PC-MSI ModemManager[394]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0': not supported by any plugin
Apr 26 17:38:26 PC-MSI systemd[1]: Created slice User Slice of gerard.
Apr 26 17:38:26 PC-MSI systemd[1]: Started Session c1 of user gerard.
Apr 26 17:38:26 PC-MSI systemd[1]: Starting User Manager for UID 1000...
Apr 26 17:38:26 PC-MSI systemd[599]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 26 17:38:26 PC-MSI systemd[599]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 26 17:38:26 PC-MSI systemd[599]: Reached target Paths.
Apr 26 17:38:26 PC-MSI systemd[599]: Reached target Timers.
Apr 26 17:38:26 PC-MSI systemd[599]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 26 17:38:26 PC-MSI systemd[599]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 26 17:38:26 PC-MSI systemd[599]: Listening on GnuPG network certificate management daemon.
Apr 26 17:38:26 PC-MSI systemd[599]: Starting D-Bus User Message Bus Socket.
Apr 26 17:38:26 PC-MSI systemd[599]: Listening on D-Bus User Message Bus Socket.
Apr 26 17:38:26 PC-MSI systemd[599]: Reached target Sockets.
Apr 26 17:38:26 PC-MSI systemd[599]: Reached target Basic System.
Apr 26 17:38:26 PC-MSI systemd[1]: Started User Manager for UID 1000.
Apr 26 17:38:26 PC-MSI systemd[599]: Reached target Default.
Apr 26 17:38:26 PC-MSI systemd[599]: Startup finished in 163ms.
Apr 26 17:38:26 PC-MSI systemd[599]: Started D-Bus User Message Bus.
Apr 26 17:38:26 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] AppArmor D-Bus mediation is enabled
Apr 26 17:38:27 PC-MSI NetworkManager[432]: <info>  [1556293107.5040] manager: rfkill: WiFi now enabled by radio killswitch
Apr 26 17:38:27 PC-MSI kernel: [   15.850928] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
Apr 26 17:38:27 PC-MSI kernel: [   15.860167] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.40
Apr 26 17:38:27 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=1000 pid=611 comm="/usr/bin/lxsession -s Lubuntu -e LXDE " label="unconfined")
Apr 26 17:38:27 PC-MSI systemd[599]: Starting Virtual filesystem service...
Apr 26 17:38:27 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 26 17:38:27 PC-MSI systemd[599]: Started Virtual filesystem service.
Apr 26 17:38:27 PC-MSI ModemManager[394]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0': not supported by any plugin
Apr 26 17:38:27 PC-MSI kernel: [   16.073387] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
Apr 26 17:38:27 PC-MSI wpa_supplicant[422]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Apr 26 17:38:27 PC-MSI wpa_supplicant[422]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Apr 26 17:38:27 PC-MSI wpa_supplicant[422]: dbus: Failed to construct signal
Apr 26 17:38:27 PC-MSI wpa_supplicant[422]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Apr 26 17:38:27 PC-MSI NetworkManager[432]: <info>  [1556293107.8228] device (wlp1s0): supplicant interface state: starting -> ready
Apr 26 17:38:27 PC-MSI NetworkManager[432]: <info>  [1556293107.8262] device (wlp1s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Apr 26 17:38:27 PC-MSI kernel: [   16.173590] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
Apr 26 17:38:28 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating service name='org.xfce.Xfconf' requested by ':1.7' (uid=1000 pid=746 comm="xfce4-power-manager " label="unconfined")
Apr 26 17:38:28 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.xfce.Xfconf'
Apr 26 17:38:28 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.8' (uid=1000 pid=746 comm="xfce4-power-manager " label="unconfined")
Apr 26 17:38:28 PC-MSI systemd[599]: Starting XFCE notifications service...
Apr 26 17:38:28 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating service name='ca.desrt.dconf' requested by ':1.15' (uid=1000 pid=738 comm="light-locker " label="unconfined")
Apr 26 17:38:28 PC-MSI xfce4-notifyd[761]: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Apr 26 17:38:28 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'ca.desrt.dconf'
Apr 26 17:38:29 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.freedesktop.Notifications'
Apr 26 17:38:29 PC-MSI systemd[599]: Started XFCE notifications service.
Apr 26 17:38:29 PC-MSI dbus-daemon[405]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.23' (uid=1000 pid=746 comm="xfce4-power-manager " label="unconfined")
Apr 26 17:38:29 PC-MSI systemd[1]: Starting Daemon for power management...
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.3225] policy: auto-activating connection 'GS7-GG'
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.3355] device (wlp1s0): Activation: starting connection 'GS7-GG' (9db2ebbd-27a2-4fba-b6b1-320e443fc8a2)
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.3495] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.3530] manager: NetworkManager state is now CONNECTING
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.3658] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.3706] device (wlp1s0): Activation: (wifi) access point 'GS7-GG' has security, but secrets are required.
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.3708] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4339] device (wlp1s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4487] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4538] device (wlp1s0): Activation: (wifi) connection 'GS7-GG' has security, and secrets exist.  No new secrets needed.
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4542] Config: added 'ssid' value 'GS7-GG'
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4555] Config: added 'scan_ssid' value '1'
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4556] Config: added 'bgscan' value 'simple:30:-80:86400'
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4558] Config: added 'key_mgmt' value 'WPA-PSK'
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4559] Config: added 'auth_alg' value 'OPEN'
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.4560] Config: added 'psk' value '<hidden>'
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: SME: Trying to authenticate with 32:07:4d:d1:d6:a8 (SSID='GS7-GG' freq=2437 MHz)
Apr 26 17:38:29 PC-MSI kernel: [   17.881002] wlp1s0: authenticate with 32:07:4d:d1:d6:a8
Apr 26 17:38:29 PC-MSI kernel: [   17.886905] wlp1s0: send auth to 32:07:4d:d1:d6:a8 (try 1/3)
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.5453] device (wlp1s0): supplicant interface state: ready -> authenticating
Apr 26 17:38:29 PC-MSI kernel: [   17.891370] wlp1s0: authenticated
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: Trying to associate with 32:07:4d:d1:d6:a8 (SSID='GS7-GG' freq=2437 MHz)
Apr 26 17:38:29 PC-MSI kernel: [   17.896099] wlp1s0: associate with 32:07:4d:d1:d6:a8 (try 1/3)
Apr 26 17:38:29 PC-MSI kernel: [   17.901068] wlp1s0: RX AssocResp from 32:07:4d:d1:d6:a8 (capab=0x431 status=0 aid=1)
Apr 26 17:38:29 PC-MSI kernel: [   17.901192] wlp1s0: associated
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.5555] device (wlp1s0): supplicant interface state: authenticating -> associating
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: Associated with 32:07:4d:d1:d6:a8
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.5655] device (wlp1s0): supplicant interface state: associating -> associated
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.5978] device (wlp1s0): supplicant interface state: associated -> 4-way handshake
Apr 26 17:38:29 PC-MSI kernel: [   18.085663] wlp1s0: Limiting TX power to 20 (20 - 0) dBm as advertised by 32:07:4d:d1:d6:a8
Apr 26 17:38:29 PC-MSI kernel: [   18.087299] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: WPA: Key negotiation completed with 32:07:4d:d1:d6:a8 [PTK=CCMP GTK=CCMP]
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 32:07:4d:d1:d6:a8 completed [id=0 id_str=]
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.7800] device (wlp1s0): supplicant interface state: 4-way handshake -> completed
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.7802] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'GS7-GG'.
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.8377] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.8491] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Apr 26 17:38:29 PC-MSI NetworkManager[432]: <info>  [1556293109.8572] dhcp4 (wlp1s0): dhclient started with pid 801
Apr 26 17:38:29 PC-MSI wpa_supplicant[422]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=9999 txrate=6500
Apr 26 17:38:30 PC-MSI dhclient[801]: DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 3 (xid=0x41388663)
Apr 26 17:38:30 PC-MSI dhclient[801]: DHCPREQUEST of 192.168.43.33 on wlp1s0 to 255.255.255.255 port 67 (xid=0x63863841)
Apr 26 17:38:30 PC-MSI dhclient[801]: DHCPOFFER of 192.168.43.33 from 192.168.43.1
Apr 26 17:38:30 PC-MSI dhclient[801]: DHCPACK of 192.168.43.33 from 192.168.43.1
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.1780] dhcp4 (wlp1s0):   address 192.168.43.33
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.1781] dhcp4 (wlp1s0):   plen 24 (255.255.255.0)
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.1782] dhcp4 (wlp1s0):   gateway 192.168.43.1
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.1783] dhcp4 (wlp1s0):   lease time 3600
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.1784] dhcp4 (wlp1s0):   hostname 'PC-MSI'
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.1785] dhcp4 (wlp1s0):   nameserver '192.168.43.1'
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.1786] dhcp4 (wlp1s0): state changed unknown -> bound
Apr 26 17:38:30 PC-MSI avahi-daemon[419]: Joining mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.43.33.
Apr 26 17:38:30 PC-MSI avahi-daemon[419]: New relevant interface wlp1s0.IPv4 for mDNS.
Apr 26 17:38:30 PC-MSI avahi-daemon[419]: Registering new address record for 192.168.43.33 on wlp1s0.IPv4.
Apr 26 17:38:30 PC-MSI dhclient[801]: bound to 192.168.43.33 -- renewal in 1373 seconds.
Apr 26 17:38:30 PC-MSI whoopsie[472]: [17:38:30] Cannot reach: https://daisy.ubuntu.com
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2125] device (wlp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2202] device (wlp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2278] device (wlp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2300] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2437] manager: NetworkManager state is now CONNECTED_SITE
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2457] policy: set 'GS7-GG' (wlp1s0) as default for IPv4 routing and DNS
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2515] device (wlp1s0): Activation: successful, device activated.
Apr 26 17:38:30 PC-MSI nm-dispatcher: req:2 'up' [wlp1s0]: new request (1 scripts)
Apr 26 17:38:30 PC-MSI nm-dispatcher: req:2 'up' [wlp1s0]: start running ordered scripts...
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.2737] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 26 17:38:30 PC-MSI nm-dispatcher: req:3 'connectivity-change': new request (1 scripts)
Apr 26 17:38:30 PC-MSI whoopsie[472]: [17:38:30] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 26 17:38:30 PC-MSI whoopsie[472]: [17:38:30] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 26 17:38:30 PC-MSI whoopsie[472]: [17:38:30] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 26 17:38:30 PC-MSI upowerd[774]: failed to coldplug unifying device: Unable to satisfy request, HID++ error 03
Apr 26 17:38:30 PC-MSI dbus-daemon[405]: [system] Successfully activated service 'org.freedesktop.UPower'
Apr 26 17:38:30 PC-MSI systemd[1]: Started Daemon for power management.
Apr 26 17:38:30 PC-MSI NetworkManager[432]: <info>  [1556293110.6692] manager: startup complete
Apr 26 17:38:30 PC-MSI systemd[1]: Reloading OpenBSD Secure Shell server.
Apr 26 17:38:30 PC-MSI systemd[1]: Reloaded OpenBSD Secure Shell server.
Apr 26 17:38:30 PC-MSI nm-dispatcher[467]: postconf: fatal: open /etc/postfix/main.cf: No such file or directory
Apr 26 17:38:31 PC-MSI systemd-resolved[342]: Using degraded feature set (UDP) for DNS server 192.168.43.1.
Apr 26 17:38:31 PC-MSI avahi-daemon[419]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::874c:99b0:da30:66f.
Apr 26 17:38:31 PC-MSI avahi-daemon[419]: New relevant interface wlp1s0.IPv6 for mDNS.
Apr 26 17:38:31 PC-MSI avahi-daemon[419]: Registering new address record for fe80::874c:99b0:da30:66f on wlp1s0.*.
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.13' (uid=1000 pid=717 comm="pcmanfm --desktop --profile lubuntu " label="unconfined")
Apr 26 17:38:32 PC-MSI systemd[599]: Starting Virtual filesystem service - disk device monitor...
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Apr 26 17:38:32 PC-MSI systemd[599]: Started Virtual filesystem service - disk device monitor.
Apr 26 17:38:32 PC-MSI systemd[1]: Reloading OpenBSD Secure Shell server.
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.13' (uid=1000 pid=717 comm="pcmanfm --desktop --profile lubuntu " label="unconfined")
Apr 26 17:38:32 PC-MSI systemd[599]: Starting Virtual filesystem service - Apple File Conduit monitor...
Apr 26 17:38:32 PC-MSI nm-dispatcher[467]: postconf: fatal: open /etc/postfix/main.cf: No such file or directory
Apr 26 17:38:32 PC-MSI gvfs-afc-volume-monitor[915]: Volume monitor alive
Apr 26 17:38:32 PC-MSI systemd[1]: Reloaded OpenBSD Secure Shell server.
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Apr 26 17:38:32 PC-MSI systemd[599]: Started Virtual filesystem service - Apple File Conduit monitor.
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.13' (uid=1000 pid=717 comm="pcmanfm --desktop --profile lubuntu " label="unconfined")
Apr 26 17:38:32 PC-MSI systemd[599]: Starting Virtual filesystem service - digital camera monitor...
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Apr 26 17:38:32 PC-MSI systemd[599]: Started Virtual filesystem service - digital camera monitor.
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.13' (uid=1000 pid=717 comm="pcmanfm --desktop --profile lubuntu " label="unconfined")
Apr 26 17:38:32 PC-MSI systemd[599]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Apr 26 17:38:32 PC-MSI systemd[599]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.13' (uid=1000 pid=717 comm="pcmanfm --desktop --profile lubuntu " label="unconfined")
Apr 26 17:38:32 PC-MSI systemd[599]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Apr 26 17:38:32 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Apr 26 17:38:32 PC-MSI systemd[599]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Apr 26 17:38:33 PC-MSI nm-dispatcher: req:3 'connectivity-change': start running ordered scripts...
Apr 26 17:38:35 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating service name='com.canonical.indicator.application' requested by ':1.12' (uid=1000 pid=710 comm="lxpanel --profile Lubuntu " label="unconfined")
Apr 26 17:38:35 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Activating service name='com.canonical.indicator.sound-gtk2' requested by ':1.12' (uid=1000 pid=710 comm="lxpanel --profile Lubuntu " label="unconfined")
Apr 26 17:38:35 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'com.canonical.indicator.application'
Apr 26 17:38:35 PC-MSI dbus-daemon[626]: [session uid=1000 pid=626] Successfully activated service 'com.canonical.indicator.sound-gtk2'
Apr 26 17:38:36 PC-MSI whoopsie[472]: [17:38:36] online
Apr 26 17:38:50 PC-MSI systemd-timesyncd[343]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Apr 26 17:39:10 PC-MSI systemd[1]: Starting Stop ureadahead data collection...
Apr 26 17:39:10 PC-MSI systemd[1]: Started Stop ureadahead data collection.
Apr 26 17:39:24 PC-MSI kernel: [   72.271393] random: crng init done
Apr 26 17:39:24 PC-MSI kernel: [   72.271403] random: 7 urandom warning(s) missed due to ratelimiting
Apr 26 17:39:39 PC-MSI wpa_supplicant[422]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-47 noise=9999 txrate=72200
Apr 26 17:39:45 PC-MSI kernel: [   93.268791] perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Apr 26 17:39:59 PC-MSI kernel: [  107.295059] perf: interrupt took too long (3165 > 3135), lowering kernel.perf_event_max_sample_rate to 63000
Apr 26 17:40:17 PC-MSI kernel: [  125.656463] perf: interrupt took too long (3986 > 3956), lowering kernel.perf_event_max_sample_rate to 50000
Apr 26 17:40:52 PC-MSI kernel: [  160.814593] perf: interrupt took too long (4983 > 4982), lowering kernel.perf_event_max_sample_rate to 40000
Apr 26 17:42:00 PC-MSI kernel: [  228.802312] perf: interrupt took too long (6278 > 6228), lowering kernel.perf_event_max_sample_rate to 31750
Apr 26 17:47:43 PC-MSI kernel: [  571.656382] perf: interrupt took too long (7892 > 7847), lowering kernel.perf_event_max_sample_rate to 25250
Apr 26 17:53:50 PC-MSI systemd[1]: Starting Cleanup of Temporary Directories...
Apr 26 17:53:50 PC-MSI systemd[1]: Started Cleanup of Temporary Directories.
gerard@PC-MSI:~$

nany · Le 26/04/2019, à 17:54

Eh oui, j’ai mis qu’un n pour passer incognito mais ça marche pas.

Bien, rien de probant à propos de plymouth. Donne le retour de :

grep -i -C20 "plymouth" /var/log/apt/history.log

winux · Le 26/04/2019, à 19:39

OK, voici, pas terrible, mais peut-être à nouveau de ma faute car pour ne plus avoir la fenêtre d'erreur j'ai utilisé ta commande magique pour faire le ménage, Il va falloir attendre la prochaine mise à jour.

gerard@PC-MSI:~$ grep -i -C20 "plymouth" /var/log/apt/history.log
gerard@PC-MSI:~$

Dernière modification par winux (Le 26/04/2019, à 19:43)

nany · Le 26/04/2019, à 19:57

winux a écrit :

Il va falloir attendre la prochaine mise à jour.

Ben justement, on va faire les mises à jour. Normalement, il y a du plymouth dans les tuyaux.
Donne le retour de :

sudo apt update && sudo apt full-upgrade

Normalement, on devrait voir passer plymouth. Je ne sais pas si ça résoudra le problème mais croisons les doigts.

winux · Le 26/04/2019, à 21:33

Effectivement c'est la grosse mise à jour !
J'ai vu passer pas mal de Plymouth.
Je rentre demain sur Paris, donc pas de news de moi avant demain soir au cas où je devrais faire d'autres essais, merci pour tout nany-avec-un-seul-n !

gerard@PC-MSI:~$ sudo apt update && sudo apt full-upgrade
[sudo] Mot de passe de gerard : 
Atteint :1 http://fr.archive.ubuntu.com/ubuntu bionic InRelease
Atteint :2 http://archive.canonical.com/ubuntu bionic InRelease       
Réception de :3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB]
Atteint :4 http://fr.archive.ubuntu.com/ubuntu bionic-updates InRelease
Atteint :5 http://fr.archive.ubuntu.com/ubuntu bionic-backports InRelease      
88,7 ko réceptionnés en 3s (29,5 ko/s)                                         
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
7 paquets peuvent être mis à jour. Exécutez « apt list --upgradable » pour les voir.
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Calcul de la mise à jour... Fait
Les paquets suivants seront mis à jour :
  libnuma1 libplymouth4 login passwd plymouth plymouth-label
  plymouth-theme-ubuntu-text
7 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 1356 ko dans les archives.
Après cette opération, 17,4 ko d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Réception de :1 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 login amd64 1:4.5-1ubuntu2 [308 kB]
Réception de :2 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 passwd amd64 1:4.5-1ubuntu2 [816 kB]
Réception de :3 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnuma1 amd64 2.0.11-2.1ubuntu0.1 [22,0 kB]
Réception de :4 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libplymouth4 amd64 0.9.3-1ubuntu7.18.04.2 [87,5 kB]
Réception de :5 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 plymouth-label amd64 0.9.3-1ubuntu7.18.04.2 [6232 B]
Réception de :6 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 plymouth-theme-ubuntu-text amd64 0.9.3-1ubuntu7.18.04.2 [9060 B]
Réception de :7 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 plymouth amd64 0.9.3-1ubuntu7.18.04.2 [108 kB]
1356 ko réceptionnés en 1s (1003 ko/s)
(Lecture de la base de données... 175893 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../login_1%3a4.5-1ubuntu2_amd64.deb ...
Dépaquetage de login (1:4.5-1ubuntu2) sur (1:4.5-1ubuntu1) ...
Paramétrage de login (1:4.5-1ubuntu2) ...
(Lecture de la base de données... 175893 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../passwd_1%3a4.5-1ubuntu2_amd64.deb ...
Dépaquetage de passwd (1:4.5-1ubuntu2) sur (1:4.5-1ubuntu1) ...
Paramétrage de passwd (1:4.5-1ubuntu2) ...
(Lecture de la base de données... 175893 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../libnuma1_2.0.11-2.1ubuntu0.1_amd64.deb ...
Dépaquetage de libnuma1:amd64 (2.0.11-2.1ubuntu0.1) sur (2.0.11-2.1) ...
Préparation du dépaquetage de .../libplymouth4_0.9.3-1ubuntu7.18.04.2_amd64.deb ...
Dépaquetage de libplymouth4:amd64 (0.9.3-1ubuntu7.18.04.2) sur (0.9.3-1ubuntu7.18.04.1) ...
Préparation du dépaquetage de .../plymouth-label_0.9.3-1ubuntu7.18.04.2_amd64.deb ...
Dépaquetage de plymouth-label (0.9.3-1ubuntu7.18.04.2) sur (0.9.3-1ubuntu7.18.04.1) ...
Préparation du dépaquetage de .../plymouth-theme-ubuntu-text_0.9.3-1ubuntu7.18.04.2_amd64.deb ...
Dépaquetage de plymouth-theme-ubuntu-text (0.9.3-1ubuntu7.18.04.2) sur (0.9.3-1ubuntu7.18.04.1) ...
Préparation du dépaquetage de .../plymouth_0.9.3-1ubuntu7.18.04.2_amd64.deb ...
Dépaquetage de plymouth (0.9.3-1ubuntu7.18.04.2) sur (0.9.3-1ubuntu7.18.04.1) ...
Traitement des actions différées (« triggers ») pour ureadahead (0.100.0-21) ...
ureadahead will be reprofiled on next reboot
Paramétrage de libnuma1:amd64 (2.0.11-2.1ubuntu0.1) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.27-3ubuntu1) ...
Traitement des actions différées (« triggers ») pour systemd (237-3ubuntu10.21) ...
Paramétrage de libplymouth4:amd64 (0.9.3-1ubuntu7.18.04.2) ...
Traitement des actions différées (« triggers ») pour man-db (2.8.3-2ubuntu0.1) ...
Paramétrage de plymouth (0.9.3-1ubuntu7.18.04.2) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Paramétrage de plymouth-label (0.9.3-1ubuntu7.18.04.2) ...
Paramétrage de plymouth-theme-ubuntu-text (0.9.3-1ubuntu7.18.04.2) ...
update-initramfs: deferring update (trigger activated)
Traitement des actions différées (« triggers ») pour libc-bin (2.27-3ubuntu1) ...
Traitement des actions différées (« triggers ») pour initramfs-tools (0.130ubuntu3.7) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-48-generic
gerard@PC-MSI:~$

winux · Le 26/04/2019, à 21:39

Bravo nany
Après reboot et malgré ce gros update la fenêtre n'est pas réapparue. Le full-upgrade semble être la solution, du moins je l'espère. Wait and see.
Bonne nuit, on attend un peu avant de fêter la victoire

Dernière modification par winux (Le 26/04/2019, à 21:40)

nany · Le 27/04/2019, à 10:05

Bien, j’espère que cette mise à jour de plymouth va mettre fin à la vague de demandes d’aide sur le sujet qu’on a pu avoir ces derniers temps.
Merci d’avoir collaboré.

winux · Le 27/04/2019, à 13:37

nany a écrit :

Bien, j’espère que cette mise à jour de plymouth va mettre fin à la vague de demandes d’aide sur le sujet qu’on a pu avoir ces derniers temps.

Hello nany
J'aurais adoré te dire que tout était fini, malheureusement tout juste arrivé à Paris j'ai ouvert le petit portable, celui qui pose Pb, et la fenêtre maléfique s'est à nouveau affichée "Pb de logiciel,détecté". Ca devient vraiment coton cette histoire.

Je viens de mettre à jour les 2 autres Lubuntu sur vieux PC fixes. Après le redémarrage demandé en fin d'installe, pas de fenêtre parasite (mais c'était pareil hier pour le petit). J'arrête et je démarre après 5s d'arrêt et toujours rien.
Je serais tenté de dire :
sur 2 PC fixes : pas de Pb
sur un PC portable : Pb récurrent, mais ça me parait difficile d'extrapoler sur un si petit échantillon.

Par contre il me reste un portable HP plus récent (3 ans) avec 4 Go de mémoire et un i5 6200U, mais quand même lent à démarrer sous Ububntu. Je vais lui installer Lubuntu pour voir, ça pourrait donner des pistes, si lui aussi affiche la fenêtre maudite ! ... peut-être ??

nany a écrit :

Merci d’avoir collaboré.

Ce fut un plaisir.
Merci surtout à toi pour ton aide !
Au fait, pour mon info, tu m'as l'air calée en ligne de commande, tu fais (ou a fait) partie de l'équipe de développement ?
@+

winux · Le 27/04/2019, à 13:37

winux a écrit :

nany a écrit :
Bien, j’espère que cette mise à jour de plymouth va mettre fin à la vague de demandes d’aide sur le sujet qu’on a pu avoir ces derniers temps.
Hello nany
J'aurais adoré te dire que tout était fini, malheureusement tout juste arrivé à Paris j'ai ouvert le petit portable, celui qui pose Pb et, sans mise à jour, la fenêtre maléfique s'est à nouveau affichée "Pb de logiciel,détecté". Ca devient vraiment coton cette histoire.
Je viens de mettre à jour les 2 autres Lubuntu sur vieux PC fixes. Après le redémarrage demandé en fin d'installe, pas de fenêtre parasite (mais c'était pareil hier pour le petit). J'arrête et je démarre après 5s d'arrêt et toujours rien.
Je serais tenté de dire :
sur 2 PC fixes : pas de Pb
sur un PC portable : Pb récurrent, mais ça me parait difficile d'extrapoler sur un si petit échantillon.
Par contre il me reste un portable HP plus récent (3 ans) avec 4 Go de mémoire et un i5 6200U, mais quand même lent à démarrer sous Ububntu. Je vais lui installer Lubuntu pour voir, ça pourrait donner des pistes, si lui aussi affiche la fenêtre maudite ! ... peut-être ??
nany a écrit :
Merci d’avoir collaboré.
Ce fut un plaisir.
Merci surtout à toi pour ton aide !
Au fait, pour mon info, tu m'as l'air calée en ligne de commande, tu fais (ou a fait) partie de l'équipe de développement ?
@+

winux · Le 27/04/2019, à 13:38

winux a écrit :

winux a écrit :
nany a écrit :
Bien, j’espère que cette mise à jour de plymouth va mettre fin à la vague de demandes d’aide sur le sujet qu’on a pu avoir ces derniers temps.
[EDIT] j'ai complété le texte
Hello nany
J'aurais adoré te dire que tout était fini, malheureusement tout juste arrivé à Paris j'ai ouvert le petit portable, celui qui pose Pb et, sans mise à jour, la fenêtre maléfique s'est à nouveau affichée "Pb de logiciel,détecté". Ca devient vraiment coton cette histoire.
Je viens de mettre à jour les 2 autres Lubuntu sur vieux PC fixes eux aussi MBR. Après le redémarrage demandé en fin d'installe, pas de fenêtre parasite (mais c'était pareil hier pour le petit). J'arrête et je démarre après 5s d'arrêt et toujours rien.
Mêmes essais depuis le PC de ma femme, une autre tour en MBR
Je serais tenté de dire :
- sur 3 PC fixes : pas de Pb
- sur un PC portable : Pb récurrent, mais ça me parait difficile d'extrapoler sur un si petit échantillon.
Une des différences est la wifi (bien que rien à voir avec plymouth), mais essai avec RJ45, pareil pour le petit
Par contre il me reste un portable HP plus récent (3 ans) avec 4 Go de mémoire et un i5 6200U, mais quand même lent à démarrer sous Ububntu. Je vais lui installer Lubuntu pour voir, ça pourrait donner des pistes, si lui aussi affiche la fenêtre maudite ! ... peut-être ??
nany a écrit :
Merci d’avoir collaboré.
Ce fut un plaisir.
Merci surtout à toi pour ton aide !
Au fait, pour mon info, tu m'as l'air calée en ligne de commande, tu fais (ou a fait) partie de l'équipe de développement ?
@+

Dernière modification par winux (Le 27/04/2019, à 13:54)

nany · Le 27/04/2019, à 13:47

winux a écrit :

J'aurais adoré te dire que tout était fini, malheureusement tout juste arrivé à Paris j'ai ouvert le petit portable, celui qui pose Pb, et la fenêtre maléfique s'est à nouveau affichée "Pb de logiciel,détecté". Ca devient vraiment coton cette histoire.

Redonne le retour de

ls -l /var/crash

pour voir de quand date le rapport.

winux a écrit :

Au fait, pour mon info, tu m'as l'air calée en ligne de commande, tu fais (ou a fait) partie de l'équipe de développement ?

Non, non, je suis juste « nounou d’enfer ».

winux · Le 27/04/2019, à 13:50

winux a écrit :

winux a écrit :
winux a écrit :
Hello nany
J'aurais adoré te dire que tout était fini, malheureusement tout juste arrivé à Paris j'ai ouvert le petit portable, celui qui pose Pb et, sans mise à jour, la fenêtre maléfique s'est à nouveau affichée "Pb de logiciel,détecté". Ca devient vraiment coton cette histoire.
Je viens de mettre à jour les 2 autres Lubuntu sur vieux PC fixes eux aussi MBR. Après le redémarrage demandé en fin d'installe, pas de fenêtre parasite (mais c'était pareil hier pour le petit). J'arrête et je démarre après 5s d'arrêt et toujours rien.
Mêmes essais depuis le PC de ma femme, une autre tour en MBR
Je serais tenté de dire :
- sur 3 PC fixes : pas de Pb
- sur un PC portable : Pb récurrent, mais ça me parait difficile d'extrapoler sur un si petit échantillon.
Une des différences est la wifi (bien que rien à voir avec plymouth), mais essai avec RJ45, pareil pour le petit
Par contre il me reste un portable HP plus récent (3 ans) avec 4 Go de mémoire et un i5 6200U, mais quand même lent à démarrer sous Ububntu. Je vais lui installer Lubuntu pour voir, ça pourrait donner des pistes, si lui aussi affiche la fenêtre maudite ! ... peut-être ??
Ce fut un plaisir.
Merci surtout à toi pour ton aide !
Au fait, pour mon info, tu m'as l'air calée en ligne de commande, tu fais (ou a fait) partie de l'équipe de développement ?
@+

winux · Le 27/04/2019, à 14:01

Voici la dernière réponse

gerard@PC-MSI:~$ ls -l /var/crash
total 592
-rw-r----- 1 root whoopsie 601482 avril 27 14:14 _sbin_plymouthd.0.crash
gerard@PC-MSI:~$

C'est vraie que tu es une super nounou pour les enfants dans le besoin !

nany · Le 27/04/2019, à 14:08

Ok. Ça date de cet après-midi donc après la maj de plymouth.
Affaire à suivre, alors…

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#26 Le 24/04/2019, à 20:02

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#27 Le 24/04/2019, à 20:12

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#28 Le 24/04/2019, à 21:36

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#29 Le 25/04/2019, à 09:36

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#30 Le 25/04/2019, à 11:09

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#31 Le 25/04/2019, à 11:33

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#32 Le 25/04/2019, à 12:25

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#33 Le 25/04/2019, à 14:21

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#34 Le 25/04/2019, à 19:41

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#35 Le 25/04/2019, à 20:45

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#36 Le 26/04/2019, à 15:18

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#37 Le 26/04/2019, à 16:56

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#38 Le 26/04/2019, à 17:54

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#39 Le 26/04/2019, à 19:39

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#40 Le 26/04/2019, à 19:57

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#41 Le 26/04/2019, à 21:33

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#42 Le 26/04/2019, à 21:39

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#43 Le 27/04/2019, à 10:05

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#44 Le 27/04/2019, à 13:37

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#45 Le 27/04/2019, à 13:37

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#46 Le 27/04/2019, à 13:38

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#47 Le 27/04/2019, à 13:47

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#48 Le 27/04/2019, à 13:50

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#49 Le 27/04/2019, à 14:01

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

#50 Le 27/04/2019, à 14:08

Re : [1/2 RÉSOLU] message sur mes 4 PC en Lub18 "erreur logiciel détectée"

Pied de page des forums