#1 Le 08/08/2023, à 23:06
- N!c0
Redémarrage intempestif: [Hardware Error]: PROCESSOR
Bonjour,
je me lance: premier post sur le forum. j'espère déjà ne pas me tromper de section...
j'ai fait une recherche sur mon problème, mais j'avoue ne pas voir trop de lien entre ce que j'ai pu lire (rapidement je l'avoue) dans les problèmes évoqués et le mien.
alors ce problème, quel est-il ?
le voici:
sans raison apparente, l'ordinateur redémarre.
je dis sans raison apparente car ce n'est pas en faisant une action spécifique que ça redémarre.
ça me l'a fait 2-3 fois déjà, pas successivement.
sauf que cette fois-ci, j'ai pensé à aller consulter le journal...
22:38:41 kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
22:38:41 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
22:38:41 gnome-session-b: GLib-CRITICAL: g_hash_table_foreach_remove_or_steal: assertion 'version == hash_table->version' failed
22:38:39 systemd: Failed to start Application launched by gnome-session-binary.
22:38:37 gdm-session-wor: gkr-pam: unable to locate daemon control file
22:38:29 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
22:38:25 kernel:
22:38:25 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1691527099 SOCKET 0 APIC 0 microcode a20120a
22:38:25 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1691527099 SOCKET 0 APIC 0 microcode a20120a
22:38:25 kernel: mce: [Hardware Error]: TSC 0
22:38:25 kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 27: faa000000000080best-ce que cet enchainement de caractère extrait du journal vous évoque quelque chose ?
merci d'avance pour votre aide.
N!c0
Dernière modification par N!c0 (Le 09/08/2023, à 20:04)
Hors ligne
#2 Le 08/08/2023, à 23:13
- xubu1957
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Bonjour,
Pour ajouter toi-même les balises code à ton précédent message #1 : Merci 
Cliquer sur le lien « Modifier » en bas à droite du message
Sélectionner le texte
Cliquer sur le <> de l'éditeur de message
Montre, en te servant du Retour utilisable de commande :
lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"ubuntu-drivers devicesuname -axrandrdpkg -l | grep nvidiadpkg -l | grep -v ^iiet :
echo $XDG_SESSION_TYPEpour voir si c'est Wayland ou x11.
Dernière modification par xubu1957 (Le 10/08/2023, à 10:10)
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#3 Le 09/08/2023, à 00:21
- geole
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Bonsoir.
22:38:25 kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 27: faa000000000080bTu pourrais booter avec le support d'installation.
Il doit y avoir une ligne proposant de lancer memtest
A faire tourner une dizaine d'heures.
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#4 Le 09/08/2023, à 20:03
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Bonjour,
ci-dessous,entre balise code, les retours des commandes proposées par xubu1957
nico@nico-X570-GAMING-X:~$ lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA102 [GeForce RTX 3090] [10de:2204] (rev a1) (prog-if 00 [VGA controller])
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidianico@nico-X570-GAMING-X:~$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:03.1/0000:09:00.0 ==
modalias : pci:v000010DEd00002204sv000019DAsd00001613bc03sc00i00
vendor : NVIDIA Corporation
model : GA102 [GeForce RTX 3090]
driver : nvidia-driver-525 - distro non-free
driver : nvidia-driver-535-server-open - distro non-free
driver : nvidia-driver-470-server - distro non-free
driver : nvidia-driver-525-server - distro non-free
driver : nvidia-driver-525-open - distro non-free
driver : nvidia-driver-470 - distro non-free
driver : nvidia-driver-535-server - distro non-free
driver : nvidia-driver-535-open - distro non-free
driver : nvidia-driver-535 - distro non-free recommended
driver : xserver-xorg-video-nouveau - distro free builtinnico@nico-X570-GAMING-X:~$ uname -a
Linux nico-X570-GAMING-X 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linuxnico@nico-X570-GAMING-X:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
1920x1080 60.00*+ 74.97 59.94 50.00
1680x1050 59.95
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x720 60.00 59.94 50.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 72.81 59.94 59.93
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)nico@nico-X570-GAMING-X:~$ dpkg -l | grep nvidia
ii libnvidia-cfg1-535:amd64 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA binary OpenGL/GLX configuration library
ii libnvidia-common-535 535.86.05-0ubuntu0.22.04.1 all Shared files used by the NVIDIA libraries
ii libnvidia-compute-535:amd64 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA libcompute package
ii libnvidia-compute-535:i386 535.86.05-0ubuntu0.22.04.1 i386 NVIDIA libcompute package
ii libnvidia-decode-535:amd64 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA Video Decoding runtime libraries
ii libnvidia-decode-535:i386 535.86.05-0ubuntu0.22.04.1 i386 NVIDIA Video Decoding runtime libraries
ii libnvidia-encode-535:amd64 535.86.05-0ubuntu0.22.04.1 amd64 NVENC Video Encoding runtime library
ii libnvidia-encode-535:i386 535.86.05-0ubuntu0.22.04.1 i386 NVENC Video Encoding runtime library
ii libnvidia-extra-535:amd64 535.86.05-0ubuntu0.22.04.1 amd64 Extra libraries for the NVIDIA driver
ii libnvidia-fbc1-535:amd64 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-fbc1-535:i386 535.86.05-0ubuntu0.22.04.1 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-gl-535:amd64 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-gl-535:i386 535.86.05-0ubuntu0.22.04.1 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii linux-modules-nvidia-535-6.2.0-26-generic 6.2.0-26.26~22.04.1+2 amd64 Linux kernel nvidia modules for version 6.2.0-26
ii linux-modules-nvidia-535-generic-hwe-22.04 6.2.0-26.26~22.04.1+2 amd64 Extra drivers for nvidia-535 for the generic-hwe-22.04 flavour
ii linux-objects-nvidia-535-6.2.0-26-generic 6.2.0-26.26~22.04.1+2 amd64 Linux kernel nvidia modules for version 6.2.0-26 (objects)
ii linux-signatures-nvidia-6.2.0-26-generic 6.2.0-26.26~22.04.1+2 amd64 Linux kernel signatures for nvidia modules for version 6.2.0-26-generic
ii nvidia-compute-utils-535 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA compute utilities
ii nvidia-dkms-535 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA DKMS package
ii nvidia-driver-535 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA driver metapackage
ii nvidia-firmware-535-535.86.05 535.86.05-0ubuntu0.22.04.1 amd64 Firmware files used by the kernel module
ii nvidia-kernel-common-535 535.86.05-0ubuntu0.22.04.1 amd64 Shared files used with the kernel module
ii nvidia-kernel-source-535 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA kernel source package
ii nvidia-prime 0.8.17.1 all Tools to enable NVIDIA's Prime
ii nvidia-settings 510.47.03-0ubuntu1 amd64 Tool for configuring the NVIDIA graphics driver
ii nvidia-utils-535 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA driver support binaries
ii screen-resolution-extra 0.18.2 all Extension for the nvidia-settings control panel
ii xserver-xorg-video-nvidia-535 535.86.05-0ubuntu0.22.04.1 amd64 NVIDIA binary Xorg drivernico@nico-X570-GAMING-X:~$ dpkg -l | grep -v ^ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version Architecture Description
+++-============================================-==========================================-============-================================================================================
rc game-data-packager 68 all Installer for game data filesnico@nico-X570-GAMING-X:~$ echo $XDG_SESSION_TYPE
x11la réponse de la dernière commande me parait bizarre (on dirait qu'il y a comme une erreur dans la commande). j'ai relancé la commande comme-ci,
nico@nico-X570-GAMING-X:~$ dpkg -l | grep -v ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version Architecture Description
+++-============================================-==========================================-============-================================================================================
rc game-data-packager 68 all Installer for game data filessans que le résultat soit plus probant...à mes yeux de novice
A+
Hors ligne
#5 Le 09/08/2023, à 20:06
- xubu1957
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Pour purger le résidu de configuration marqué "rc" :
sudo apt purge ~ccomme expliqué à la machine à café et rajouté dans ce message
As-tu moyen de changer de session avec la roue crantée, pour tester avec wayland ?
Regarde l'EDIT de malbo dans ce message, pour la roue crantée.
Donne aussi la liste des anomalies de démarrage :
journalctl --no-pager -b -p erret :
ls -l /var/crashDernière modification par xubu1957 (Le 09/08/2023, à 20:06)
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#6 Le 09/08/2023, à 22:46
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
pour la roue crantée, je ne peux pas le faire...je n'ai pas cette roue...
ou alors c'est uniquement lors du démarrage, et pas simplement en vérrouillant la session.
je fais le test
ci-dessous les retours utilisables des commandes
nico@nico-X570-GAMING-X:~$ journalctl --no-pager -b -p err
août 09 12:37:53 nico-X570-GAMING-X kernel:
août 09 12:37:53 nico-X570-GAMING-X kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
août 09 12:37:55 nico-X570-GAMING-X gnome-session-binary[1389]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
août 09 12:37:55 nico-X570-GAMING-X gnome-session-binary[1389]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
août 09 12:38:12 nico-X570-GAMING-X gdm-password][1753]: gkr-pam: unable to locate daemon control file
août 09 12:38:13 nico-X570-GAMING-X systemd[1859]: Failed to start Application launched by gnome-session-binary.
août 09 12:38:13 nico-X570-GAMING-X systemd[1859]: Failed to start Application launched by gnome-session-binary.
août 09 12:38:15 nico-X570-GAMING-X gnome-session-binary[1389]: GLib-CRITICAL: g_hash_table_foreach_remove_or_steal: assertion 'version == hash_table->version' failed
août 09 12:38:15 nico-X570-GAMING-X gdm-launch-environment][1230]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 12:38:15 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:03 nico-X570-GAMING-X kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
août 09 20:18:18 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:18 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:18 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:18 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:20 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:20 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:20 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:20 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:31 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:31 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:31 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 20:18:31 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:06 nico-X570-GAMING-X gnome-session-binary[22077]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
août 09 22:38:06 nico-X570-GAMING-X gnome-session-binary[22077]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
août 09 22:38:11 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:11 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:11 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:11 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:18 nico-X570-GAMING-X gdm3[1218]: GLib: Source ID 81 was not found when attempting to remove it
août 09 22:38:27 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:27 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:27 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:27 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X gdm-launch-environment][21921]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
août 09 22:38:29 nico-X570-GAMING-X kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownershipwoaw !!
et encore, je n'ai pas eu de "plantage" aujourd'hui.
et l'autre commande:
nico@nico-X570-GAMING-X:~$ ls -l /var/crash
total 24616
-rw-r----- 1 nico whoopsie 16316912 août 8 23:12 _usr_bin_mozillavpn.1000.crash
-rw-rw-r-- 1 nico whoopsie 0 août 8 23:12 _usr_bin_mozillavpn.1000.upload
-rw------- 1 whoopsie whoopsie 37 août 8 23:12 _usr_bin_mozillavpn.1000.uploaded
-rw-r----- 1 nico whoopsie 8754087 août 7 10:08 _usr_bin_remmina.1000.crash
-rw-rw-r-- 1 nico whoopsie 0 août 7 10:08 _usr_bin_remmina.1000.upload
-rw------- 1 whoopsie whoopsie 37 août 7 10:08 _usr_bin_remmina.1000.uploaded
-rw-r----- 1 nico whoopsie 117650 août 8 13:16 _usr_share_playonlinux_python_mainwindow.py.1000.crash
-rw-rw-r-- 1 nico whoopsie 0 août 8 13:16 _usr_share_playonlinux_python_mainwindow.py.1000.upload
-rw------- 1 whoopsie whoopsie 37 août 8 13:16 _usr_share_playonlinux_python_mainwindow.py.1000.uploadedHors ligne
#7 Le 09/08/2023, à 22:49
- xubu1957
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Le 24/04/2023, nany a écrit :
Bonjour,
La roue crantée n’apparaît que lorsqu’on clique sur le nom d’utilisateur.
Écran d’accueil avant clic.
Écran d’accueil après clic.
La roue crantée se trouve en bas à droite.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#8 Le 09/08/2023, à 22:54
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
après avoir connecté mes 2 neuronnes, j'ai pu basculer sur Wayland
nico@nico-X570-GAMING-X:~$ echo $XDG_SESSION_TYPE
waylandpour ce qui est des redémarrages intempestifs, c'est parce que j'utilise le protocole X11 ?
avec Wayland, "tout est réglé" ?
Hors ligne
#9 Le 09/08/2023, à 23:07
- xubu1957
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
C'est à tester comme indiqué dans la discussion initiée par malbo.
Si l'informatique était simple, notre forum déjà serait moins utilisé. 
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#10 Le 10/08/2023, à 08:35
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
ça marche.
je ferai un retour d'ici quelques jours
merci !
Hors ligne
#11 Le 10/08/2023, à 18:42
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
petit retour sur le passage de X11 à Wayland -> ça me fait ramer et me "force à quitter" le jeu Assaultcube (pas de commentaires désobligeant s'il vous plait 
)
en repassant sur X11. plus de soucis avec Assaultcube.
Hors ligne
#12 Le 12/08/2023, à 14:14
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
salut à tous,
2ème petit retour: (en mettant de côte le passage de Wayland vers X11 pour jouer à assaultcube - voir post #11)
j'ai un autre symptôme lié à l'affichage
explication:
il m'arrive de mettre en veille moi-même ma session.
Lorsque je veux sortir de veille, des problèmes d'affichages plus ou moins étendus apparaissent.
Ca donne l'impression que des zones de l'écran sont allumées en même que d'autres sont éteintes. les zones allumées sont parfaitement nettes. Celles éteintes sont parfaitement éteintes. Ce n'est pas un pixel par-ci par-là. Je ne vois pas forcément le curseur. ou alors, que sur certains zones. Tant bien que mal j'arrive à me loguer (en me déplaçant au clavier). La session se déverrouille (sans lenteur, ni problème particulier), mais toujours avec ces zones manquantes et ces zones "normales".
pour corriger le problème. je n'ai pas trouvé d'autre solution que de fermer la session. Avant de me loguer, je vérifie (sur la roue crantée) que je suis bien sur Wayland...et tout rentre dans l'ordre. En apparence du moins
A noter que j'ai un message d'erreur provenant de mozillavpn. peut-être n'aime-t-il pas la fermeture "brutale" de la session.
Ubuntu me propose d'envoyer un rapport aux développeurs. ce que je voudrais faire, mais, sans succès. "vérifier votre connexion internet"....
pour info, ci-dessous, le retour de
nico@nico-X570-GAMING-X:~$ printenv | lessSHELL=/bin/bash
SESSION_MANAGER=local/nico-X570-GAMING-X:@/tmp/.ICE-unix/15395,unix/nico-X570-GAMING-X:/tmp/.ICE-unix/15395
QT_ACCESSIBILITY=1
COLORTERM=truecolor
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu-wayland:/etc/xdg
SSH_AGENT_LAUNCHER=gnome-keyring
XDG_MENU_PREFIX=gnome-
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GNOME_SHELL_SESSION_MODE=ubuntu
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
XMODIFIERS=@im=ibus
DESKTOP_SESSION=ubuntu-wayland
GTK_MODULES=gail:atk-bridge
PWD=/home/nico
LOGNAME=nico
XDG_SESSION_DESKTOP=ubuntu-wayland
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=15531
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.LE1O91
HOME=/home/nico
USERNAME=nico
IM_CONFIG_PHASE=1
LANG=fr_FR.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
XDG_CURRENT_DESKTOP=ubuntu:GNOME
VTE_VERSION=6800
WAYLAND_DISPLAY=wayland-0
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/751191aa_798d_484e_939a_057c90e98533
GNOME_SETUP_DISPLAY=:2
LESSCLOSE=/usr/bin/lesspipe %s %s
XDG_SESSION_CLASS=user
TERM=xterm-256color
LESSOPEN=| /usr/bin/lesspipe %s
USER=nico
GNOME_TERMINAL_SERVICE=:1.137
DISPLAY=:1
SHLVL=0
QT_IM_MODULE=ibus
XDG_RUNTIME_DIR=/run/user/1000
XDG_DATA_DIRS=/usr/share/ubuntu-wayland:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin
GDMSESSION=ubuntu-wayland
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
_=/usr/bin/printenv
~et aussi le journal
13:40:15 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
13:40:14 systemd: Failed to start Application launched by gnome-session-binary.
13:40:14 systemd: Failed to start Application launched by gnome-session-binary.
13:40:14 systemd: Failed to start Application launched by gnome-session-binary.
13:40:12 gdm-session-wor: gkr-pam: unable to locate daemon control file
13:39:53 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
13:39:53 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
13:39:53 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
13:38:13 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
13:38:13 gdm3: GLib: Source ID 161 was not found when attempting to remove it
13:27:22 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
13:27:22 gnome-session-b: GLib-CRITICAL: g_hash_table_foreach_remove_or_steal: assertion 'version == hash_table->version' failed
13:27:20 systemd: Failed to start Application launched by gnome-session-binary.
13:27:20 systemd: Failed to start Application launched by gnome-session-binary.
13:27:20 systemd: Failed to start Application launched by gnome-session-binary.
13:27:19 gdm-session-wor: gkr-pam: unable to locate daemon control file
13:27:04 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
13:27:04 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
13:27:04 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
13:26:18 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
11:04:24 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:04:23 systemd: Failed to start Application launched by gnome-session-binary.
11:04:23 systemd: Failed to start Application launched by gnome-session-binary.
11:04:23 systemd: Failed to start Application launched by gnome-session-binary.
11:04:22 systemd: Failed to start Application launched by gnome-session-binary.
11:04:22 systemd: Failed to start Application launched by gnome-session-binary.
11:04:21 gdm-session-wor: gkr-pam: unable to locate daemon control file
11:04:06 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
11:04:06 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
11:04:06 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
11:04:00 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:03:59 systemd: Failed to start Application launched by gnome-session-binary.
11:03:59 systemd: Failed to start Application launched by gnome-session-binary.
11:03:58 systemd: Failed to start Application launched by gnome-session-binary.
11:03:58 systemd: Failed to start Application launched by gnome-session-binary.
11:03:58 systemd: Failed to start Application launched by gnome-session-binary.
11:03:57 gdm-session-wor: gkr-pam: unable to locate daemon control file
11:03:46 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
11:03:46 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
11:03:46 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
11:03:44 kernel:
11:03:43 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1691831018 SOCKET 0 APIC b microcode a20120a
11:03:43 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1691831018 SOCKET 0 APIC b microcode a20120a
11:03:43 kernel: mce: [Hardware Error]: TSC 0
11:03:43 kernel: mce: [Hardware Error]: CPU 17: Machine Check: 0 Bank 0: fc00080001010135merci pour votre aide.
Dernière modification par N!c0 (Le 12/08/2023, à 14:15)
Hors ligne
#13 Le 12/08/2023, à 14:19
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
@geole
désolé, mais vu mon niveau, est-ce que tu peux m'expliquer plus concrètement comment faire ceci ?
geole a écrit :
Bonsoir.
22:38:25 kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 27: faa000000000080bTu pourrais booter avec le support d'installation.
Il doit y avoir une ligne proposant de lancer memtest
A faire tourner une dizaine d'heures.
j'ai bien tenté de démarrer sur la clé-live usb, mais pas de memtest en vue.
j'ai
"try or install ubuntu"
"OEM for manufacturer"
un truc qui me parle d'UEFI.
Dernière modification par N!c0 (Le 12/08/2023, à 14:27)
Hors ligne
#14 Le 12/08/2023, à 14:19
- xubu1957
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Bonjour,
Si tu veux tenter la commande de nany, en l'adaptant.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#15 Le 12/08/2023, à 15:11
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
bonjour,
xubu1957 a écrit :
Bonjour,
Si tu veux tenter la commande de nany, en l'adaptant.
j'ai ouvert une nouvelle discussion (https://forum.ubuntu-fr.org/viewtopic.p … #p22699644) pour ne pas mélanger les 2 sujets: le "non-envoie" des rapports et les plantages d'affichage
d'ailleurs, mon post #12, il évoque quelque chose à quelqu'un ?
Hors ligne
#16 Le 12/08/2023, à 15:29
- xubu1957
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
En cherchant avec :
PROCESSOR "2:a20f12" TIME SOCKET 0 APIC b microcode a20120aje trouve forum.proxmox.com/threads/proxmox-random-crashes-please-help et forums.unraid.net/topic/140308-consant-crashes-on-gpu-usage-with-ryzen 
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#17 Le 12/08/2023, à 15:45
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
ce que je comprends (je suis à peine plutôt doué en anglais qu'en informatique) c'est que le point commun entre eux et moi, c'est le processeur et un comportement qui ressemble assez à ce que je "subis"
mon problème viendrait donc du processeur? et non pas de la carte graphique ?
Hors ligne
#18 Le 12/08/2023, à 16:16
- xubu1957
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Je trouve Hardware Error “mce” indiquant ces deux liens > askubuntu.com/questions/605369/mce-hardware-error-machine-check-events-logged-appears-in-syslog-what-should I do? et bugzilla.redhat.com/show_bug.cgi?id=1467040.
Et c'est pas à ma portée.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#19 Le 12/08/2023, à 17:42
- geole
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
N!c0 a écrit :
j'ai bien tenté de démarrer sur la clé-live usb, mais pas de memtest en vue. j'ai
"try or install ubuntu"
"OEM for manufacturer"
un truc qui me parle d'UEFI.
Bonjour
Donc le support livré ne contient plus memtest.
Habituellement, je fais la clé de boot avec ventoy, je n'ai donc qu'un copié collé de l'iso à faire.
Voici un lien qui indique comment obtenir une nouvelle version.
Cela pointe donc A cet endroit
Habituellement, je prends cette version que je dézippe puis je copie l'ISO dans la partition ventoy.... et le tour est joué.
Je vois qu'il y a aussi une version GRUB
Mais il faudrait que je cherche comme faire après.
Dernière modification par geole (Le 12/08/2023, à 17:47)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#20 Le 14/08/2023, à 10:53
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
salut,
j'ai réussi (y'a pas de petite victoire...) à faire le memtest via ventoy, comme me l'indiqué Geole.
je pensais pas en effet qu'il serait nécessaire de faire tourner le test aussi longtemps, et pourtant...
au bout de 20h (...), le test s'étant déroulé sans erreur , mais avec des "pass", au nombre de 7, et le statut étant lui-même passé de "testing" à "pass", j'en ai conclu que le test était terminé, mais qu'il ne s'arrêterait qu'à ma demande.
j'ai donc quitté le test, sans avoir pu enregistrer de rapport . Peut-être se trouve-t-il quelque part ?
bref, à mes yeux, rien d'anormal à signaler à l'issue du memtest.
Hors ligne
#21 Le 14/08/2023, à 11:07
- geole
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Bonjour.
C'est rassurant. Le problème serait donc uniquement logiciel.
S'il a des erreurs rencontrées, c'est uniquement signalé en rouge à l'écran.
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#22 Le 14/08/2023, à 17:31
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
salut,
oui c'est rassurant.
en revanche, ça ne vient pas du Wayland ou X11: aujourd'hui, sous Wayland, j'ai eu droit à un redémarrage.
Hors ligne
#23 Le 14/08/2023, à 19:12
- geole
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Donne ce retour
journalctl --no-pager -b -1 -n 1500Dernière modification par geole (Le 14/08/2023, à 19:13)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#24 Le 15/08/2023, à 07:10
- N!c0
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
et voici
nico@nico-X570-GAMING-X:~$ journalctl --no-pager -b -1 -n 1500
août 14 17:11:21 nico-X570-GAMING-X kernel: usb 1-3: new high-speed USB device number 12 using xhci_hcd
août 14 17:11:22 nico-X570-GAMING-X kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.00
août 14 17:11:22 nico-X570-GAMING-X kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
août 14 17:11:22 nico-X570-GAMING-X kernel: usb 1-3: Product: Flash Disk
août 14 17:11:22 nico-X570-GAMING-X kernel: usb 1-3: Manufacturer: USB
août 14 17:11:22 nico-X570-GAMING-X kernel: usb 1-3: SerialNumber: 5AB6BC00
août 14 17:11:22 nico-X570-GAMING-X kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
août 14 17:11:22 nico-X570-GAMING-X kernel: scsi host11: usb-storage 1-3:1.0
août 14 17:11:22 nico-X570-GAMING-X mtp-probe[16322]: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:11:22 nico-X570-GAMING-X mtp-probe[16322]: bus: 1, device: 12 was not an MTP device
août 14 17:11:22 nico-X570-GAMING-X mtp-probe[16324]: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:11:22 nico-X570-GAMING-X mtp-probe[16324]: bus: 1, device: 12 was not an MTP device
août 14 17:11:23 nico-X570-GAMING-X kernel: scsi 11:0:0:0: Direct-Access USB Flash Disk 8.07 PQ: 0 ANSI: 4
août 14 17:11:23 nico-X570-GAMING-X kernel: sd 11:0:0:0: Attached scsi generic sg3 type 0
août 14 17:11:23 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] 15605760 512-byte logical blocks: (7.99 GB/7.44 GiB)
août 14 17:11:23 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write Protect is off
août 14 17:11:23 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Mode Sense: 23 00 00 00
août 14 17:11:23 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
août 14 17:11:23 nico-X570-GAMING-X kernel: sdb: sdb1 sdb2
août 14 17:11:23 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Attached SCSI removable disk
août 14 17:11:23 nico-X570-GAMING-X systemd-udevd[16334]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
août 14 17:11:23 nico-X570-GAMING-X systemd-udevd[16334]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1.
août 14 17:11:23 nico-X570-GAMING-X systemd-udevd[16332]: sdb2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb2' failed with exit code 1.
août 14 17:11:23 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): warning: mounting unchecked fs, running e2fsck is recommended
août 14 17:11:23 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): mounted filesystem 8666a128-0766-11ee-968f-287fcfeb4376 without journal. Quota mode: none.
août 14 17:11:26 nico-X570-GAMING-X kernel: usb 1-3: USB disconnect, device number 12
août 14 17:11:26 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:11:26 nico-X570-GAMING-X kernel: device offline error, dev sdb, sector 278528 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2
août 14 17:11:26 nico-X570-GAMING-X kernel: Buffer I/O error on dev sdb2, logical block 32768, lost sync page write
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2) in ext4_update_backup_sb:173: IO failure
août 14 17:11:26 nico-X570-GAMING-X kernel: device offline error, dev sdb, sector 16384 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2
août 14 17:11:26 nico-X570-GAMING-X kernel: Buffer I/O error on dev sdb2, logical block 0, lost sync page write
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): I/O error while writing superblock
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): Remounting filesystem read-only
août 14 17:11:26 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692025886.366:88): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:11:26 nico-X570-GAMING-X kernel: device offline error, dev sdb, sector 43064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1662: inode #2: comm gvfsd-trash: reading directory lblock 0
août 14 17:11:26 nico-X570-GAMING-X kernel: device offline error, dev sdb, sector 16384 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2
août 14 17:11:26 nico-X570-GAMING-X kernel: Buffer I/O error on dev sdb2, logical block 0, lost sync page write
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): I/O error while writing superblock
août 14 17:11:26 nico-X570-GAMING-X kernel: device offline error, dev sdb, sector 43064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1662: inode #2: comm gvfsd-trash: reading directory lblock 0
août 14 17:11:26 nico-X570-GAMING-X kernel: device offline error, dev sdb, sector 16384 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2
août 14 17:11:26 nico-X570-GAMING-X kernel: Buffer I/O error on dev sdb2, logical block 0, lost sync page write
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): I/O error while writing superblock
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1662: inode #2: comm pool: reading directory lblock 0
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1662: inode #2: comm pool: reading directory lblock 0
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1662: inode #2: comm pool: reading directory lblock 0
août 14 17:11:26 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692025886.394:89): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:11:26 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): unmounting filesystem 8666a128-0766-11ee-968f-287fcfeb4376.
août 14 17:11:26 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:11:26 nico-X570-GAMING-X udisksd[854]: Mounted /dev/sdb2 at /media/nico/easy2 on behalf of uid 1000
août 14 17:11:26 nico-X570-GAMING-X udisksd[854]: Error opening /sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3/1-3:1.0/host11/target11:0:0/11:0:0:0/block/sdb/sdb2/uevent while triggering uevent: No such file or directory
août 14 17:11:26 nico-X570-GAMING-X udisksd[854]: Error opening /sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3/1-3:1.0/host11/target11:0:0/11:0:0:0/block/sdb/sdb2/uevent while triggering uevent: No such file or directory
août 14 17:11:26 nico-X570-GAMING-X udisksd[854]: Cleaning up mount point /media/nico/easy2 (device 8:18 no longer exists)
août 14 17:11:26 nico-X570-GAMING-X systemd[1]: media-nico-easy2.mount: Deactivated successfully.
août 14 17:11:26 nico-X570-GAMING-X kernel: usb 1-3: new high-speed USB device number 13 using xhci_hcd
août 14 17:11:27 nico-X570-GAMING-X kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=1234, bcdDevice= 0.01
août 14 17:11:27 nico-X570-GAMING-X kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
août 14 17:11:27 nico-X570-GAMING-X kernel: usb 1-3: Product: Mass Storage Device
août 14 17:11:27 nico-X570-GAMING-X kernel: usb 1-3: Manufacturer: Alcor Micro
août 14 17:11:27 nico-X570-GAMING-X kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
août 14 17:11:27 nico-X570-GAMING-X kernel: scsi host11: usb-storage 1-3:1.0
août 14 17:11:27 nico-X570-GAMING-X mtp-probe[16385]: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:11:27 nico-X570-GAMING-X mtp-probe[16385]: bus: 1, device: 13 was not an MTP device
août 14 17:11:27 nico-X570-GAMING-X mtp-probe[16387]: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:11:27 nico-X570-GAMING-X mtp-probe[16387]: bus: 1, device: 13 was not an MTP device
août 14 17:11:28 nico-X570-GAMING-X kernel: scsi 11:0:0:0: Direct-Access Generic USB Flash Disk 7.76 PQ: 0 ANSI: 4
août 14 17:11:28 nico-X570-GAMING-X kernel: sd 11:0:0:0: Attached scsi generic sg3 type 0
août 14 17:11:28 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Media removed, stopped polling
août 14 17:11:28 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Attached SCSI removable disk
août 14 17:11:28 nico-X570-GAMING-X systemd-udevd[16321]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
août 14 17:11:49 nico-X570-GAMING-X kernel: usb 1-3: USB disconnect, device number 13
août 14 17:11:53 nico-X570-GAMING-X kernel: usb 1-3: new high-speed USB device number 14 using xhci_hcd
août 14 17:11:53 nico-X570-GAMING-X kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.00
août 14 17:11:53 nico-X570-GAMING-X kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
août 14 17:11:53 nico-X570-GAMING-X kernel: usb 1-3: Product: Flash Disk
août 14 17:11:53 nico-X570-GAMING-X kernel: usb 1-3: Manufacturer: USB
août 14 17:11:53 nico-X570-GAMING-X kernel: usb 1-3: SerialNumber: 5AB6BC00
août 14 17:11:53 nico-X570-GAMING-X kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
août 14 17:11:53 nico-X570-GAMING-X kernel: scsi host11: usb-storage 1-3:1.0
août 14 17:11:53 nico-X570-GAMING-X mtp-probe[16423]: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:11:53 nico-X570-GAMING-X mtp-probe[16423]: bus: 1, device: 14 was not an MTP device
août 14 17:11:53 nico-X570-GAMING-X mtp-probe[16427]: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:11:53 nico-X570-GAMING-X mtp-probe[16427]: bus: 1, device: 14 was not an MTP device
août 14 17:11:54 nico-X570-GAMING-X kernel: scsi 11:0:0:0: Direct-Access USB Flash Disk 8.07 PQ: 0 ANSI: 4
août 14 17:11:54 nico-X570-GAMING-X kernel: sd 11:0:0:0: Attached scsi generic sg3 type 0
août 14 17:11:54 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] 15605760 512-byte logical blocks: (7.99 GB/7.44 GiB)
août 14 17:11:54 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write Protect is off
août 14 17:11:54 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Mode Sense: 23 00 00 00
août 14 17:11:54 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
août 14 17:11:54 nico-X570-GAMING-X kernel: sdb: sdb1 sdb2
août 14 17:11:54 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Attached SCSI removable disk
août 14 17:11:54 nico-X570-GAMING-X systemd-udevd[16408]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
août 14 17:11:54 nico-X570-GAMING-X systemd-udevd[16408]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1.
août 14 17:11:54 nico-X570-GAMING-X systemd-udevd[16406]: sdb2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb2' failed with exit code 1.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): warning: mounting unchecked fs, running e2fsck is recommended
août 14 17:11:54 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): mounted filesystem 8666a128-0766-11ee-968f-287fcfeb4376 without journal. Quota mode: none.
août 14 17:11:54 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692025914.637:90): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfsd-trash: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1673: inode #2: comm gvfsd-trash: checksumming directory block 0
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm pool: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1673: inode #2: comm pool: checksumming directory block 0
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm pool: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1673: inode #2: comm pool: checksumming directory block 0
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfs-udisks2-vo: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): htree_dirblock_to_tree:1072: inode #2: comm gvfs-udisks2-vo: Directory block failed checksum
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): Remounting filesystem read-only
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfs-udisks2-vo: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfsd-trash: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): htree_dirblock_to_tree:1072: inode #2: comm gvfs-udisks2-vo: Directory block failed checksum
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): __ext4_find_entry:1673: inode #2: comm gvfsd-trash: checksumming directory block 0
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfs-udisks2-vo: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): htree_dirblock_to_tree:1072: inode #2: comm gvfs-udisks2-vo: Directory block failed checksum
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfs-udisks2-vo: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): htree_dirblock_to_tree:1072: inode #2: comm gvfs-udisks2-vo: Directory block failed checksum
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfs-udisks2-vo: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): htree_dirblock_to_tree:1072: inode #2: comm gvfs-udisks2-vo: Directory block failed checksum
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs warning (device sdb2): ext4_dirblock_csum_verify:404: inode #2: comm gvfs-udisks2-vo: No space for directory leaf checksum. Please run e2fsck -D.
août 14 17:11:54 nico-X570-GAMING-X kernel: EXT4-fs error (device sdb2): htree_dirblock_to_tree:1072: inode #2: comm gvfs-udisks2-vo: Directory block failed checksum
août 14 17:11:54 nico-X570-GAMING-X udisksd[854]: Mounted /dev/sdb2 at /media/nico/easy2 on behalf of uid 1000
août 14 17:11:54 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Activating service name='org.gnome.Shell.HotplugSniffer' requested by ':1.38' (uid=1000 pid=1972 comm="/usr/bin/gnome-shell " label="unconfined")
août 14 17:11:54 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: libEGL warning: egl: failed to create dri2 screen
août 14 17:12:14 nico-X570-GAMING-X gnome-shell[1972]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16538]: libEGL warning: egl: failed to create dri2 screen
août 14 17:12:14 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:12:14 nico-X570-GAMING-X rtkit-daemon[1312]: Successfully made thread 16557 of process 16538 owned by '1000' RT at priority 5.
août 14 17:12:14 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 7 threads of 5 processes of 1 users.
août 14 17:12:14 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 7 threads of 5 processes of 1 users.
août 14 17:12:14 nico-X570-GAMING-X rtkit-daemon[1312]: Successfully made thread 16613 of process 16538 owned by '1000' RT at priority 5.
août 14 17:12:14 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 8 threads of 5 processes of 1 users.
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating blue bg color. Using rgb(253,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating dark bg color. Using rgb(253,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating purple fg color. Using rgb(45,21,53)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating yellow bg color. Using rgb(253,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating gray bg color. Using rgb(253,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating red bg color. Using rgb(253,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating blue fg color. Using rgb(15,37,65)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating red fg color. Using rgb(55,9,12)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating orange fg color. Using rgb(72,45,21)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating orange bg color. Using rgb(255,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating dark fg color. Using rgb(55,55,53)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating yellow fg color. Using rgb(69,65,27)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating green bg color. Using rgb(253,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating gray fg color. Using rgb(55,55,53)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating purple bg color. Using rgb(253,253,253)
août 14 17:12:14 nico-X570-GAMING-X org.gnome.Nautilus[16521]: Recursion depth exceeded calculating green fg color. Using rgb(24,64,39)
août 14 17:12:39 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:12:39 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692025959.385:91): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:12:39 nico-X570-GAMING-X kernel: EXT4-fs (sdb2): unmounting filesystem 8666a128-0766-11ee-968f-287fcfeb4376.
août 14 17:12:39 nico-X570-GAMING-X systemd[1]: media-nico-easy2.mount: Deactivated successfully.
août 14 17:12:39 nico-X570-GAMING-X udisksd[854]: Cleaning up mount point /media/nico/easy2 (device 8:18 is not mounted)
août 14 17:12:39 nico-X570-GAMING-X udisksd[854]: Unmounted /dev/sdb2 on behalf of uid 1000
août 14 17:12:42 nico-X570-GAMING-X udisksd[854]: Error issuing BLKRRPART to /dev/sdb2: Invalid argument
août 14 17:12:52 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.171' (uid=1000 pid=6845 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
août 14 17:12:52 nico-X570-GAMING-X systemd[1]: Starting Hostname Service...
août 14 17:12:52 nico-X570-GAMING-X dbus-daemon[804]: [system] Successfully activated service 'org.freedesktop.hostname1'
août 14 17:12:52 nico-X570-GAMING-X systemd[1]: Started Hostname Service.
août 14 17:12:52 nico-X570-GAMING-X audit[804]: USER_AVC pid=804 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.333" pid=5600 label="snap.firefox.firefox" peer_pid=16648 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
août 14 17:12:52 nico-X570-GAMING-X kernel: audit: type=1107 audit(1692025972.206:92): pid=804 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.333" pid=5600 label="snap.firefox.firefox" peer_pid=16648 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
août 14 17:12:53 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:12:53 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692025973.470:93): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:12:53 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Activating service name='org.gnome.Shell.HotplugSniffer' requested by ':1.38' (uid=1000 pid=1972 comm="/usr/bin/gnome-shell " label="unconfined")
août 14 17:12:53 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
août 14 17:12:53 nico-X570-GAMING-X udisksd[854]: Mounted /dev/sdb2 at /media/nico/TTL_436 on behalf of uid 1000
août 14 17:12:53 nico-X570-GAMING-X nautilus[6845]: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed
août 14 17:13:08 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:13:08 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692025988.252:94): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:13:08 nico-X570-GAMING-X systemd[1]: media-nico-TTL_436.mount: Deactivated successfully.
août 14 17:13:08 nico-X570-GAMING-X udisksd[854]: Cleaning up mount point /media/nico/TTL_436 (device 8:18 is not mounted)
août 14 17:13:08 nico-X570-GAMING-X udisksd[854]: Unmounted /dev/sdb2 on behalf of uid 1000
août 14 17:13:08 nico-X570-GAMING-X kernel: sdb: detected capacity change from 15605760 to 0
août 14 17:13:15 nico-X570-GAMING-X kernel: usb 1-3: USB disconnect, device number 14
août 14 17:13:22 nico-X570-GAMING-X systemd[1]: systemd-hostnamed.service: Deactivated successfully.
août 14 17:17:01 nico-X570-GAMING-X CRON[16716]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
août 14 17:17:01 nico-X570-GAMING-X CRON[16717]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
août 14 17:17:01 nico-X570-GAMING-X CRON[16716]: pam_unix(cron:session): session closed for user root
août 14 17:18:51 nico-X570-GAMING-X kernel: usb 1-3: new high-speed USB device number 15 using xhci_hcd
août 14 17:18:52 nico-X570-GAMING-X kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.00
août 14 17:18:52 nico-X570-GAMING-X kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
août 14 17:18:52 nico-X570-GAMING-X kernel: usb 1-3: Product: Flash Disk
août 14 17:18:52 nico-X570-GAMING-X kernel: usb 1-3: Manufacturer: USB
août 14 17:18:52 nico-X570-GAMING-X kernel: usb 1-3: SerialNumber: 5AB6BC00
août 14 17:18:52 nico-X570-GAMING-X kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
août 14 17:18:52 nico-X570-GAMING-X kernel: scsi host11: usb-storage 1-3:1.0
août 14 17:18:52 nico-X570-GAMING-X mtp-probe[16726]: checking bus 1, device 15: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:18:52 nico-X570-GAMING-X mtp-probe[16726]: bus: 1, device: 15 was not an MTP device
août 14 17:18:52 nico-X570-GAMING-X mtp-probe[16728]: checking bus 1, device 15: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:18:52 nico-X570-GAMING-X mtp-probe[16728]: bus: 1, device: 15 was not an MTP device
août 14 17:18:53 nico-X570-GAMING-X kernel: scsi 11:0:0:0: Direct-Access USB Flash Disk 8.07 PQ: 0 ANSI: 4
août 14 17:18:53 nico-X570-GAMING-X kernel: sd 11:0:0:0: Attached scsi generic sg3 type 0
août 14 17:18:53 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] 15605760 512-byte logical blocks: (7.99 GB/7.44 GiB)
août 14 17:18:53 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write Protect is off
août 14 17:18:53 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Mode Sense: 23 00 00 00
août 14 17:18:53 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
août 14 17:18:53 nico-X570-GAMING-X kernel: sdb: sdb1 sdb2
août 14 17:18:53 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Attached SCSI removable disk
août 14 17:18:53 nico-X570-GAMING-X systemd-udevd[16724]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
août 14 17:18:53 nico-X570-GAMING-X systemd-udevd[16724]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1.
août 14 17:18:53 nico-X570-GAMING-X systemd-udevd[16739]: sdb2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb2' failed with exit code 1.
août 14 17:18:53 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:18:53 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692026333.366:95): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:18:53 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Activating service name='org.gnome.Shell.HotplugSniffer' requested by ':1.38' (uid=1000 pid=1972 comm="/usr/bin/gnome-shell " label="unconfined")
août 14 17:18:53 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
août 14 17:18:53 nico-X570-GAMING-X udisksd[854]: Mounted /dev/sdb2 at /media/nico/TTL_436 on behalf of uid 1000
août 14 17:18:54 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.171' (uid=1000 pid=6845 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
août 14 17:18:54 nico-X570-GAMING-X systemd[1]: Starting Hostname Service...
août 14 17:18:54 nico-X570-GAMING-X dbus-daemon[804]: [system] Successfully activated service 'org.freedesktop.hostname1'
août 14 17:18:54 nico-X570-GAMING-X systemd[1]: Started Hostname Service.
août 14 17:18:54 nico-X570-GAMING-X audit[804]: USER_AVC pid=804 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.346" pid=5600 label="snap.firefox.firefox" peer_pid=16777 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
août 14 17:18:54 nico-X570-GAMING-X kernel: audit: type=1107 audit(1692026334.466:96): pid=804 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.346" pid=5600 label="snap.firefox.firefox" peer_pid=16777 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
août 14 17:19:18 nico-X570-GAMING-X kernel: loop19: detected capacity change from 0 to 231364
août 14 17:19:20 nico-X570-GAMING-X udisksd[854]: Set up loop device /dev/loop19 (backed by /media/nico/TTL_436/ToutouLinux-436_2015-04-30.iso)
août 14 17:19:20 nico-X570-GAMING-X kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
août 14 17:19:20 nico-X570-GAMING-X kernel: ISO 9660 Extensions: IEEE_P1282
août 14 17:19:20 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692026360.699:97): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:19:20 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:19:20 nico-X570-GAMING-X udisksd[854]: Mounted /dev/loop19 at /media/nico/ttl-436 on behalf of uid 1000
août 14 17:19:24 nico-X570-GAMING-X systemd[1]: systemd-hostnamed.service: Deactivated successfully.
août 14 17:19:32 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:19:32 nico-X570-GAMING-X udisksd[854]: No longer watching loop device /dev/loop19
août 14 17:19:32 nico-X570-GAMING-X udisksd[854]: Cleaning up mount point /media/nico/ttl-436 (device 7:19 no longer exists)
août 14 17:19:32 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692026372.808:98): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:19:32 nico-X570-GAMING-X systemd[1]: media-nico-ttl\x2d436.mount: Deactivated successfully.
août 14 17:19:32 nico-X570-GAMING-X gnome-shell[1972]: JS ERROR: Impossible to find an URI handler for mountable-volume:2015-04-30-08-24-01-00: Gio.IOErrorEnum: Erreur lors de l’obtention des informations du fichier « /media/nico/ttl-436 » : Aucun fichier ou dossier de ce type
_getHandlerApp@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:303:34
vfunc_get_commandline@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:208:21
makeLocationApp/<@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:944:26
_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:296:68
_updateNewWindowItem@resource:///org/gnome/shell/ui/appMenu.js:140:43
_onAppStateChanged@resource:///org/gnome/shell/ui/appMenu.js:129:14
_notifyStateChanged@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:794:43
_setWindows@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:820:22
_updateWindows@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:989:45
makeLocationApp/<@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:1005:18
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_updateFromPaths@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/fileManager1API.js:197:18
_updateLocationMap@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/fileManager1API.js:141:18
_onPropertyChanged@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/fileManager1API.js:105:18
août 14 17:19:32 nico-X570-GAMING-X udisksd[854]: Unmounted /dev/loop19 on behalf of uid 1000
août 14 17:19:44 nico-X570-GAMING-X kernel: loop19: detected capacity change from 0 to 231364
août 14 17:19:44 nico-X570-GAMING-X udisksd[854]: Set up loop device /dev/loop19 (backed by /media/nico/TTL_436/ToutouLinux-436_2015-04-30.iso)
août 14 17:19:44 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:19:44 nico-X570-GAMING-X kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
août 14 17:19:44 nico-X570-GAMING-X kernel: ISO 9660 Extensions: IEEE_P1282
août 14 17:19:44 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692026384.816:99): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:19:44 nico-X570-GAMING-X udisksd[854]: Mounted /dev/loop19 at /media/nico/ttl-436 on behalf of uid 1000
août 14 17:20:31 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:20:31 nico-X570-GAMING-X systemd[1]: media-nico-ttl\x2d436.mount: Deactivated successfully.
août 14 17:20:31 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692026431.418:100): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:20:31 nico-X570-GAMING-X udisksd[854]: Cleaning up mount point /media/nico/ttl-436 (device 7:19 no longer exists)
août 14 17:20:31 nico-X570-GAMING-X udisksd[854]: Unmounted /dev/loop19 on behalf of uid 1000
août 14 17:20:31 nico-X570-GAMING-X udisksd[854]: No longer watching loop device /dev/loop19
août 14 17:20:49 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:20:49 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692026449.487:101): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:20:49 nico-X570-GAMING-X systemd[1]: media-nico-TTL_436.mount: Deactivated successfully.
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: Object .Gjs_components_autorunManager_AutorunSource (0x55cb198cc4a0), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: Object Gio.Settings (0x7f1ec4242560), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #0 55cb173923d8 i resource:///org/gnome/shell/ui/messageTray.js:779 (2dbc29656a60 @ 149)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #1 55cb17392328 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (3bd46a430420 @ 68)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #2 55cb17392298 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (3bd46a4301f0 @ 25)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #3 7ffd9a359460 b self-hosted:1178 (427948b0a10 @ 454)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #0 55cb17392480 i resource:///org/gnome/shell/ui/messageTray.js:248 (2dbc29651880 @ 22)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #1 55cb173923d8 i resource:///org/gnome/shell/ui/messageTray.js:781 (2dbc29656a60 @ 169)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #2 55cb17392328 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (3bd46a430420 @ 68)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #3 55cb17392298 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (3bd46a4301f0 @ 25)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #4 7ffd9a359460 b self-hosted:1178 (427948b0a10 @ 454)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #0 55cb17392480 i resource:///org/gnome/shell/ui/messageTray.js:249 (2dbc29651880 @ 42)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #1 55cb173923d8 i resource:///org/gnome/shell/ui/messageTray.js:781 (2dbc29656a60 @ 169)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #2 55cb17392328 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (3bd46a430420 @ 68)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #3 55cb17392298 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (3bd46a4301f0 @ 25)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #4 7ffd9a359460 b self-hosted:1178 (427948b0a10 @ 454)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #0 55cb17392510 i resource:///org/gnome/shell/ui/messageTray.js:161 (2dbc29651380 @ 17)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #1 55cb17392480 i resource:///org/gnome/shell/ui/messageTray.js:251 (2dbc29651880 @ 59)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #2 55cb173923d8 i resource:///org/gnome/shell/ui/messageTray.js:781 (2dbc29656a60 @ 169)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #3 55cb17392328 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (3bd46a430420 @ 68)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #4 55cb17392298 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (3bd46a4301f0 @ 25)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #5 7ffd9a359460 b self-hosted:1178 (427948b0a10 @ 454)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: Object Gio.Settings (0x55cb19e7b5e0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #0 55cb173923d8 i resource:///org/gnome/shell/ui/messageTray.js:782 (2dbc29656a60 @ 184)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #1 55cb17392328 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (3bd46a430420 @ 68)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #2 55cb17392298 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (3bd46a4301f0 @ 25)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: #3 7ffd9a359460 b self-hosted:1178 (427948b0a10 @ 454)
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: Object .Gjs_ui_messageTray_NotificationApplicationPolicy (0x55cb1a690380), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
août 14 17:20:49 nico-X570-GAMING-X gnome-shell[1972]: Object .Gjs_components_autorunManager_AutorunSource (0x55cb198cc4a0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
août 14 17:20:49 nico-X570-GAMING-X udisksd[854]: Cleaning up mount point /media/nico/TTL_436 (device 8:18 is not mounted)
août 14 17:20:49 nico-X570-GAMING-X udisksd[854]: Unmounted /dev/sdb2 on behalf of uid 1000
août 14 17:20:49 nico-X570-GAMING-X kernel: sdb: detected capacity change from 15605760 to 0
août 14 17:20:51 nico-X570-GAMING-X kernel: usb 1-3: USB disconnect, device number 15
août 14 17:21:51 nico-X570-GAMING-X kernel: usb 1-3: new high-speed USB device number 16 using xhci_hcd
août 14 17:21:51 nico-X570-GAMING-X kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.00
août 14 17:21:51 nico-X570-GAMING-X kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
août 14 17:21:51 nico-X570-GAMING-X kernel: usb 1-3: Product: Flash Disk
août 14 17:21:51 nico-X570-GAMING-X kernel: usb 1-3: Manufacturer: USB
août 14 17:21:51 nico-X570-GAMING-X kernel: usb 1-3: SerialNumber: 5AB6BC00
août 14 17:21:51 nico-X570-GAMING-X kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
août 14 17:21:51 nico-X570-GAMING-X kernel: scsi host11: usb-storage 1-3:1.0
août 14 17:21:51 nico-X570-GAMING-X mtp-probe[16892]: checking bus 1, device 16: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:21:51 nico-X570-GAMING-X mtp-probe[16892]: bus: 1, device: 16 was not an MTP device
août 14 17:21:51 nico-X570-GAMING-X mtp-probe[16894]: checking bus 1, device 16: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-3"
août 14 17:21:51 nico-X570-GAMING-X mtp-probe[16894]: bus: 1, device: 16 was not an MTP device
août 14 17:21:52 nico-X570-GAMING-X kernel: scsi 11:0:0:0: Direct-Access USB Flash Disk 8.07 PQ: 0 ANSI: 4
août 14 17:21:52 nico-X570-GAMING-X kernel: sd 11:0:0:0: Attached scsi generic sg3 type 0
août 14 17:21:52 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] 15605760 512-byte logical blocks: (7.99 GB/7.44 GiB)
août 14 17:21:52 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write Protect is off
août 14 17:21:52 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Mode Sense: 23 00 00 00
août 14 17:21:52 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
août 14 17:21:52 nico-X570-GAMING-X kernel: sdb: sdb1 sdb2
août 14 17:21:52 nico-X570-GAMING-X kernel: sd 11:0:0:0: [sdb] Attached SCSI removable disk
août 14 17:21:52 nico-X570-GAMING-X systemd-udevd[16905]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
août 14 17:21:52 nico-X570-GAMING-X systemd-udevd[16905]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1.
août 14 17:21:52 nico-X570-GAMING-X systemd-udevd[16891]: sdb2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb2' failed with exit code 1.
août 14 17:21:52 nico-X570-GAMING-X audit[5600]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:21:52 nico-X570-GAMING-X kernel: audit: type=1400 audit(1692026512.629:102): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5600 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
août 14 17:21:52 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Activating service name='org.gnome.Shell.HotplugSniffer' requested by ':1.38' (uid=1000 pid=1972 comm="/usr/bin/gnome-shell " label="unconfined")
août 14 17:21:52 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
août 14 17:21:52 nico-X570-GAMING-X udisksd[854]: Mounted /dev/sdb2 at /media/nico/TTL_436 on behalf of uid 1000
août 14 17:22:04 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:22:04 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:23:04 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:23:04 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:23:05 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:23:05 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:23:27 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.9' (uid=1000 pid=1805 comm="/usr/libexec/tracker-miner-fs-3 " label="unconfined")
août 14 17:23:27 nico-X570-GAMING-X systemd[1726]: Starting Tracker metadata extractor...
août 14 17:23:27 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
août 14 17:23:27 nico-X570-GAMING-X systemd[1726]: Started Tracker metadata extractor.
août 14 17:24:10 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:24:10 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:24:10 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:24:27 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:24:27 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:24:45 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.9' (uid=1000 pid=1805 comm="/usr/libexec/tracker-miner-fs-3 " label="unconfined")
août 14 17:24:45 nico-X570-GAMING-X systemd[1726]: Starting Tracker metadata extractor...
août 14 17:24:45 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
août 14 17:24:45 nico-X570-GAMING-X systemd[1726]: Started Tracker metadata extractor.
août 14 17:24:56 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:24:56 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:24:56 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:25:06 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.9' (uid=1000 pid=1805 comm="/usr/libexec/tracker-miner-fs-3 " label="unconfined")
août 14 17:25:06 nico-X570-GAMING-X systemd[1726]: Starting Tracker metadata extractor...
août 14 17:25:06 nico-X570-GAMING-X dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
août 14 17:25:06 nico-X570-GAMING-X systemd[1726]: Started Tracker metadata extractor.
août 14 17:25:26 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:25:26 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:25:26 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:25:56 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:25:56 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:25:56 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:26:57 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:26:57 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:26:57 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:27:22 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:27:22 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:27:22 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:28:18 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:28:18 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:28:18 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:28:25 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:28:25 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:30:01 nico-X570-GAMING-X CRON[17283]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
août 14 17:30:01 nico-X570-GAMING-X CRON[17284]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
août 14 17:30:01 nico-X570-GAMING-X CRON[17283]: pam_unix(cron:session): session closed for user root
août 14 17:31:43 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:31:43 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:31:43 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:32:07 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:32:07 nico-X570-GAMING-X rtkit-daemon[1312]: Supervising 6 threads of 4 processes of 1 users.
août 14 17:32:39 nico-X570-GAMING-X systemd[1]: Started Run anacron jobs.
août 14 17:32:39 nico-X570-GAMING-X systemd[1]: anacron.service: Deactivated successfully.
août 14 17:32:39 nico-X570-GAMING-X anacron[17353]: Anacron 2.3 started on 2023-08-14
août 14 17:32:39 nico-X570-GAMING-X anacron[17353]: Normal exit (0 jobs run)
août 14 17:33:13 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set DNS server list to: 100.64.0.7
août 14 17:33:13 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set default route setting: yes
août 14 17:33:13 nico-X570-GAMING-X systemd-resolved[728]: moz0: Bus client set search domain list to: ~.
août 14 17:35:51 nico-X570-GAMING-X systemd[1726]: snap.firefox.firefox.99774116-caf4-4002-8797-f464a90755c6.scope: Consumed 3min 5.150s CPU time.
août 14 17:36:40 nico-X570-GAMING-X systemd[1726]: vte-spawn-ec0b6730-5200-4738-8cf8-151b5a5cd1e4.scope: Consumed 1.509s CPU time.
août 14 17:36:40 nico-X570-GAMING-X systemd[1726]: gnome-terminal-server.service: Consumed 7.572s CPU time.
août 14 17:36:47 nico-X570-GAMING-X gnome-shell[1972]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
août 14 17:36:47 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027407.2417] device (moz0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed')
août 14 17:36:47 nico-X570-GAMING-X gnome-shell[1972]: Removing a network device that was not added
août 14 17:36:47 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=806 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
août 14 17:36:47 nico-X570-GAMING-X systemd[1]: Starting Network Manager Script Dispatcher Service...
août 14 17:36:47 nico-X570-GAMING-X dbus-daemon[804]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
août 14 17:36:47 nico-X570-GAMING-X systemd[1]: Started Network Manager Script Dispatcher Service.
août 14 17:36:48 nico-X570-GAMING-X kernel: rfkill: input handler enabled
août 14 17:36:48 nico-X570-GAMING-X mozillavpn-startup.desktop[2162]: ICE default IO error handler doing an exit(), pid = 2162, errno = 32
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X systemd-logind[851]: System is powering down.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was notify on NMDeviceEthernet 0x55cb19636280.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was notify on NMDeviceEthernet 0x55cb19636510.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was notify on NMDeviceWifi 0x55cb19638300.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was notify on NMDeviceBt 0x55cb19610490.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was notify on NMActiveConnection 0x55cb19612180.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was notify on NMActiveConnection 0x55cb19612180.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was state-changed on NMDeviceEthernet 0x55cb19636280.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was state-changed on NMDeviceEthernet 0x55cb19636510.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was state-changed on NMDeviceWifi 0x55cb19638300.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was state-changed on NMDeviceBt 0x55cb19610490.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1963ec70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1963ec70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1963ec70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1963ec70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb183e9080.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19bfba60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19bfba60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19bfba60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19bfba60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb18d16230.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4c30a0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4c30a0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4c30a0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4c30a0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb177c4370.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb184af550.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb184af550.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb184af550.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb184af550.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c4b97c0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a5df390.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a5df390.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a5df390.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a5df390.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1a071c20.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4d5ea0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4d5ea0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4d5ea0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c4d5ea0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1964edc0.
août 14 17:36:48 nico-X570-GAMING-X ModemManager[911]: <info> caught signal, shutting down...
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X nm-dispatcher[17436]: Caught signal 15, shutting down...
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50e4c0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50e4c0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50e4c0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50e4c0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb19648590.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c530b70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c530b70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c530b70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c530b70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X ModemManager[911]: <info> ModemManager is shut down
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb183e77c0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183afb00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183afb00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183afb00.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Terminating
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183afb00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb183db250.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183c7560.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183c7560.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183c7560.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183c7560.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb183d1f70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X nvidia-persistenced[1259]: Received signal 15
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183cba70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183cba70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183cba70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183cba70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb17823830.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb1795f680.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending callback was set_container(), a vfunc.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X rsyslogd[827]: [origin software="rsyslogd" swVersion="8.2112.0" x-pid="827" x-info="https://www.rsyslog.com"] exiting on signal 15.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X snapd[839]: main.go:155: Exiting on terminated signal.
août 14 17:36:48 nico-X570-GAMING-X snapd[839]: overlord.go:516: Released state lock file
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50d7b0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50d7b0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50d7b0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c50d7b0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c4d6be0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1beda0d0.
août 14 17:36:48 nico-X570-GAMING-X fwupd[2583]: 15:36:48:0954 FuPluginUpower failed to query lid state
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X fwupd[2583]: 15:36:48:0954 FuPluginUpower failed to query lid state
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1beda0d0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1beda0d0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1beda0d0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb18eaec30.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c534b00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c534b00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c534b00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c534b00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c4c0480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183eadc0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183eadc0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183eadc0.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: unattended-upgrades.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Session 2 of User nico...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Removed slice Slice /system/getty.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: app-gnome-mozillavpn\x2dstartup-2162.scope: Consumed 1h 10min 30.093s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Removed slice Slice /system/modprobe.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Bluetooth Support.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Preparation for Logins.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Graphical Interface.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Multi-User System.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Login Prompts.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Sound Card.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Timer Units.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: anacron.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Trigger anacron every hour.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: apt-daily-upgrade.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Daily apt upgrade and clean activities.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: apt-daily.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Daily apt download activities.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: dpkg-db-backup.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Daily dpkg database backup timer.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: e2scrub_all.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: fstrim.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Discard unused blocks once a week.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: fwupd-refresh.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Refresh fwupd metadata regularly.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: logrotate.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Daily rotation of log files.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: man-db.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Daily man-db regeneration.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: motd-news.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Message of the Day.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: systemd-tmpfiles-clean.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Daily Cleanup of Temporary Directories.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: update-notifier-download.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Download data for packages that failed at package install time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: update-notifier-motd.timer: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Check to see whether there is a new version of Ubuntu available.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: systemd-rfkill.socket: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Modem Manager...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Network Manager Script Dispatcher Service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Accounts Service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping ACPI event daemon...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Wayland Session (session: ubuntu).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target Current graphical user session.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Path trigger for Apport crash notifications.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Path trigger for new release of Ubuntu notifications.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Session.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Wayland Session.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME session X11 services.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Session (session: ubuntu).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME accessibility target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME color management target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME date & time target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME maintenance of expirable data target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME keyboard configuration target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME keyboard shortcuts target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME power management target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME printer notifications target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME RFKill support target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME FreeDesktop screensaver target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME file sharing target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME smartcard target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME sound sample caching target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Save/Restore Sound Card State...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Wacom tablet support target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME XSettings target.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping IBus Daemon for GNOME...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping GNOME color management service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping GNOME keyboard configuration service...
août 14 17:36:48 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027408.9500] modem-manager: ModemManager no longer available
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping GNOME keyboard shortcuts service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping GNOME power management service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping GNOME Wacom tablet support service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping LSB: automatic crash report generation...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Monitor Session leader for GNOME Session.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Bluetooth service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: org.freedesktop.IBus.session.GNOME.service: Killing process 2187 (gdbus) with signal SIGKILL.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Manage, Install and Generate Color Profiles...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: org.freedesktop.IBus.session.GNOME.service: Killing process 2218 (gdbus) with signal SIGKILL.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: org.freedesktop.IBus.session.GNOME.service: Killing process 2250 (dconf worker) with signal SIGKILL.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Regular background program processing daemon...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Make remote CUPS printers available locally...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping GNOME Display Manager...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping irqbalance daemon...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped GNOME Session Manager (session: ubuntu).
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Tool to automatically collect and submit kernel crash signatures...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: lm-sensors.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Initialize hardware monitoring sensors.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping MozillaVPN D-Bus service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Dispatcher daemon for systemd-networkd...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped GNOME XSettings service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping NVIDIA Persistence Daemon...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: openvpn.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME session X11 services.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped OpenVPN service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping PackageKit Daemon...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: plymouth-quit-wait.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Hold until boot process finishes up.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Power Profiles daemon...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping System Logging Service...
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183eadc0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb183dcf30.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: snapd.seeded.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Wait until snapd is fully seeded.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19afee60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19afee60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19afee60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19afee60.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Snap Daemon...
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c4be200.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Condition check resulted in Ubuntu core (all-snaps) system shutdown helper setup service being skipped.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183f0a30.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183f0a30.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183f0a30.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb183f0a30.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1bed9650.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb179fe480.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending callback was set_container(), a vfunc.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c3d3a00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c3d3a00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c3d3a00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c3d3a00.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c510c40.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c48abf0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c48abf0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c48abf0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1c48abf0.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb192dde50.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Load/Save Random Seed...
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1bedbd60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1bedbd60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1bedbd60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1bedbd60.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb19341120.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1748e670.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1748e670.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1748e670.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1748e670.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c53cc10.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Disk Manager...
août 14 17:36:48 nico-X570-GAMING-X nvidia-persistenced[1259]: Socket closed.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X nvidia-persistenced[1259]: PID file unlocked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X nvidia-persistenced[1259]: PID file closed.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X nvidia-persistenced[1259]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19b0ad40.
août 14 17:36:48 nico-X570-GAMING-X nvidia-persistenced[1259]: Shutdown (1259)
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19b0ad40.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19b0ad40.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb19b0ad40.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c4c7040.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Daemon for power management...
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb174b7080.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending callback was set_container(), a vfunc.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb17558620.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb17558620.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55cb17558620.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb17f97f50.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb17f97f50.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb17f97f50.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb17f97f50.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1ae8fa70.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb17558620.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a68e460.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a68e460.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a68e460.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cb1a68e460.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cb1c13d630.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55cb17558620.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: The offending callback was set_container(), a vfunc.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: accounts-daemon.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Accounts Service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: cron.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Regular background program processing daemon.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: irqbalance.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped irqbalance daemon.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: networkd-dispatcher.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Dispatcher daemon for systemd-networkd.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: power-profiles-daemon.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Power Profiles daemon.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: rsyslog.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped System Logging Service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: snapd.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Snap Daemon.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: snapd.service: Consumed 2.210s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: ModemManager.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Modem Manager.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: rtkit-daemon.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: upower.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Daemon for power management.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Network Manager Script Dispatcher Service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: alsa-restore.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Save/Restore Sound Card State.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: kerneloops.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Tool to automatically collect and submit kernel crash signatures.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: session-2.scope: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Session 2 of User nico.
août 14 17:36:48 nico-X570-GAMING-X systemd-logind[851]: Session 2 logged out. Waiting for processes to exit.
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.27' (uid=0 pid=1264 comm="/usr/sbin/gdm3 " label="unconfined")
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for accounts-daemon.service/start is destructive (systemd-sysusers.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X udisksd[854]: udisks daemon version 2.9.4 exiting
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Transaction for accounts-daemon.service/start is destructive (systemd-sysusers.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: packagekit.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X gdm3[1264]: Gdm: Failed to contact accountsservice: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.Accounts : Transaction for accounts-daemon.service/start is destructive (systemd-sysusers.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped IBus Daemon for GNOME.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: org.freedesktop.IBus.session.GNOME.service: Consumed 3.072s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped PackageKit Daemon.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: packagekit.service: Consumed 8.841s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: colord.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Manage, Install and Generate Color Profiles.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: colord.service: Consumed 4.398s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: gdm.service: Failed with result 'exit-code'.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped GNOME Display Manager.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: gdm.service: Triggering OnFailure= dependencies.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (systemd-fsck@dev-disk-by\x2duuid-B96A\x2d8A74.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (systemd-fsck@dev-disk-by\x2duuid-B96A\x2d8A74.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: nvidia-persistenced.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X apport[17471]: * Stopping automatic crash report generation: apport
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped NVIDIA Persistence Daemon.
août 14 17:36:48 nico-X570-GAMING-X systemd-logind[851]: Removed session 2.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: systemd-random-seed.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X apport[17471]: ...done.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Load/Save Random Seed.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: apport.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped LSB: automatic crash report generation.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Host and Network Name Lookups.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target System Time Set.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Firmware update daemon...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Starting Show Plymouth Power Off Screen...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Authorization Manager...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Switcheroo Control Proxy service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping User Login Management...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping User Manager for UID 1000...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: cups-browsed.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Make remote CUPS printers available locally.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped target Network is Online.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: NetworkManager-wait-online.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Application launched by gnome-session-binary...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Application launched by gnome-session-binary...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Network Manager Wait Online.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Application launched by gnome-session-binary...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Application launched by gnome-session-binary...
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
août 14 17:36:48 nico-X570-GAMING-X avahi-daemon[800]: Got SIGTERM, quitting.
août 14 17:36:48 nico-X570-GAMING-X avahi-daemon[800]: Leaving mDNS multicast group on interface enx344b50000000.IPv6 with address fe80::dfc3:5b34:664e:a5f3.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping snap.snap-store.ubuntu-software.1824d5da-2ec7-414b-85f3-438b354ce943.scope...
août 14 17:36:48 nico-X570-GAMING-X avahi-daemon[800]: Leaving mDNS multicast group on interface enx344b50000000.IPv4 with address 192.168.0.178.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopping CUPS Scheduler...
août 14 17:36:48 nico-X570-GAMING-X avahi-daemon[800]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Received SIGRTMIN+20 from PID 17493 (plymouthd).
août 14 17:36:48 nico-X570-GAMING-X avahi-daemon[800]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Removed slice Slice /app/gnome-session-manager.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Removed slice Slice /app/org.gnome.Terminal.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: app-org.gnome.Terminal.slice: Consumed 9.082s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped target Main User Target.
août 14 17:36:48 nico-X570-GAMING-X gvfsd[1751]: A connection to the bus can't be made
août 14 17:36:48 nico-X570-GAMING-X io.snapcraft.Settings[5870]: Exiting on terminated.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping D-Bus User Message Bus...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping User preferences database...
août 14 17:36:48 nico-X570-GAMING-X xdg-desktop-por[2335]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.368' (uid=1000 pid=7455 comm="/usr/libexec/gvfsd-dnssd --spawner :1.2 /org/gtk/g" label="unconfined")
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Evolution address book service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Evolution calendar service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Evolution source registry...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Virtual filesystem service - Apple File Conduit monitor...
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Transaction for avahi-daemon.service/start is destructive (systemd-sysctl.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for avahi-daemon.service/start is destructive (systemd-sysctl.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Virtual filesystem service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Virtual filesystem service - digital camera monitor...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Virtual filesystem metadata service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Virtual filesystem service - disk device monitor...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping PipeWire Media Session Manager...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Sound Service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Service for snap application snapd-desktop-integration.snapd-desktop-integration...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Tracker file system data miner...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Portal service (GNOME implementation)...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Portal service (GTK/GNOME implementation)...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping Portal service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping flatpak document portal service...
août 14 17:36:48 nico-X570-GAMING-X avahi-daemon[800]: avahi-daemon 0.8 exiting.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping sandboxed app permission store...
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.369' (uid=1000 pid=1735 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Unmounted /run/user/1000/doc.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Unmounted /run/user/1000/gvfs.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: avahi-daemon.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped PipeWire Media Session Manager.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: gvfs-daemon.service: Killing process 17409 (trash-expunge) with signal SIGKILL.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: polkit.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: xdg-document-portal.service: Failed with result 'exit-code'.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Authorization Manager.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped flatpak document portal service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: xdg-permission-store.service: Failed with result 'exit-code'.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: udisks2.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped sandboxed app permission store.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped Disk Manager.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: udisks2.service: Consumed 1.246s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Virtual filesystem service - disk device monitor.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: gvfs-udisks2-volume-monitor.service: Consumed 1.991s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Virtual filesystem service - digital camera monitor.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Virtual filesystem service - Apple File Conduit monitor.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for rtkit-daemon.service/start is destructive (systemd-timesyncd.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Transaction for rtkit-daemon.service/start is destructive (systemd-timesyncd.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.370' (uid=1000 pid=1735 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Evolution source registry.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for rtkit-daemon.service/start is destructive (systemd-binfmt.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Transaction for rtkit-daemon.service/start is destructive (systemd-binfmt.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped User preferences database.
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.371' (uid=1000 pid=1735 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Virtual filesystem metadata service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for rtkit-daemon.service/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Transaction for rtkit-daemon.service/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Main process exited, code=exited, status=143/n/a
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'.
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.372' (uid=1000 pid=1735 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for rtkit-daemon.service/start is destructive (system-systemd\x2dfsck.slice has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Transaction for rtkit-daemon.service/start is destructive (system-systemd\x2dfsck.slice has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.373' (uid=1000 pid=1735 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Application launched by gnome-session-binary.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: app-gnome-update\x2dnotifier-5527.scope: Consumed 2.738s CPU time.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Application launched by gnome-session-binary.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for rtkit-daemon.service/start is destructive (systemd-update-utmp.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Application launched by gnome-session-binary.
août 14 17:36:48 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Transaction for rtkit-daemon.service/start is destructive (systemd-update-utmp.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopping PipeWire Multimedia Service...
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped PipeWire Multimedia Service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Virtual filesystem service.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: cups.service: Deactivated successfully.
août 14 17:36:48 nico-X570-GAMING-X systemd[1]: Stopped CUPS Scheduler.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: dbus.service: Killing process 6847 (gdbus) with signal SIGKILL.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/ldac_hq
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Evolution calendar service.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/ldac_sq
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Evolution address book service.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/ldac_mq
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/aptx_hd
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx_hd
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Portal service.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/aptx
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Portal service (GNOME implementation).
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: xdg-desktop-portal-gnome.service: Consumed 2.479s CPU time.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Portal service (GTK/GNOME implementation).
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc_xq_453
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc_xq_453
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped snap.snap-store.ubuntu-software.1824d5da-2ec7-414b-85f3-438b354ce943.scope.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: snap.snap-store.ubuntu-software.1824d5da-2ec7-414b-85f3-438b354ce943.scope: Consumed 1.897s CPU time.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc_xq_512
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped D-Bus User Message Bus.
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: dbus.service: Consumed 50.001s CPU time.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc_xq_512
août 14 17:36:48 nico-X570-GAMING-X systemd[1726]: Stopped Application launched by gnome-session-binary.
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc_xq_552
août 14 17:36:48 nico-X570-GAMING-X bluetoothd[801]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc_xq_552
août 14 17:36:49 nico-X570-GAMING-X pulseaudio[1735]: After module unload, module 'module-null-sink' was still loaded!
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: mozillavpn.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped MozillaVPN D-Bus service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped Sound Service.
août 14 17:36:49 nico-X570-GAMING-X tracker-miner-fs-3[1805]: OK
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: fwupd.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped Tracker file system data miner.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Firmware update daemon.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: tracker-miner-fs-3.service: Consumed 6.439s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Removed slice User Background Tasks Slice.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: background.slice: Consumed 6.878s CPU time.
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.1123] device (44:4A:DB:5F:0C:94): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
août 14 17:36:49 nico-X570-GAMING-X bluetoothd[801]: Stopping SDP server
août 14 17:36:49 nico-X570-GAMING-X bluetoothd[801]: Exit
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: switcheroo-control.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Switcheroo Control Proxy service.
août 14 17:36:49 nico-X570-GAMING-X gnome-shell[1972]: Could not release device '/dev/input/event2' (13,66): GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Started Show Plymouth Power Off Screen.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Condition check resulted in Tell Plymouth To Jump To initramfs being skipped.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-logind.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped User Login Management.
août 14 17:36:49 nico-X570-GAMING-X gnome-shell[2299]: (EE) failed to write to Xwayland fd: Broken pipe
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped GNOME keyboard configuration service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped GNOME color management service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped GNOME keyboard shortcuts service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped GNOME power management service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped GNOME Wacom tablet support service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Session is initialized.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Shell.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopping GNOME Shell on Wayland...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: bluetooth.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Bluetooth service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped GNOME Shell on Wayland.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: org.gnome.Shell@wayland.service: Consumed 12min 10.545s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Removed slice User Core Session Slice.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: session.slice: Consumed 12min 15.690s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target GNOME Session Manager is ready.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target Tasks to be run before GNOME Session starts.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target Session services which should run early before the graphical session is brought up.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Reached target Shutdown running GNOME Session.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopping Start gnome-keyring as SSH agent...
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Starting Restart DBus after GNOME Session shutdown...
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target Shutdown running GNOME Session.
août 14 17:36:49 nico-X570-GAMING-X sh[17539]: dbus-update-activation-environment: error: unable to connect to D-Bus: 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.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Started Restart DBus after GNOME Session shutdown.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: gnome-keyring-ssh.service: Control process exited, code=exited, status=71/OSERR
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: gnome-keyring-ssh.service: Failed with result 'exit-code'.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped Start gnome-keyring as SSH agent.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target Basic System.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target Paths.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped Pending report trigger for Ubuntu Report.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target Sockets.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Stopped target Timers.
août 14 17:36:49 nico-X570-GAMING-X gnome-session-c[17538]: Couldn't connect to session bus: Erreur lors de la réception des données : Connexion ré-initialisée par le correspondant
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed D-Bus User Message Bus Socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed GnuPG network certificate management daemon.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed GnuPG cryptographic agent (ssh-agent emulation).
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed GnuPG cryptographic agent and passphrase cache.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed PipeWire Multimedia System Socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed debconf communication socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed Sound System.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed REST API socket for snapd user session agent.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Closed Speech Dispatcher Socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Removed slice User Application Slice.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: app.slice: Consumed 1h 14min 46.282s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Reached target Shutdown.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Finished Exit the Session.
août 14 17:36:49 nico-X570-GAMING-X systemd[1726]: Reached target Exit the Session.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: user@1000.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped User Manager for UID 1000.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: user@1000.service: Consumed 1h 27min 9.428s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Killer...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping User Runtime Directory /run/user/1000...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-oomd.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-oomd.service: Consumed 3.834s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: run-user-1000.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /run/user/1000.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: user-runtime-dir@1000.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped User Runtime Directory /run/user/1000.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Removed slice User Slice of UID 1000.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: user-1000.slice: Consumed 1h 27min 9.550s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping Permit User Sessions...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-user-sessions.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Permit User Sessions.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Network.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target User and Group Name Lookups.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Remote File Systems.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping Network Manager...
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.3637] caught SIGTERM, shutting down normally.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping Network Name Resolution...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping WPA supplicant...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-resolved.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Network Name Resolution.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: wpa_supplicant.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped WPA supplicant.
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.3803] dhcp4 (enx344b50000000): canceled DHCP transaction
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.3803] dhcp4 (enx344b50000000): activation: beginning transaction (timeout in 45 seconds)
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.3803] dhcp4 (enx344b50000000): state changed no lease
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.3805] manager: NetworkManager state is now CONNECTED_SITE
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.3808] device (wlp4s0): state change: unavailable -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed')
août 14 17:36:49 nico-X570-GAMING-X dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=806 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Requested transaction contradicts existing jobs: Transaction for NetworkManager-dispatcher.service/start is destructive (systemd-timesyncd.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:49 nico-X570-GAMING-X dbus-daemon[804]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Transaction for NetworkManager-dispatcher.service/start is destructive (systemd-timesyncd.service has 'stop' job queued, but 'start' is included in transaction).
août 14 17:36:49 nico-X570-GAMING-X NetworkManager[806]: <info> [1692027409.4169] exiting (success)
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: NetworkManager.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Network Manager.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Preparation for Network.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: acpid.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped ACPI event daemon.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Basic System.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Path Units.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: acpid.path: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped ACPI Events Check.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: cups.path: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped CUPS Scheduler.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: resolvconf-pull-resolved.path: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped resolvconf-pull-resolved.path.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: whoopsie.path: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Start whoopsie on modification of the /var/crash directory.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Slice Units.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Removed slice User and Session Slice.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: user.slice: Consumed 1h 27min 12.817s CPU time.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Socket Units.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: acpid.socket: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Closed ACPID Listen Socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: avahi-daemon.socket: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: cups.socket: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Closed CUPS Scheduler.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snapd.socket: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Closed Socket activation for snappy daemon.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: syslog.socket: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Closed Syslog Socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: uuidd.socket: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Closed UUID daemon activation socket.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target System Initialization.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Local Encrypted Volumes.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Local Verity Protected Volumes.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping Set Up Additional Binary Formats...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-sysctl.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Apply Kernel Variables.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-modules-load.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Load Kernel Modules.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping Network Time Synchronization...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopping Record System Boot/Shutdown in UTMP...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-binfmt.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Set Up Additional Binary Formats.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: proc-sys-fs-binfmt_misc.automount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unset automount Arbitrary Executable File Formats File System Automount Point.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: proc-sys-fs-binfmt_misc.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-update-utmp.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Record System Boot/Shutdown in UTMP.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-timesyncd.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Network Time Synchronization.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Create Volatile Files and Directories.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Local File Systems.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Mounted snaps.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /boot/efi...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /media/nico/TTL_436...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /media/nico/Ubuntu...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /media/nico/ZTEMODEM...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /run/credentials/systemd-sysusers.service...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /run/snapd/ns/firefox.mnt...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /run/snapd/ns/snap-store.mnt...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /run/snapd/ns/snapd-desktop-integration.mnt...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for bare, revision 5...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for core, revision 15511...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for core20, revision 1822...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for core20, revision 1974...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for core22, revision 858...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for firefox, revision 2971...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for firefox, revision 2987...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for gnome-3-38-2004, revision 119...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for gnome-3-38-2004, revision 143...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for gnome-42-2204, revision 120...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for gnome-42-2204, revision 126...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for gtk-common-themes, revision 1535...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for snap-store, revision 638...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for snap-store, revision 959...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for snapd, revision 18357...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for snapd, revision 19457...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for snapd-desktop-integration, revision 49...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for snapd-desktop-integration, revision 83...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for urban-terror, revision 70...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting Mount unit for firefox, revision 2356 via mount-control...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: boot-efi.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /boot/efi.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: media-nico-TTL_436.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /media/nico/TTL_436.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: media-nico-ZTEMODEM.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /media/nico/ZTEMODEM.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: run-credentials-systemd\x2dsysusers.service.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /run/credentials/systemd-sysusers.service.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: run-snapd-ns-firefox.mnt.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /run/snapd/ns/firefox.mnt.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: run-snapd-ns-snap\x2dstore.mnt.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /run/snapd/ns/snap-store.mnt.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /run/snapd/ns/snapd-desktop-integration.mnt.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-bare-5.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for bare, revision 5.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-core-15511.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for core, revision 15511.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-core20-1822.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for core20, revision 1822.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-core20-1974.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for core20, revision 1974.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-core22-858.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for core22, revision 858.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-firefox-2971.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for firefox, revision 2971.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-firefox-2987.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for firefox, revision 2987.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-gnome\x2d3\x2d38\x2d2004-119.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for gnome-3-38-2004, revision 119.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-gnome\x2d3\x2d38\x2d2004-143.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for gnome-3-38-2004, revision 143.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-gnome\x2d42\x2d2204-120.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for gnome-42-2204, revision 120.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-gnome\x2d42\x2d2204-126.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for gnome-42-2204, revision 126.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-gtk\x2dcommon\x2dthemes-1535.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for gtk-common-themes, revision 1535.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-snap\x2dstore-638.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for snap-store, revision 638.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-snap\x2dstore-959.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for snap-store, revision 959.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-snapd-18357.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for snapd, revision 18357.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-snapd-19457.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for snapd, revision 19457.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-snapd\x2ddesktop\x2dintegration-49.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for snapd-desktop-integration, revision 49.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-snapd\x2ddesktop\x2dintegration-83.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for snapd-desktop-integration, revision 83.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: snap-urban\x2dterror-70.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for urban-terror, revision 70.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: var-snap-firefox-common-host\x2dhunspell.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted Mount unit for firefox, revision 2356 via mount-control.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Mounting snaps.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounting /run/snapd/ns...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-fsck@dev-disk-by\x2duuid-B96A\x2d8A74.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped File System Check on /dev/disk/by-uuid/B96A-8A74.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Removed slice Slice /system/systemd-fsck.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: run-snapd-ns.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /run/snapd/ns.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Swaps.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Deactivating swap /swapfile...
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: media-nico-Ubuntu.mount: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Unmounted /media/nico/Ubuntu.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped target Preparation for Local File Systems.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Create Static Device Nodes in /dev.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-sysusers.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Create System Users.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: swapfile.swap: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Deactivated swap /swapfile.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Reached target Unmount All Filesystems.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-remount-fs.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Stopped Remount Root and Kernel File Systems.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Reached target System Shutdown.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Reached target Late Shutdown Services.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: systemd-poweroff.service: Deactivated successfully.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Finished System Power Off.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Reached target System Power Off.
août 14 17:36:49 nico-X570-GAMING-X systemd[1]: Shutting down.
août 14 17:36:49 nico-X570-GAMING-X systemd-shutdown[1]: Syncing filesystems and block devices.
août 14 17:36:49 nico-X570-GAMING-X systemd-journald[446]: Journal stoppedHors ligne
#25 Le 15/08/2023, à 11:00
- geole
Re : Redémarrage intempestif: [Hardware Error]: PROCESSOR
Bonjour.
Je ne sais pas s'il s'agit de cet arrêt.
Je ne sais pas en trouver la cause. Peut-être lié à la ligne répétive "Stack Trace ....."
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0==
août 14 17:36:48 nico-X570-GAMING-X systemd-logind[851]: System is powering down.
août 14 17:36:48 nico-X570-GAMING-X gnome-shell[1972]: == Stack trace for context 0x55cb172224b0 ==Dernière modification par geole (Le 15/08/2023, à 11:03)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne