probleme apres mise à niveau RESOLU

geole · Le 05/02/2023, à 14:46

Peux-tu faire

mkdir A B
sudo mount -v /dev/sda3 A

sudo mount -v /dev/sda6 B
df -BM -text3
df -BM -text4

Ainsi que

grep -v "#" B/etc/fstab

Dernière modification par geole (Le 05/02/2023, à 14:49)

dellko · Le 05/02/2023, à 14:50

ubuntu@ubuntu:~$ mkdir A B
ubuntu@ubuntu:~$ sudo mount -v /dev/sda3 A
mount: /dev/sda3 mounted on /home/ubuntu/A.

ubuntu@ubuntu:~$ sudo mount -v /dev/sda6 B
mount: /dev/sda6 mounted on /home/ubuntu/B.
ubuntu@ubuntu:~$ df -BM -text3
Filesystem     1M-blocks  Used Available Use% Mounted on
/dev/sda3            81M   13M       39M  25% /home/ubuntu/A
ubuntu@ubuntu:~$ df -BM -text4
Filesystem     1M-blocks   Used Available Use% Mounted on
/dev/sda6         75567M 44677M    27010M  63% /home/ubuntu/B

je crois ubuntu est sur sda6

Dernière modification par dellko (Le 05/02/2023, à 14:51)

geole · Le 05/02/2023, à 14:59

La piste du manque de place disque est à écarter.
J’attends le retour du fstab
Tu donneras aussi ce retour

ls -ls /home/ubuntu/A

Dernière modification par geole (Le 05/02/2023, à 15:14)

dellko · Le 05/02/2023, à 14:59

Ok

dellko · Le 05/02/2023, à 15:02

ubuntu@ubuntu:~$ ls -ls /home/ubuntu/A
total 16
16 drwx------ 2 root root 16384 Feb  6  2021 lost+found

dellko · Le 05/02/2023, à 15:05

ubuntu@ubuntu:~$ grep -v "#" B/etc/fstab
UUID=81fefb9c-97f1-42f0-95de-2f34a09ccbe6 /               ext4    errors=remount-ro 0       1
/swapfile                                 none            swap    sw              0       0

geole · Le 05/02/2023, à 15:08

dellko a écrit :

ubuntu@ubuntu:~$ grep -v "#" B/etc/fstab
UUID=81fefb9c-97f1-42f0-95de-2f34a09ccbe6 /               ext4    errors=remount-ro 0       1

Cela colle aussi avec le lsblk précédant

└─sda6 ext4               81fefb9c-97f1-42f0-95de-2f34a09ccbe6

geole · Le 05/02/2023, à 15:11

Tandis qu’on y ait, donne la fin de la trace

journalctl --no-pager  -D B/var/log/journal  -n 500

Dernière modification par geole (Le 05/02/2023, à 15:13)

dellko · Le 05/02/2023, à 15:15

voici la tartine.....

