Serpolet
Messages : 820
Enregistré le : 02 févr. 2019, 19:19

18.04.4 : comment nettoyer tout cela ?

02 mai 2020, 16:11

bonjour

tout est dans le titre

ces erreurs, comment les supprimer ?

journalctl -b -p err
-- Logs begin at Sat 2020-01-18 12:41:33 CET, end at Sat 2020-05-02 16:05:36 CEST. --
mai 02 09:23:30 XXXXXX kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
mai 02 09:23:30 XXXXXX kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
mai 02 09:23:30 XXXXXX kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
mai 02 09:23:30 XXXXXX kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
mai 02 09:23:30 XXXXXX kernel: sd 8:0:0:0: [sdg] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 8:0:0:0: [sdg] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: sd 9:0:0:0: [sdi] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 9:0:0:0: [sdi] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: scsi 8:0:0:1: Wrong diagnostic page; asked for 1 got 8
mai 02 09:23:30 XXXXXX kernel: scsi 8:0:0:1: Failed to get diagnostic page 0x1
mai 02 09:23:30 XXXXXX kernel: scsi 8:0:0:1: Failed to bind enclosure -19
mai 02 09:23:30 XXXXXX kernel: ses 9:0:0:1: Failed to get diagnostic page 0x1
mai 02 09:23:30 XXXXXX kernel: ses 9:0:0:1: Failed to bind enclosure -19
mai 02 09:23:30 XXXXXX kernel: ses 10:0:0:1: Wrong diagnostic page; asked for 1 got 8
mai 02 09:23:30 XXXXXX kernel: ses 10:0:0:1: Failed to get diagnostic page 0x1
mai 02 09:23:30 XXXXXX kernel: ses 10:0:0:1: Failed to bind enclosure -19
mai 02 09:23:30 XXXXXX kernel: ses 11:0:0:1: Failed to get diagnostic page 0x1
mai 02 09:23:30 XXXXXX kernel: ses 11:0:0:1: Failed to bind enclosure -19
mai 02 09:23:30 XXXXXX kernel: sd 10:0:0:0: [sdj] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 10:0:0:0: [sdj] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: ses 13:0:0:1: Wrong diagnostic page; asked for 1 got 8
mai 02 09:23:30 XXXXXX kernel: ses 13:0:0:1: Failed to get diagnostic page 0x1
mai 02 09:23:30 XXXXXX kernel: ses 13:0:0:1: Failed to bind enclosure -19
mai 02 09:23:30 XXXXXX kernel: sd 11:0:0:0: [sdk] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 11:0:0:0: [sdk] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: sd 12:0:0:0: [sdl] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 12:0:0:0: [sdl] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: sd 13:0:0:0: [sdm] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 13:0:0:0: [sdm] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: ses 14:0:0:1: Failed to get diagnostic page 0x1
mai 02 09:23:30 XXXXXX kernel: ses 14:0:0:1: Failed to bind enclosure -19
mai 02 09:23:30 XXXXXX kernel: ses 15:0:0:1: Failed to get diagnostic page 0x1
mai 02 09:23:30 XXXXXX kernel: ses 15:0:0:1: Failed to bind enclosure -19
mai 02 09:23:30 XXXXXX kernel: sd 15:0:0:0: [sdo] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 15:0:0:0: [sdo] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: sd 16:0:0:0: [sdp] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 16:0:0:0: [sdp] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: sd 17:0:0:0: [sdq] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 17:0:0:0: [sdq] Assuming drive cache: write through
mai 02 09:23:30 XXXXXX kernel: sd 14:0:0:0: [sdn] No Caching mode page found
mai 02 09:23:30 XXXXXX kernel: sd 14:0:0:0: [sdn] Assuming drive cache: write through
mai 02 09:23:34 XXXXXX systemd-udevd[563]: Invalid rule /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9: unknown key 'SYSFS{idVendor}'
mai 02 09:24:19 XXXXXX hp[2048]: io/hpmud/pp.c 627: unable to read device-id ret=-1
mai 02 09:24:34 XXXXXX lightdm[2272]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
mai 02 09:24:34 XXXXXX lightdm[2272]: PAM adding faulty module: pam_kwallet.so
mai 02 09:24:34 XXXXXX lightdm[2272]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
mai 02 09:24:34 XXXXXX lightdm[2272]: PAM adding faulty module: pam_kwallet5.so
mai 02 09:24:38 XXXXXX systemd[1]: Failed to start Network Manager Wait Online.
mai 02 09:24:47 XXXXXX colord-sane[2033]: io/hpmud/pp.c 627: unable to read device-id ret=-1
mai 02 09:25:01 XXXXXX lightdm[2629]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
mai 02 09:25:01 XXXXXX lightdm[2629]: PAM adding faulty module: pam_kwallet.so
mai 02 09:25:01 XXXXXX lightdm[2629]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
mai 02 09:25:01 XXXXXX lightdm[2629]: PAM adding faulty module: pam_kwallet5.so
mai 02 09:25:32 XXXXXX spice-vdagent[3126]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mai 02 09:25:40 XXXXXX pulseaudio[3197]: [pulseaudio] pid.c: Daemon already running.
mai 02 09:26:04 XXXXXX pulseaudio[3057]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
mai 02 09:27:08 XXXXXX colord-sane[3279]: io/hpmud/pp.c 627: unable to read device-id ret=-1
mai 02 11:25:47 XXXXXX systemd-udevd[563]: Invalid rule /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9: unknown key 'SYSFS{idVendor}'
mai 02 11:26:24 XXXXXX simple-scan[20410]: io/hpmud/pp.c 627: unable to read device-id ret=-1
mai 02 12:32:35 XXXXXX colord-sane[25136]: io/hpmud/pp.c 627: unable to read device-id ret=-1
mai 02 14:48:11 XXXXXX simple-scan[9205]: io/hpmud/pp.c 627: unable to read device-id ret=-1
mai 02 15:19:23 XXXXXX kernel: usblp: can't set desired altsetting 0 on interface 0

Retourner vers « Xubuntu »