ubuntu@ubuntu:~$ journalctl --no-pager  -D B/var/log/journal  -n 500
Journal file B/var/log/journal/a781b46dfe604baf9ff15ca5743f74d3/system@0005f3f337b620c9-c078678ca4c2f2b7.journal~ uses an unsupported feature, ignoring file.
Use SYSTEMD_LOG_LEVEL=debug journalctl --file=B/var/log/journal/a781b46dfe604baf9ff15ca5743f74d3/system@0005f3f337b620c9-c078678ca4c2f2b7.journal~ to see the details.
-- Logs begin at Thu 2020-12-03 13:59:07 UTC, end at Wed 2023-02-01 14:51:17 UTC. --
Feb 01 14:37:11 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:37:11 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:37:11 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:37:11 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:37:12 ann-Vostro-1700 systemd[1]: udisks2.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Feb 01 14:37:12 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:37:12 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:37:12 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:37:12 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:17 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:17 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:17 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:17 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1454 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Feb 01 14:37:17 ann-Vostro-1700 systemd[1417]: Starting Tracker metadata extractor...
Feb 01 14:37:17 ann-Vostro-1700 tracker-extract[40799]: Set scheduler policy to SCHED_IDLE
Feb 01 14:37:17 ann-Vostro-1700 tracker-extract[40799]: Setting priority nice level to 19
Feb 01 14:37:18 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:18 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Feb 01 14:37:18 ann-Vostro-1700 systemd[1417]: Started Tracker metadata extractor.
Feb 01 14:37:19 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:19 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:19 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:19 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:19 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:19 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:19 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:20 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:20 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:24 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:37:25 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:37:31 ann-Vostro-1700 systemd[1417]: tracker-extract.service: Succeeded.
Feb 01 14:37:32 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:32 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:32 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1454 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Feb 01 14:37:32 ann-Vostro-1700 systemd[1417]: Starting Tracker metadata extractor...
Feb 01 14:37:32 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:32 ann-Vostro-1700 tracker-extract[41092]: Set scheduler policy to SCHED_IDLE
Feb 01 14:37:32 ann-Vostro-1700 tracker-extract[41092]: Setting priority nice level to 19
Feb 01 14:37:32 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:33 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Feb 01 14:37:33 ann-Vostro-1700 systemd[1417]: Started Tracker metadata extractor.
Feb 01 14:37:33 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:33 ann-Vostro-1700 tracker-extract[41092]: Could not insert metadata for item with ID 108593: Subject `urn:uuid:81f69531-73b0-484e-b33a-32ad03f1aeb3' is not in domain `nie:DataObject' of property `nie:dataSource'
Feb 01 14:37:33 ann-Vostro-1700 tracker-extract[41092]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
Feb 01 14:37:34 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:34 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:34 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:34 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:34 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:34 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:34 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:35 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:43 ann-Vostro-1700 systemd[1417]: tracker-extract.service: Succeeded.
Feb 01 14:37:48 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:48 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:48 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:48 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:48 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:37:59 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:37:59 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:37:59 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:38:01 ann-Vostro-1700 systemd-udevd[368]: Configuration file /etc/udev/rules.d/79-udev-epson.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb 01 14:38:04 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:38:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:38:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:38:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:38:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:38:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:38:14 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:38:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:38:15 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:38:18 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:38:19 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:38:20 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:38:21 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:38:41 ann-Vostro-1700 systemd[1]: systemd-ask-password-plymouth.path: Succeeded.
Feb 01 14:38:41 ann-Vostro-1700 systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
Feb 01 14:38:42 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:38:45 ann-Vostro-1700 systemd-udevd[368]: Configuration file /etc/udev/rules.d/79-udev-epson.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:38:46 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:38:46 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:38:47 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:38:47 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:38:59 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:38:59 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:39:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:39:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:39:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:39:03 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:03 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:03 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:03 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:03 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:04 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:04 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:04 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:04 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:04 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:04 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:04 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:05 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:10 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:10 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:39:11 ann-Vostro-1700 systemd[1]: accounts-daemon.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Feb 01 14:39:11 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:11 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:13 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:14 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:14 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:39:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:39:52 ann-Vostro-1700 systemd[1]: ua-timer.timer: Succeeded.
Feb 01 14:39:52 ann-Vostro-1700 systemd[1]: Stopped Ubuntu Advantage Timer for running repeated jobs.
Feb 01 14:39:53 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:39:54 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:39:56 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:39:58 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:39:58 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:40:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:40:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:40:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:40:05 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:40:22 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:40:23 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:40:23 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:40:23 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:40:24 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:40:24 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:40:52 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:40:53 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:40:58 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:41:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:41:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:41:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:41:05 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:41:38 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:41:38 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:41:39 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:42:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:42:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:42:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:42:05 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:42:15 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:42:16 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:42:34 ann-Vostro-1700 systemd[1]: man-db.timer: Succeeded.
Feb 01 14:42:34 ann-Vostro-1700 systemd[1]: Stopped Daily man-db regeneration.
Feb 01 14:42:35 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:42:54 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:43:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:43:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:43:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:43:03 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:43:03 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:43:05 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:43:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:43:14 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:43:15 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:43:15 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:43:15 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:43:30 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:43:31 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:43:36 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:43:36 ann-Vostro-1700 systemd[1]: fstrim.timer: Succeeded.
Feb 01 14:43:36 ann-Vostro-1700 systemd[1]: Stopped Discard unused blocks once a week.
Feb 01 14:43:36 ann-Vostro-1700 systemd[1]: Stopping Discard unused blocks once a week.
Feb 01 14:43:36 ann-Vostro-1700 systemd[1]: Started Discard unused blocks once a week.
Feb 01 14:43:36 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:43:59 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:00 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:00 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:00 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:00 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:05 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:08 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:11 ann-Vostro-1700 systemd[1]: Stopping crash report submission daemon...
Feb 01 14:44:12 ann-Vostro-1700 systemd[1]: whoopsie.service: Succeeded.
Feb 01 14:44:12 ann-Vostro-1700 systemd[1]: Stopped crash report submission daemon.
Feb 01 14:44:12 ann-Vostro-1700 systemd-udevd[368]: Configuration file /etc/udev/rules.d/79-udev-epson.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: failed to search file: failed to load file: Erreur lors de l’ouverture du fichier /usr/share/color/icc/colord/x11-colors.icc.dpkg-new : Aucun fichier ou dossier de ce type
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: failed to search file: failed to load file: Erreur lors de l’ouverture du fichier /usr/share/color/icc/colord/sRGB.icc.dpkg-new : Aucun fichier ou dossier de ce type
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_3b80589086cd3cb9be79f226864e9669 »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_3c85d74bc9e8e96a43a70bcec260093d »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_695743cf63e8c5590d242beec01c2179 »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_4196c9abcf72e4c50a20779fc7c067af »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_d157efd089c1a6c1f6a48daf765afeee »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_4a125962d3de890419553f98db1bca91 »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_68c0284ee4c1f3c53ae046efae2e51dc »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_eff1632a2ce10ae7b538e5ca8c213944 »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_7af8535a229f23aa2fed2af104946955 »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_416044e70eb112694291cb3e921f081f »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_f65b8b8a63de00a75e70ed18739d076b »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_9b261811816e8d13faa98cad086873c1 »
Feb 01 14:44:15 ann-Vostro-1700 colord[1169]: CdMain: failed to emit ProfileAdded: failed to register object: Un objet est déjà exporté pour l’interface « org.freedesktop.ColorManager.Profile » en « /org/freedesktop/ColorManager/profiles/icc_8f5339e1c4f10efa07f66e756f744aca »
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:27 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:27 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:44:28 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:28 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:28 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:31 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:44:32 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:32 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:38 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:38 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:44:39 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:39 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:42 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:42 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:42 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:42 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:43 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:43 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:44 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:44 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:44 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:44 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:44 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:44 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:44 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:44:45 ann-Vostro-1700 systemd[1]: upower.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Feb 01 14:44:45 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:45 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:45 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:45 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:52 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:52 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:52 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:44:52 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:44:56 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:03 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:03 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:06 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:13 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:36 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:40 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:40 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:40 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:40 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:45:47 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:48 ann-Vostro-1700 evolution-calen[1992]: module_load: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib/x86_64-linux-gnu/libcamel-1.2.so.63)
Feb 01 14:45:48 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:45:48 ann-Vostro-1700 evolution-calendar-factory[1992]: Failed to load module: /usr/lib/evolution-data-server/calendar-backends/libecalbackendwebdavnotes.so
Feb 01 14:46:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:46:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:46:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:46:04 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:46:04 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:46:04 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:46:04 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:46:04 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:46:06 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:46:47 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:46:48 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:04 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 110 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:06 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:15 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 180 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:15 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 160 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:38 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:47:39 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:06 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:10 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:48:11 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:48:14 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:15 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:15 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:48:16 ann-Vostro-1700 systemd[1]: /lib/systemd/system/systemd-timesyncd.service:35: Unknown key name 'ProtectProc' in section 'Service', ignoring.
Feb 01 14:48:16 ann-Vostro-1700 systemd[1]: systemd-timesyncd.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring.
Feb 01 14:48:16 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:16 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:16 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:16 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:20 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[1472]: [session uid=1000 pid=1472] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:48:21 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:48:21 ann-Vostro-1700 systemd-udevd[368]: Configuration file /etc/udev/rules.d/79-udev-epson.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb 01 14:48:22 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:23 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:48:34 ann-Vostro-1700 systemd[1]: Reexecuting.
Feb 01 14:48:35 ann-Vostro-1700 systemd[1]: systemd 249.11-0ubuntu3.6 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
Feb 01 14:48:35 ann-Vostro-1700 systemd[1]: Detected architecture x86-64.
Feb 01 14:48:35 ann-Vostro-1700 systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Feb 01 14:48:35 ann-Vostro-1700 systemd[1]: Unknown serialization item 'show-status=no', ignoring.
Feb 01 14:48:36 ann-Vostro-1700 systemd[1]: Stopped target Printer Support.
Feb 01 14:48:59 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:49:00 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:49:06 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:49:20 ann-Vostro-1700 systemd[1]: motd-news.timer: Deactivated successfully.
Feb 01 14:49:20 ann-Vostro-1700 systemd[1]: Stopped Message of the Day.
Feb 01 14:49:20 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:49:21 ann-Vostro-1700 systemd[1]: dbus.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Feb 01 14:49:21 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:49:23 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:49:24 ann-Vostro-1700 systemd[1]: Started Message of the Day.
Feb 01 14:49:24 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:49:32 ann-Vostro-1700 systemd-udevd[368]: /lib/udev/rules.d/50-udev-default.rules:42 Unknown group 'sgx', ignoring
Feb 01 14:49:32 ann-Vostro-1700 systemd-udevd[368]: Configuration file /etc/udev/rules.d/79-udev-epson.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb 01 14:49:38 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:49:48 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:49:49 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:49:51 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: apt-daily-upgrade.timer: Deactivated successfully.
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: Stopped Daily apt upgrade and clean activities.
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: Stopping Daily apt upgrade and clean activities...
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: Started Daily apt upgrade and clean activities.
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: apt-daily.timer: Deactivated successfully.
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: Stopped Daily apt download activities.
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: Stopping Daily apt download activities...
Feb 01 14:49:52 ann-Vostro-1700 systemd[1]: Started Daily apt download activities.
Feb 01 14:49:57 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:49:58 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:06 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:14 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 46 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:33 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:34 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:50:58 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:50:58 ann-Vostro-1700 systemd[1]: Reloading.
Feb 01 14:50:59 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:50:59 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:50:59 ann-Vostro-1700 dbus-daemon[984]: Unknown group "power" in message bus configuration file
Feb 01 14:50:59 ann-Vostro-1700 dbus-daemon[984]: [system] Reloaded configuration
Feb 01 14:51:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 42 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:51:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:51:01 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:51:04 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:51:04 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 150 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:51:06 ann-Vostro-1700 kernel: b44 0000:03:00.0: swiotlb buffer is full (sz: 86 bytes), total 0 (slots), used 0 (slots)
Feb 01 14:51:14 ann-Vostro-1700 systemd[1]: Reexecuting.
Feb 01 14:51:14 ann-Vostro-1700 systemd[1]: systemd 249.11-0ubuntu3.6 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
Feb 01 14:51:14 ann-Vostro-1700 systemd[1]: Detected architecture x86-64.
Feb 01 14:51:15 ann-Vostro-1700 systemd[1]: Stopping Network Name Resolution...
Feb 01 14:51:16 ann-Vostro-1700 systemd[1]: systemd-resolved.service: Deactivated successfully.
Feb 01 14:51:16 ann-Vostro-1700 systemd[1]: Stopped Network Name Resolution.
Feb 01 14:51:16 ann-Vostro-1700 systemd[1]: Starting Network Name Resolution...
Feb 01 14:51:16 ann-Vostro-1700 systemd-udevd[368]: /lib/udev/rules.d/50-udev-default.rules:42 Unknown group 'sgx', ignoring
Feb 01 14:51:16 ann-Vostro-1700 kernel: proc: Bad value for 'hidepid'
Feb 01 14:51:16 ann-Vostro-1700 systemd-udevd[368]: Configuration file /etc/udev/rules.d/79-udev-epson.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb 01 14:51:17 ann-Vostro-1700 systemd-resolved[54246]: Positive Trust Anchors:
Feb 01 14:51:17 ann-Vostro-1700 systemd-resolved[54246]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Feb 01 14:51:17 ann-Vostro-1700 systemd-resolved[54246]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Feb 01 14:51:17 ann-Vostro-1700 systemd-resolved[54246]: Using system hostname 'ann-Vostro-1700'.
Feb 01 14:51:17 ann-Vostro-1700 systemd[1]: Started Network Name Resolution.
Feb 01 14:51:17 ann-Vostro-1700 systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 01 14:51:17 ann-Vostro-1700 systemd[1]: Stopping Journal Service...
Feb 01 14:51:17 ann-Vostro-1700 systemd-journald[264]: Journal stopped
ubuntu@ubuntu:~$

geole · Le 05/02/2023, à 15:30

Il s'est certainement passé quelque chose le 1er février vers 14heures 30
Le problème est que depuis cette date, cela n'écrit plus dans le journal..... Vu ce que tu expliques, je ne m'y attendais pas.

dellko · Le 05/02/2023, à 15:51

geole a écrit :

Il s'est certainement passé quelque chose le 1er février vers 14heures 30
Le problème est que depuis cette date, cela n'écrit plus dans le journal..... Vu ce que tu expliques, je ne m'y attendais pas.

Il me semble que c’est à cette date que j’ai fait la mise à niveau apres avoir fait la mise à jour j’ai cliquer sur ”mettre à niveau” sur la fenetre du gestionnaire de mise à jour
Je crois que quelque chose a bugé car ça a duré des heures et au soir j’ai du éteindre le pc manuellement vers 22h
J’avais deja fait une mise à niveau mour passer de la version 18.04 à la 20.04
Est il possible que mon pc ne soit pas compatible avec cette version car trop vieux ?
Je pense que je vais réinstaller à partir de ma clef
Mais avant je vais remettre de l’ordre dans mon sda, il y a trop de partitions j’ai pas géfé correctement quand j’ai supprimé vista

xubu1957 · Le 05/02/2023, à 15:53

Essaye :

sudo apt-get install -f

dellko · Le 05/02/2023, à 15:55

ubuntu@ubuntu:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

iznobe · Le 05/02/2023, à 17:24

Si tu reinstalles , je te conseillerai plutot de rester sur une 20.04 , et d' activer l ' ESM , je pense que ton ordi risque de se fatiguer sur une 22.04 et superieure .

l' ESM activé tu es encore bon pour 7 ans , donc d' ici là je pense que tu auras probablement changé d' ordi .

Cela dit , le probleme rencontré est surprenant , je ne pense pas que ce soit lié directement a l' ancienneté de l' ordinateur , meme si il n' est pas jeune .
Il se peut par contre que ton disque dur soit proche de sa limite ... tu le verras vite au ou tu reinstalles . ou bient tu peux verifier qu ' il est sain avec une session live et en produisant un rapport smart avec ta session live : https://doc.ubuntu-fr.org/smartmontools

dellko · Le 05/02/2023, à 18:13

Qu’est ce que l’ESM ?

iznobe · Le 05/02/2023, à 18:15

https://doc.ubuntu-fr.org/esm

xubu1957 · Le 05/02/2023, à 18:16

> Extended Security Maintenance (ESM) et Ubuntu Advantage

dellko · Le 05/02/2023, à 18:47

Merci xubu1957 et Iznobe j’y penserais quand j’aurais fait l’installation
J’ai une question (encore...) :
Peut on créer une nouvelle clef bootable à partir d’une session live ?
J’ai la version 18.04 sur ma clef et j’aimerais installer la 20.04 si c faisable

Pour le disque dur, c’est bien possible qu’il s’use le pauvre.
J’ai suivi le lien pour les smartmoontools, je vais essayer...

iznobe · Le 05/02/2023, à 19:16

c ' est possible si tu as un endroit annexe pour sauvegarder l' image autre que la clé usb et une 2eme clé .
il n' est pas possible de transformer la clé 18.04 en 20.04 en tout cas si ' est ta question .

Sinon c' est peut etre plus simple d ' installer la 18.04 , puis de faire la MANiveau vers 20.04 directement aprés avoir installé .
ca sera l' occasion de tester la commande "do-release-upgrade" ou " do-release upgrade" me rapelle plus exactement

dellko · Le 05/02/2023, à 19:33

Oui je pensais bien utiliser une seconde clef usb pour la version 20.04
Je viens de lancer un test avec smartmoontools qui devrait se terminer vers 20h (test long, autant faire un scan complet), je viendrai poster le résultat
Vais voir demain pour créer la nouvelle clef, là j’ai assez vu de code pour aujourd’hui et je préfère faire ça à tête reposée...

iznobe · Le 05/02/2023, à 19:37

je ne pens pas qu ' il soit utile de lancer le test long via smartmontools .
en general pour voir si le disque est en bonne santé , unfois l' outil installé il suffit de donné ce retour en adaptant la lettre correspondante au disque ( A en general quand on a un seul disque ) :

sudo smartctl -s on -a /dev/sda

dellko · Le 05/02/2023, à 21:35

iznobe a écrit :

je ne pens pas qu ' il soit utile de lancer le test long via smartmontools .
en general pour voir si le disque est en bonne santé , unfois l' outil installé il suffit de donné ce retour en adaptant la lettre correspondante au disque ( A en general quand on a un seul disque ) :
sudo smartctl -s on -a /dev/sda

ubuntu@ubuntu:~$ sudo smartctl -s on -a /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-20-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 7200.2
Device Model:     ST9200420ASG
Serial Number:    5SH09V1E
Firmware Version: 3.ADD
User Capacity:    200,049,647,616 bytes [200 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 (minor revision not indicated)
Local Time is:    Sun Feb  5 17:55:36 2023 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (  41)	The self-test routine was interrupted
					by the host with a hard or soft reset.
Total time to complete Offline 
data collection: 		(  426) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 111) minutes.
SCT capabilities: 	       (0x0035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   098   097   085    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   084   084   020    Old_age   Always       -       17304
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   078   051   030    Pre-fail  Always       -       72211091
  9 Power_On_Hours          0x0032   075   075   000    Old_age   Always       -       22520
 10 Spin_Retry_Count        0x0013   100   100   034    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   090   090   020    Old_age   Always       -       10862
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   059   037   045    Old_age   Always   In_the_past 41 (Min/Max 27/42 #123)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       3451
193 Load_Cycle_Count        0x0022   001   001   000    Old_age   Always       -       224610
194 Temperature_Celsius     0x001a   041   063   000    Old_age   Always       -       41 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x0012   059   046   000    Old_age   Always       -       63917773
197 Current_Pending_Sector  0x0010   100   100   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x003e   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0000   200   200   000    Old_age   Offline      -       5
200 Multi_Zone_Error_Rate   0x0032   100   253   000    Old_age   Always       -       0
202 Data_Address_Mark_Errs  0x0000   100   253   000    Old_age   Offline      -       0
240 Head_Flying_Hours       0x0000   000   000   000    Old_age   Offline      -       22616 (166 254 0)
241 Total_LBAs_Written      0x0000   000   000   000    Old_age   Offline      -       37347314276
242 Total_LBAs_Read         0x0000   000   000   000    Old_age   Offline      -       863577
254 Free_Fall_Sensor        0x0000   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 39 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 39 occurred at disk power-on lifetime: 19142 hours (797 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 40 10 6b 6c 40  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 40 00      00:42:44.071  READ LOG EXT
  60 40 40 00 00 00 00 00      00:42:44.101  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:42:44.097  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:42:44.096  READ FPDMA QUEUED
  61 40 40 00 00 00 00 00      00:42:44.096  WRITE FPDMA QUEUED

Error 38 occurred at disk power-on lifetime: 19142 hours (797 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 38 20 fb a2 40  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 40 00      00:11:12.428  READ LOG EXT
  60 40 40 00 00 00 00 00      00:11:12.427  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:11:12.426  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:11:12.425  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:11:12.424  READ FPDMA QUEUED

Error 37 occurred at disk power-on lifetime: 18922 hours (788 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 b8 00 bb e9 40  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 40 00      08:05:00.268  READ LOG EXT
  60 40 40 00 00 00 00 00      08:05:00.267  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      08:05:00.265  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      08:05:00.264  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      08:05:00.263  READ FPDMA QUEUED

Error 36 occurred at disk power-on lifetime: 18676 hours (778 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 40 70 91 fb 40  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 40 00      00:10:38.285  READ LOG EXT
  60 40 40 00 00 00 00 00      00:10:38.284  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:10:38.284  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:10:38.299  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:10:38.295  READ FPDMA QUEUED

Error 35 occurred at disk power-on lifetime: 18572 hours (773 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 90 08 cb a2 40  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 40 00      00:09:21.204  READ LOG EXT
  60 40 40 00 00 00 00 00      00:09:21.203  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:09:21.202  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:09:21.202  READ FPDMA QUEUED
  60 40 40 00 00 00 00 00      00:09:21.201  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Interrupted (host reset)      90%     18430         -
# 2  Short offline       Interrupted (host reset)      90%     18277         -
# 3  Short offline       Interrupted (host reset)      90%     17420         -
# 4  Short offline       Interrupted (host reset)      90%     17309         -
# 5  Short offline       Completed without error       00%     17200         -
# 6  Short offline       Completed without error       00%     17185         -
# 7  Extended offline    Completed: read failure       30%     17177         369044120
# 8  Short offline       Completed without error       00%     17174         -
# 9  Short offline       Interrupted (host reset)      90%     16977         -
#10  Extended offline    Completed: read failure       40%     16156         369044120
#11  Short offline       Completed without error       00%     16154         -
#12  Short offline       Aborted by host               10%     15880         -
#13  Short offline       Completed without error       00%     15737         -
#14  Short offline       Completed without error       00%     15442         -
#15  Short offline       Completed without error       00%     14927         -
#16  Short offline       Completed without error       00%     12722         -
#17  Short offline       Completed without error       00%     12551         -
#18  Short offline       Aborted by host               90%     12006         -
#19  Short offline       Completed without error       00%     11210         -
#20  Short offline       Completed without error       00%     10945         -
#21  Short offline       Completed without error       00%     10725         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

iznobe · Le 06/02/2023, à 06:51

Alors , on voit que ton disque a quelques heures de vol : 22 000 et des brouettes .

je ne comprends pas trop ces 2 lignes :

241 Total_LBAs_Written      0x0000   000   000   000    Old_age   Offline      -       37347314276
242 Total_LBAs_Read         0x0000   000   000   000    Old_age   Offline      -       863577

En temps normal on devrait avoir un nombre plus grand pour la lecture ( read ) que pour l' ecriture , sauf si ce disque est utilisé pour de la video surveillance et qu ' il enregistre en permanence , est ce le cas ?

Ton disque a rencontré des erreurs de type " ABRT " , au moins 5 sur un total de 39 .

ce compteur est vraiment tres gros , pas bon signe du tout :

195 Hardware_ECC_Recovered  0x0012   059   046   000    Old_age   Always       -       63917773

celui-ci devrait etre a zero :

192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       3451

probleme de connectique en general .

Mon anlyse est succinte , je ne suis pas un pro dans le domaine , il faudrait justement faire confirmer par un pro , mais je pense que ton disque est a changer . ca fait pas mal d' erreur differentes ...et de problemes potentiels .

Dernière modification par iznobe (Le 06/02/2023, à 06:53)

dellko · Le 06/02/2023, à 14:21

Bonjour Iznobe et merci pour ta lecture éclairée de ce pavé
J’ai survolé ce rapport et j’avais remarqué aussi ces erreurs ABRT , je ne sais pas si ça correspond aux fois où j’ai du éteindre manuellement le pc avec le bouton de mise en route ?
Pour le disque dur il va falloir que je regarde pour en acheter un autre avant que celui ci me lâche complètement, j’espère trouver un modèle compatible avec mon pc, que les connectiques sont standard et n’ont pas trop évolué...
Dans tous les cas, je n’investirai pas dans un SSD car je ne suis pas sûre que le processeur suive...
Bon en attendant, si un pro passe par là et a un peu de temps pour donner son avis, je suis preneuse
Ah j’allais oublier : pour répondre à ta question, j’ai testé la vidéo surveillance avec pour voir comment ça fonctionne, mais très peu au début que je l’avais

Dernière modification par dellko (Le 06/02/2023, à 14:28)

geole · Le 06/02/2023, à 16:51

Bonjour.
Je ne partage pas le pessimisme de iznobe.
Une autre vision des chiffres.

9 Power_On_Hours          0x0032   075   075   000    Old_age   Always       -       22520

Il est prévu pour fonctionner 90000 heures.

Error 39 occurred at disk power-on lifetime: 19142 hours   Error: ABRT

Cela fait quand même 3598 heures sans erreurs rencontrées. Si toutes les erreurs étaient de ce style, cela n’est pas grave. Souvent la cause est un logiciel qui expédie une commande que le firmware ne comprend pas. Soit la commande du logiciel n’ a pas de sens et il s’est mis au point ou il n’est plus utilisé. soit elle a un sens et le firmware a été mis à jour.

195 Hardware_ECC_Recovered  0x0012   059   046   000    Old_age

Je dirais que c’est en amélioration. Il fut à 46% d’efficacité, il est maintenant noté à 59%

et celui-ci est à 99%

192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age

Le maillon faible est plutôt ce compteur qui ralentit le fonctionnement du disque au quotidien.

 7 Seek_Error_Rate         0x000f   078   051   030    Pre-fail  Always

Il a tourné à 51% Peut-etre pendant sa période de surveillance active. Il est noté actuellement à 78%
Il est quand même au-dessus du seuil critique fixé à 30%
Mais ce n’est pas une raison pour diminuer la fréquence de tes sauvegardes de données personnelles

Dernière modification par geole (Le 06/02/2023, à 17:24)

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#26 Le 05/02/2023, à 14:46

Re : probleme apres mise à niveau RESOLU

#27 Le 05/02/2023, à 14:50

Re : probleme apres mise à niveau RESOLU

#28 Le 05/02/2023, à 14:59

Re : probleme apres mise à niveau RESOLU

#29 Le 05/02/2023, à 14:59

Re : probleme apres mise à niveau RESOLU

#30 Le 05/02/2023, à 15:02

Re : probleme apres mise à niveau RESOLU

#31 Le 05/02/2023, à 15:05

Re : probleme apres mise à niveau RESOLU

#32 Le 05/02/2023, à 15:08

Re : probleme apres mise à niveau RESOLU

#33 Le 05/02/2023, à 15:11

Re : probleme apres mise à niveau RESOLU

#34 Le 05/02/2023, à 15:15

Re : probleme apres mise à niveau RESOLU

#35 Le 05/02/2023, à 15:30

Re : probleme apres mise à niveau RESOLU

#36 Le 05/02/2023, à 15:51

Re : probleme apres mise à niveau RESOLU

#37 Le 05/02/2023, à 15:53

Re : probleme apres mise à niveau RESOLU

#38 Le 05/02/2023, à 15:55

Re : probleme apres mise à niveau RESOLU

#39 Le 05/02/2023, à 17:24

Re : probleme apres mise à niveau RESOLU

#40 Le 05/02/2023, à 18:13

Re : probleme apres mise à niveau RESOLU

#41 Le 05/02/2023, à 18:15

Re : probleme apres mise à niveau RESOLU

#42 Le 05/02/2023, à 18:16

Re : probleme apres mise à niveau RESOLU

#43 Le 05/02/2023, à 18:47

Re : probleme apres mise à niveau RESOLU

#44 Le 05/02/2023, à 19:16

Re : probleme apres mise à niveau RESOLU

#45 Le 05/02/2023, à 19:33

Re : probleme apres mise à niveau RESOLU

#46 Le 05/02/2023, à 19:37

Re : probleme apres mise à niveau RESOLU

#47 Le 05/02/2023, à 21:35

Re : probleme apres mise à niveau RESOLU

#48 Le 06/02/2023, à 06:51

Re : probleme apres mise à niveau RESOLU

#49 Le 06/02/2023, à 14:21

Re : probleme apres mise à niveau RESOLU

#50 Le 06/02/2023, à 16:51

Re : probleme apres mise à niveau RESOLU

Pied de page des forums