#1 Le 15/12/2020, à 14:36
- ar barzh paour
journal pollué
en consultant les messages générés par le système , je constate que mon journal est pollué par des messages à tel point que j'arrrive à peine à le faire défiler quand je lance journalctl
j'ai regardé le man de journalctl mais je ne comprends pas comment l'utiliser pour faire du ménage
à moins qu'il n'y ait une autre façon de suprimer ces messages du journal
1-avez-vous une piste pour alléger un peu le journal ?
2- voyez-vous d'où peut provenir cette erreur
quelques exemples de pollution
=================================================================================================================
le 18 septembre
un nombre impressionnant de messages (peut-on les compter ?) , de plus le message lui même fait douze lignes
sept. 18 17:19:52 jpb-MS-7A70 gnome-shell[2689]: JS ERROR: TypeError: null has no properties
........
_convertToNativeSignal@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:169:19
le même qui commence pareil mais plus court
sept. 18 17:20:08 jpb-MS-7A70 gnome-shell[2689]: JS ERROR: TypeError: this._dialog is null
_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
encore un autre
sept. 18 17:24:57 jpb-MS-7A70 gnome-shell[2689]: JS ERROR: TypeError: null has no properties
_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
journalctl -S 2020-09-18 -U "2020-09-18 23:00:00" -g "JS ERROR"me donne 2 940 516 lignes
=================================================================================================================
plus récent , 7 lignes
=================================================================================================================
déc. 14 21:04:18 jpb-MS-7A70 gnome-shell[15604]: JS ERROR: TypeError: null has no properties
...........
action@resource:///org/gnome/shell/ui/endSessionDialog.js:380:26
journalctl -S 2020-12-14 -U "2020-12-14 23:00:00" -g "JS ERROR"me donne 1 894700 lignes
=================================================================================================================
Dernière modification par ar barzh paour (Le 15/12/2020, à 14:38)
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#2 Le 15/12/2020, à 16:44
- moko138
Re : journal pollué
Commence par sauvegarder les lignes ou groupes de ligne répétitifs récents, puisqu'ils signalent un problème à traiter.
Ensuite, j'indique une façon de contenir le volume de /var/log dans les limites fixées par toi, dans ce message : ./viewtopic.php?pid=22191055#p22191055
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#3 Le 15/12/2020, à 17:25
- Compte supprimé
Re : journal pollué
Bonjour,
Je lis:
journalctl -S 2020-09-18 -U "2020-09-18 23:00:00" -g "JS ERROR"Sur mon pc (18.04 Mate) , l'option -g , bien que figurant dans le man, ne semble pas être reconnu:
journalctl -g "ERROR"
journalctl : option invalide -- 'g'et pour l'option équivalente --grep, j'obtiens :
journalctl --grep "ERROR"
Compiled without pattern matching supportIl est fait mention d'un bug ---> https://bugs.launchpad.net/ubuntu/+sour … ug/1751006
...
Dernière modification par Compte supprimé (Le 15/12/2020, à 17:26)
#4 Le 15/12/2020, à 18:07
- ar barzh paour
Re : journal pollué
@moko
ok je regarde ça
@pseudofab
l'option -g de journalctl me donne la même taille que --grep
jpb@jpb-MS-7A70:~$ ls -ails journalctl-*.txt
147440 314916 -rw-rw-r-- 1 jpb jpb 322465992 déc. 15 17:00 journalctl-g-JS-ERROR.txt
137021 314916 -rw-rw-r-- 1 jpb jpb 322465992 déc. 15 17:01 journalctl--grep-JS-ERROR.txt
jpb@jpb-MS-7A70:~$ donc je ne sais pas si c'est bon ou pas , en tout cas ça ressemble à ce que je visualise (avec difficulté) par journalctl sans option ni paramètre
journalctl -S 2020-09-18 -U "2020-09-18 23:00:00" > journalctl-2020-09-18.txt
131256 315112 -rw-rw-r-- 1 jpb jpb 322671993 déc. 15 17:22 journalctl-2020-09-18.txtsi j'enlève la taille du fichier contenant JS ERROR j'obtiendrais une taille convenable !! 206001
(au moins pour ce jour là)
Dernière modification par ar barzh paour (Le 20/12/2020, à 18:33)
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#5 Le 16/12/2020, à 10:34
- Compte supprimé
Re : journal pollué
Bonjour,
ar barzh paour a écrit :
@pseudofab
l'option -g de journalctl me donne la même taille que --grep
donc je ne sais pas si c'est bon ou pas ,
Pas de souci. Le bug a donc été corrigé sur la 20.04 (pour rappel, je suis sous 18.04).
C'est pas un bug particulièrement invalidant puisque l'on peut placer un grep à la suite d'un pipe 
#6 Le 16/12/2020, à 15:07
- ar barzh paour
Re : journal pollué
je ne sais pas où ça va me mener
j'ai regardé les journaux de /var/log
par date
par taille
user par date
user par taille
system par date
system par taille
Dernière modification par ar barzh paour (Le 16/12/2020, à 16:19)
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#7 Le 16/12/2020, à 18:55
- ar barzh paour
Re : journal pollué
je ne m'en sors pas pour analyser quelles sont les erreurs contenues dans le journal
je crois que je vais me contenter d'appliquer la solution de moko qui devait permettre de réduire le taille des infos
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#8 Le 16/12/2020, à 19:44
- geole
Re : journal pollué
Bonjour
Ton journal de log ne dépassera jamais 4 Go.
Peux-tu donner le retour des erreurs importantes.
journalctl --no-pager -b -p errAinsi que la quantité de fois pour ton erreur spécifique
journalctl --no-pager -b | grep "endSessionDialog.js" | wc -l Pour en connaître un peu plus
journalctl --no-pager -b | grep "JS ERROR" | tail -200 J'ai noté ce lien https://bugs.launchpad.net/ubuntu/+sour … ug/1841774
Dernière modification par geole (Le 16/12/2020, à 19:54)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
En ligne
#9 Le 16/12/2020, à 20:14
- ar barzh paour
Re : journal pollué
@geole
je regarderais ça
mais déjà en regardant le début du bug
-- Logs begin at Tue 2019-02-19 00:29:40 CET. --
ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties
_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13
vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties
_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13
vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
ça ressemble beaucoup à ce que j'étais en train d'analyser
journalctl -S "2020-12-01 00:00:00" -U "2020-12-01 23:59:59" |grep -v "JS ERROR" |grep -v "vfunc_show"|grep -v "onFocus"|grep -v "addWindowEffect"jpb@jpb-MS-7A70:~$ journalctl --no-pager -b -p err
-- Logs begin at Fri 2020-09-18 15:00:57 CEST, end at Wed 2020-12-16 19:12:31 CET. --
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
déc. 16 10:26:15 jpb-MS-7A70 systemd-udevd[342]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
déc. 16 10:26:27 jpb-MS-7A70 gnome-session-binary[1350]: Unrecoverable failure in required component org.gnome.Shell.desktop
déc. 16 10:26:29 jpb-MS-7A70 pulseaudio[1336]: Failed to find a working profile.
déc. 16 10:26:29 jpb-MS-7A70 pulseaudio[1336]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" card_name="alsa_card.usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
déc. 16 10:26:29 jpb-MS-7A70 pulseaudio[1336]: Failed to find a working profile.
déc. 16 10:26:29 jpb-MS-7A70 pulseaudio[1336]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" card_name="alsa_card.usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
déc. 16 10:27:38 jpb-MS-7A70 gdm-password][2853]: gkr-pam: unable to locate daemon control file
déc. 16 10:27:39 jpb-MS-7A70 pulseaudio[2876]: Failed to find a working profile.
déc. 16 10:27:39 jpb-MS-7A70 pulseaudio[2876]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" card_name="alsa_card.usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
déc. 16 10:27:52 jpb-MS-7A70 systemd[1]: Failed to start Samba NMB Daemon.
déc. 16 10:28:04 jpb-MS-7A70 pulseaudio[2876]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[1336]: Failed to find a working profile.
déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[1336]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" card_name="alsa_card.usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
déc. 16 11:32:29 jpb-MS-7A70 gdm-password][10143]: gkr-pam: unable to locate daemon control file
déc. 16 11:32:32 jpb-MS-7A70 pulseaudio[10257]: Failed to find a working profile.
déc. 16 11:32:32 jpb-MS-7A70 pulseaudio[10257]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" card_name="alsa_card.usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
déc. 16 11:32:57 jpb-MS-7A70 pulseaudio[10257]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
déc. 16 18:19:44 jpb-MS-7A70 kernel: sd 8:0:0:0: [sdk] No Caching mode page found
déc. 16 18:19:44 jpb-MS-7A70 kernel: sd 8:0:0:0: [sdk] Assuming drive cache: write through
jpb@jpb-MS-7A70:~$ EDIT :
voir résolution des erreurs EVIOCSKEYCODE ici
https://forum.ubuntu-fr.org/viewtopic.p … #p22393172
Dernière modification par ar barzh paour (Le 29/12/2020, à 14:37)
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#10 Le 16/12/2020, à 20:17
- ar barzh paour
Re : journal pollué
jpb@jpb-MS-7A70:~$ journalctl --no-pager -b | grep "endSessionDialog.js" | wc -l
0
jpb@jpb-MS-7A70:~$ jpb@jpb-MS-7A70:~$ journalctl --no-pager -b | grep "JS ERROR" | tail -200
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null
jpb@jpb-MS-7A70:~$ PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#11 Le 16/12/2020, à 20:59
- ar barzh paour
Re : journal pollué
geole a écrit :
Bonjour
Ton journal de log ne dépassera jamais 4 Go.
actuellement Propiétés de journal : 4,2GB
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#12 Le 17/12/2020, à 11:21
- geole
Re : journal pollué
Bonjour
La quantité d'erreurs est minime. On va détailler pour voir ce que cela cache
journalctl --no-pager --since "2020-12-16 11:32:20" --until "2020-12-16 11:32:22" Si tu as plein d'espace libre, le réalignement à 4 Gio n'est pas instantané
Si tu as très peu d'espace disponible la limitation à de 4 Gio est diminuée de façon importante.
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
En ligne
#13 Le 17/12/2020, à 17:55
- ar barzh paour
Re : journal pollué
jpb@jpb-MS-7A70:~$ journalctl --no-pager --since "2020-12-16 11:32:20" --until "2020-12-16 11:32:22"
-- Logs begin at Fri 2020-09-18 15:00:57 CEST, end at Thu 2020-12-17 16:53:18 CET. --
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Media keys handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Maintenance of expirable data.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Freedesktop screensaver handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-housekeeping.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Maintenance of expirable data.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-screensaver-proxy.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Freedesktop screensaver handling.
déc. 16 11:32:21 jpb-MS-7A70 kernel: rfkill: input handler enabled
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME RFKill handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-media-keys.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Media keys handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Accessibility settings.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Sound sample caching handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME XSettings.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-a11y-settings.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Accessibility settings.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Sharing handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Power management handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-rfkill.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME RFKill handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Color management.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Smartcard handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME USB protection handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Keyboard handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-keyboard.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Keyboard handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-sharing.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Sharing handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: at-spi-dbus-bus.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Date & Time handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-power.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Power management handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-smartcard.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Smartcard handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-usb-protection.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME USB protection handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Wacom handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME WWan management.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-wacom.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Wacom handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-sound.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Sound sample caching handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Printer notifications.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-color.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Color management.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-datetime.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Date & Time handling.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-print-notifications.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Printer notifications.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-wwan.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME WWan management.
déc. 16 11:32:21 jpb-MS-7A70 gsd-color[1655]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PLX2283H_1159483586318_jpb_1000
déc. 16 11:32:21 jpb-MS-7A70 gsd-color[1655]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PLE431_05197G4427828_jpb_1000
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-xsettings.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME XSettings.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME X11 Session (session: ubuntu).
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Current graphical user session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: unicast-local-avahi.path: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Path trigger for Avahi .local domain notifications.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: update-notifier-crash.path: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Path trigger for Apport crash notifications.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: update-notifier-release.path: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Path trigger for new release of Ubuntu notifications.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME session X11 services.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME X11 Session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session (session: ubuntu).
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session is initialized.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Shell on X11.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping GNOME Shell on X11...
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping GNOME Terminal Server...
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-terminal-server.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Terminal Server.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: vte-spawn-7231d5ee-a595-43fb-aa81-7b62394fc50a.scope: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-session-manager@ubuntu.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Session Manager (session: ubuntu).
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Object Meta.BackgroundActor (0x555eed88f6e0), has been already deallocated — 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #0 7ffd97afd050 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (23abe98b6c40 @ 25)
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #1 555ef0156550 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (34d52deaf088 @ 85)
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #2 555ef01564c8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (34d52deabe20 @ 12)
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
_init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
_onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45
_init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Object Meta.BackgroundActor (0x555eed88fab0), has been already deallocated — 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #0 7ffd97afd050 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (23abe98b6c40 @ 25)
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #1 555ef0156550 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (34d52deaf088 @ 85)
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #2 555ef01564c8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (34d52deabe20 @ 12)
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
_init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
_onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45
_init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555eeeb75e60.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555ef2ae9290.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555ef2ae9290.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef2afa670.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eecc32d00.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eecc32d00.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed15f470.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eec1dfac0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eec1dfac0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eecd43f70.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 ==
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed67c490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed67c490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed9dbc70.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed8338a0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed8338a0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb38b70.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed82f3e0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed82f3e0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef1350bb0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeba15490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeba15490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef1613bf0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed835590.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed835590.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eefe856e0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed865b00.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed865b00.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eee2705b0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb58a690.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb58a690.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb57a670.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb6b9490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb6b9490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb6c1670.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eee3f6e60.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eee3f6e60.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb5fc40.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd03c30.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd03c30.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb3da60.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb589090.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb589090.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb595a70.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedce32d0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedce32d0.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb92e070.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd98490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd98490.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed89dc70.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was notify on NMDeviceEthernet 0x555eed94c240.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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.
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was state-changed on NMDeviceEthernet 0x555eed94c240.
déc. 16 11:32:21 jpb-MS-7A70 polkitd(authority=local)[516]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.86, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus)
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-shell-x11.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Shell on X11.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session Manager is ready.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Tasks to be run before GNOME Session starts.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Session services which should run early before the graphical session is brought up.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Reached target Shutdown running GNOME Session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping Start gnome-keyring as SSH agent...
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping Monitor Session leader for GNOME Session...
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Starting Restart DBus after GNOME Session shutdown...
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Shutdown running GNOME Session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-keyring-ssh.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Start gnome-keyring as SSH agent.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Reached target Shutdown running GNOME Session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Shutdown running GNOME Session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Started Restart DBus after GNOME Session shutdown.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-session-monitor.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Monitor Session leader for GNOME Session.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping D-Bus User Message Bus...
déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-fs[2878]: Received signal:15->'Complété'
déc. 16 11:32:21 jpb-MS-7A70 gvfsd[2890]: A connection to the bus can't be made
déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-f[2878]: Error while sending AddMatch() message: La connexion est fermée
déc. 16 11:32:21 jpb-MS-7A70 gvfsd[4206]: A connection to the bus can't be made
déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-f[2878]: Error while sending AddMatch() message: La connexion est fermée
déc. 16 11:32:21 jpb-MS-7A70 gvfsd[4192]: A connection to the bus can't be made
déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-f[2878]: Error while sending AddMatch() message: La connexion est fermée
déc. 16 11:32:21 jpb-MS-7A70 gvfsd[3242]: A connection to the bus can't be made
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-fs[2878]: OK
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: run-user-1000-gvfs.mount: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: dbus.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "27"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event2 - Power Button: device removed
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped D-Bus User Message Bus.
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "30"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event7 - Video Bus: device removed
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "31"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event1 - Power Button: device removed
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "32"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event0 - Sleep Button: device removed
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "33"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event6 - UVC Camera (046d:081b): device removed
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "34"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event5 - Logitech Wireless Mouse PID:0036: device removed
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-udisks2-volume-monitor.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "35"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "36"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event3 - AT Translated Set 2 keyboard: device removed
déc. 16 11:32:21 jpb-MS-7A70 systemd[1330]: run-user-1000-gvfs.mount: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-gphoto2-volume-monitor.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-mtp-volume-monitor.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-afc-volume-monitor.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[1]: run-user-1000-gvfs.mount: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[1330]: run-user-1000-doc.mount: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "35"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event4 - Logitech Wireless Keyboard PID:0056: device removed
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: run-user-1000-doc.mount: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-goa-volume-monitor.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-permission-store.service: Failed with result 'exit-code'.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: evolution-source-registry.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[1]: run-user-1000-doc.mount: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-metadata.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: evolution-addressbook-factory.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-session-restart-dbus.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Started D-Bus User Message Bus.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-daemon.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: tracker-miner-fs.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 dbus-daemon[10129]: [session uid=1000 pid=10129] AppArmor D-Bus mediation is enabled
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: evolution-calendar-factory.service: Succeeded.
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-document-portal.service: Failed with result 'exit-code'.
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: not releasing fd for 13:68, still in use
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:67
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:68
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:69
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:70
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:64
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:65
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:71
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput"
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:66
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) Server terminated successfully (0). Closing log file.
déc. 16 11:32:21 jpb-MS-7A70 gdm-password][2853]: pam_unix(gdm-password:session): session closed for user jpb
déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[1336]: Failed to find a working profile.
déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[1336]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" card_name="alsa_card.usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:65
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:71
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:68
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:66
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:64
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:67
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:69
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:70
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 226:0
déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) AIGLX: Resuming AIGLX clients after VT switch
déc. 16 11:32:21 jpb-MS-7A70 kernel: rfkill: input handler disabled
déc. 16 11:32:21 jpb-MS-7A70 systemd-logind[532]: Session 2 logged out. Waiting for processes to exit.
déc. 16 11:32:21 jpb-MS-7A70 rtkit-daemon[1366]: Supervising 6 threads of 2 processes of 2 users.
déc. 16 11:32:21 jpb-MS-7A70 rtkit-daemon[1366]: Successfully made thread 10131 of process 2876 owned by '1000' RT at priority 5.
déc. 16 11:32:21 jpb-MS-7A70 rtkit-daemon[1366]: Supervising 7 threads of 2 processes of 2 users.
déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[2876]: After module unload, module 'module-null-sink' was still loaded!
déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: pulseaudio.service: Succeeded.
jpb@jpb-MS-7A70:~$ PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#14 Le 17/12/2020, à 17:59
- ar barzh paour
Re : journal pollué
dans le journal du 24/10
j'ai aussi trouvé de très nombreux messages
#24/10 ligne 4393 à 13540
#oct. 24 16:04:52 jpb-MS-7A70 gnome-shell[2654]: == Stack trace for context 0x560cb7145900 ==
#oct. 24 16:04:52 jpb-MS-7A70 gnome-shell[2654]: #0 7ffe89306c80 b /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:594 (1a5f8a3ac790 @ 22)
#oct. 24 16:04:52 jpb-MS-7A70 gnome-shell[2654]: #1 7ffe89306d00 I self-hosted:1015 (2785a95e9448 @ 537)
#oct. 24 16:04:52 jpb-MS-7A70 gnome-shell[2654]: #2 7ffe89307db0 b /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:153 (1a5f8a39e9e8 @ 1021)
#13541 à 15639
#oct. 24 16:04:53 jpb-MS-7A70 gnome-shell[2654]: == Stack trace for context 0x560cb7145900 ==
#15641 à 15795
#oct. 24 16:04:55 jpb-MS-7A70 gnome-shell[2654]: The offending callback was SourceFunc().
#oct. 24 16:04:55 jpb-MS-7A70 gnome-shell[2654]: 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.
#rebelote 15796 à 49393
#oct. 24 16:04:55 jpb-MS-7A70 gnome-shell[2654]: == Stack trace for context 0x560cb7145900 ==
#oct. 24 16:05:10 jpb-MS-7A70 gnome-shell[2654]: == Stack trace for context 0x560cb7145900 ==
#oct. 24 16:05:25 jpb-MS-7A70 systemd-journald[274]: Suppressed 38045 messages from user@1000.service
#oct. 24 16:05:55 jpb-MS-7A70 systemd-journald[274]: Suppressed 65142 messages from user@1000.service
# dernière ligne 54164 Journal stoppedPC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#15 Le 17/12/2020, à 18:37
- ar barzh paour
Re : journal pollué
@geole
que veux dire cette option de journalctl ?
--no-pager
Do not pipe output into a pager.
--no-pager
Ne dirige pas la sortie vers un pager.PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#16 Le 17/12/2020, à 19:11
- ar barzh paour
Re : journal pollué
j'ai récupéré les messages de décembre
journalctl -S "2020-12-01 00:00:01" -U "2020-12-16 23:59:59" > journalctl-T-2020-12-01-a-16.txtle fichier fait 396MB
j'ai supprimé les message contenant JS ERROR et les lignes qui commencent par des espaces
journalctl -S "2020-12-01 00:00:01" -U "2020-12-16 23:59:59" |grep -v 'JS ERROR' | grep -v '^ *' > journalctl-F-2020-12-01-a-16.txtle fichier fait 29,7MB
j'ai divisé par 15 le poids des messages !!!!!
j'ai aussi trouvé une pollution avec ce genre de message
audit[xxxx]: AVC apparmor="DENIED"........
Dernière modification par ar barzh paour (Le 17/12/2020, à 19:36)
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#17 Le 17/12/2020, à 20:48
- geole
Re : journal pollué
ar barzh paour a écrit :
jpb@jpb-MS-7A70:~$ journalctl --no-pager --since "2020-12-16 11:32:20" --until "2020-12-16 11:32:22" -- Logs begin at Fri 2020-09-18 15:00:57 CEST, end at Thu 2020-12-17 16:53:18 CET. -- déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Media keys handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Maintenance of expirable data. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Freedesktop screensaver handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-housekeeping.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Maintenance of expirable data. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-screensaver-proxy.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Freedesktop screensaver handling. déc. 16 11:32:21 jpb-MS-7A70 kernel: rfkill: input handler enabled déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME RFKill handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-media-keys.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Media keys handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Accessibility settings. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Sound sample caching handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME XSettings. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-a11y-settings.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Accessibility settings. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Sharing handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Power management handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-rfkill.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME RFKill handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Color management. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Smartcard handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME USB protection handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Keyboard handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-keyboard.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Keyboard handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-sharing.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Sharing handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: at-spi-dbus-bus.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Date & Time handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-power.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Power management handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-smartcard.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Smartcard handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-usb-protection.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME USB protection handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Wacom handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME WWan management. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-wacom.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Wacom handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-sound.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Sound sample caching handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Printer notifications. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-color.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Color management. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-datetime.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Date & Time handling. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-print-notifications.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Printer notifications. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-wwan.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME WWan management. déc. 16 11:32:21 jpb-MS-7A70 gsd-color[1655]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PLX2283H_1159483586318_jpb_1000 déc. 16 11:32:21 jpb-MS-7A70 gsd-color[1655]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PLE431_05197G4427828_jpb_1000 déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gsd-xsettings.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME XSettings. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME X11 Session (session: ubuntu). déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Current graphical user session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: unicast-local-avahi.path: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Path trigger for Avahi .local domain notifications. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: update-notifier-crash.path: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Path trigger for Apport crash notifications. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: update-notifier-release.path: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Path trigger for new release of Ubuntu notifications. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME session X11 services. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME X11 Session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session (session: ubuntu). déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session is initialized. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Shell on X11. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping GNOME Shell on X11... déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping GNOME Terminal Server... déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-terminal-server.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Terminal Server. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: vte-spawn-7231d5ee-a595-43fb-aa81-7b62394fc50a.scope: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-session-manager@ubuntu.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Session Manager (session: ubuntu). déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Object Meta.BackgroundActor (0x555eed88f6e0), has been already deallocated — 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #0 7ffd97afd050 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (23abe98b6c40 @ 25) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #1 555ef0156550 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (34d52deaf088 @ 85) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #2 555ef01564c8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (34d52deabe20 @ 12) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24 _onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45 _init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Object Meta.BackgroundActor (0x555eed88fab0), has been already deallocated — 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #0 7ffd97afd050 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (23abe98b6c40 @ 25) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #1 555ef0156550 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (34d52deaf088 @ 85) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #2 555ef01564c8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (34d52deabe20 @ 12) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24 _onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45 _init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555eeeb75e60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555ef2ae9290. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555ef2ae9290. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef2afa670. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eecc32d00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eecc32d00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed15f470. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eec1dfac0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eec1dfac0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eecd43f70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed67c490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed67c490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed9dbc70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed8338a0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed8338a0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb38b70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed82f3e0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed82f3e0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef1350bb0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeba15490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeba15490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef1613bf0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed835590. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed835590. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eefe856e0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed865b00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed865b00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eee2705b0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb58a690. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb58a690. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb57a670. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb6b9490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb6b9490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb6c1670. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eee3f6e60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eee3f6e60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb5fc40. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd03c30. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd03c30. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb3da60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb589090. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb589090. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb595a70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedce32d0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedce32d0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb92e070. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd98490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd98490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed89dc70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was notify on NMDeviceEthernet 0x555eed94c240. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was state-changed on NMDeviceEthernet 0x555eed94c240. déc. 16 11:32:21 jpb-MS-7A70 polkitd(authority=local)[516]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.86, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus) déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-shell-x11.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped GNOME Shell on X11. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target GNOME Session Manager is ready. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Tasks to be run before GNOME Session starts. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Session services which should run early before the graphical session is brought up. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Reached target Shutdown running GNOME Session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping Start gnome-keyring as SSH agent... déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping Monitor Session leader for GNOME Session... déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Starting Restart DBus after GNOME Session shutdown... déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Shutdown running GNOME Session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-keyring-ssh.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Start gnome-keyring as SSH agent. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Reached target Shutdown running GNOME Session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped target Shutdown running GNOME Session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Started Restart DBus after GNOME Session shutdown. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-session-monitor.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped Monitor Session leader for GNOME Session. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopping D-Bus User Message Bus... déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-fs[2878]: Received signal:15->'Complété' déc. 16 11:32:21 jpb-MS-7A70 gvfsd[2890]: A connection to the bus can't be made déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-f[2878]: Error while sending AddMatch() message: La connexion est fermée déc. 16 11:32:21 jpb-MS-7A70 gvfsd[4206]: A connection to the bus can't be made déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-f[2878]: Error while sending AddMatch() message: La connexion est fermée déc. 16 11:32:21 jpb-MS-7A70 gvfsd[4192]: A connection to the bus can't be made déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-f[2878]: Error while sending AddMatch() message: La connexion est fermée déc. 16 11:32:21 jpb-MS-7A70 gvfsd[3242]: A connection to the bus can't be made déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-fs[2878]: OK déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: run-user-1000-gvfs.mount: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: dbus.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "27" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event2 - Power Button: device removed déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Stopped D-Bus User Message Bus. déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "30" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event7 - Video Bus: device removed déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "31" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event1 - Power Button: device removed déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "32" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event0 - Sleep Button: device removed déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "33" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event6 - UVC Camera (046d:081b): device removed déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "34" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event5 - Logitech Wireless Mouse PID:0036: device removed déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-udisks2-volume-monitor.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "35" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "36" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event3 - AT Translated Set 2 keyboard: device removed déc. 16 11:32:21 jpb-MS-7A70 systemd[1330]: run-user-1000-gvfs.mount: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-gphoto2-volume-monitor.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-mtp-volume-monitor.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-afc-volume-monitor.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[1]: run-user-1000-gvfs.mount: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[1330]: run-user-1000-doc.mount: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (**) Option "fd" "35" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) event4 - Logitech Wireless Keyboard PID:0056: device removed déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: run-user-1000-doc.mount: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-goa-volume-monitor.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-permission-store.service: Failed with result 'exit-code'. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: evolution-source-registry.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[1]: run-user-1000-doc.mount: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-metadata.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: evolution-addressbook-factory.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gnome-session-restart-dbus.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: Started D-Bus User Message Bus. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: gvfs-daemon.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: tracker-miner-fs.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 dbus-daemon[10129]: [session uid=1000 pid=10129] AppArmor D-Bus mediation is enabled déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: evolution-calendar-factory.service: Succeeded. déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: xdg-document-portal.service: Failed with result 'exit-code'. déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: not releasing fd for 13:68, still in use déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:67 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:68 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:69 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:70 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:64 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:65 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:71 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) UnloadModule: "libinput" déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) systemd-logind: releasing fd for 13:66 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[2959]: (II) Server terminated successfully (0). Closing log file. déc. 16 11:32:21 jpb-MS-7A70 gdm-password][2853]: pam_unix(gdm-password:session): session closed for user jpb déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[1336]: Failed to find a working profile. déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[1336]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" card_name="alsa_card.usb-E-MU_Systems__Inc._E-MU_XMidi1X1_E-MU-31-3F07-07D90504-0BE10-STATION_02-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:65 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:71 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:68 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:66 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:64 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:67 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:69 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 13:70 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) systemd-logind: got resume for 226:0 déc. 16 11:32:21 jpb-MS-7A70 /usr/lib/gdm3/gdm-x-session[1453]: (II) AIGLX: Resuming AIGLX clients after VT switch déc. 16 11:32:21 jpb-MS-7A70 kernel: rfkill: input handler disabled déc. 16 11:32:21 jpb-MS-7A70 systemd-logind[532]: Session 2 logged out. Waiting for processes to exit. déc. 16 11:32:21 jpb-MS-7A70 rtkit-daemon[1366]: Supervising 6 threads of 2 processes of 2 users. déc. 16 11:32:21 jpb-MS-7A70 rtkit-daemon[1366]: Successfully made thread 10131 of process 2876 owned by '1000' RT at priority 5. déc. 16 11:32:21 jpb-MS-7A70 rtkit-daemon[1366]: Supervising 7 threads of 2 processes of 2 users. déc. 16 11:32:21 jpb-MS-7A70 pulseaudio[2876]: After module unload, module 'module-null-sink' was still loaded! déc. 16 11:32:21 jpb-MS-7A70 systemd[2866]: pulseaudio.service: Succeeded. jpb@jpb-MS-7A70:~$
Pour cet incident, je n'ai pas trouvé grand chose.
Il semble que la session utilisateur soit déconnectée sauvagement. Tu devrais t'en rendre compte si tel est le cas. J'ai cherché sur pas mal de phrases clés
Celle qui me semble avoir un sens est
Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct
Mais cela aboutit sur quelque chose de résolu:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1066
Qui est lié au touch pad. L'utilises-tu?
https://bugs.launchpad.net/ubuntu/+sour … ug/1892245.
Le fait de mettre l'option --no-pager permet de ne pas bloquer toutes les 24 lignes d'affichage et evite donc à l'utilisateur d'appuyer sur entrée pour que la suite s'affiche
Si tu as retrouvé un autre cas, regarde quand tu l'as eu et récupère de la seconde qui précède à la seconde qui suit et poste.
Inutile de trop remonter le temps pour regarder comment un ancien noyau fonctionnait.
Bonne soirée
Dernière modification par geole (Le 17/12/2020, à 20:56)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
En ligne
#18 Le 18/12/2020, à 11:48
- ar barzh paour
Re : journal pollué
@geole
merci pour tes recherches , je ne sais pas comment on recherche si un incident "identique" est déjà arrivé
j'ai recherché sur le net
"JS ERROR: TypeError: actor.get_meta_window(...) is null"
est-ce la bonne méthode ?
je vais regarder ce que donne Window Manager .....
pas de touchpad sur mon PC
le paquet gnome-shell-extension-dash-to-panel n'est pas chargé chez moi
autre remarque : mon PC fonctionne bien , je ne me suis jamais aperçu de dysfonctionnement important
ce n'est qu'en fouillant dans le journal sur cette discussion (où tu es également intervenu)
https://forum.ubuntu-fr.org/viewtopic.php?id=2059748
j'ai voulu chercher des traces de messages et j'ai vu que le journal me semblait avoir une taille trop importante et que certazins jours je n'arrivais même pas à en lire le contenu
tu dis
Pour cet incident, je n'ai pas trouvé grand chose.
de quel incident parles-tu ? (par rapport aux messages)
Inutile de trop remonter le temps pour regarder comment un ancien noyau fonctionnait.
c'était pour pouvoir diminuer la taille du journal pour pouvoir le consulter , mais maintenant avec les options -S -U et des grep je sais filtrer
comme j'ai deux écrans , j'ai ouvert sur l'un deux via autostart
journalctl -fet je peux observer les messages qui défilent
Dernière modification par ar barzh paour (Le 18/12/2020, à 12:05)
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#19 Le 18/12/2020, à 19:28
- geole
Re : journal pollué
Pendant ces deux secondes, il s'est passé pas mal de choses
On voit que la session s'arrête. Normal ou pas, il n'y a que toi qui peut le savoir.
J'ai noté que tu n'as pas de touchpad. Donc je suis à coté de la plaque
Je ne conserve que l'erreur flagrante.
ar barzh paour a écrit :
jpb@jpb-MS-7A70:~$ journalctl --no-pager --since "2020-12-16 11:32:20" --until "2020-12-16 11:32:22" déc. 16 11:32:21 jpb-MS-7A70 gsd-color[1655]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PLX2283H_1159483586318_jpb_1000 déc. 16 11:32:21 jpb-MS-7A70 gsd-color[1655]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PLE431_05197G4427828_jpb_1000 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Object Meta.BackgroundActor (0x555eed88f6e0), has been already deallocated — 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #0 7ffd97afd050 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (23abe98b6c40 @ 25) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #1 555ef0156550 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (34d52deaf088 @ 85) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #2 555ef01564c8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (34d52deabe20 @ 12) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24 _onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45 _init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: Object Meta.BackgroundActor (0x555eed88fab0), has been already deallocated — 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #0 7ffd97afd050 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (23abe98b6c40 @ 25) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #1 555ef0156550 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (34d52deaf088 @ 85) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: #2 555ef01564c8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (34d52deabe20 @ 12) déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24 _onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45 _init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56 déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555eeeb75e60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555ef2ae9290. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555ef2ae9290. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef2afa670. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eecc32d00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eecc32d00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed15f470. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eec1dfac0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eec1dfac0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eecd43f70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: == Stack trace for context 0x555eeab42900 == déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed67c490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed67c490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed9dbc70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed8338a0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed8338a0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb38b70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed82f3e0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed82f3e0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef1350bb0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeba15490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeba15490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555ef1613bf0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed835590. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed835590. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eefe856e0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed865b00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eed865b00. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eee2705b0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb58a690. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb58a690. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb57a670. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb6b9490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb6b9490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb6c1670. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eee3f6e60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eee3f6e60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb5fc40. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd03c30. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd03c30. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eedb3da60. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb589090. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eeb589090. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb595a70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedce32d0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedce32d0. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eeb92e070. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd98490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555eedd98490. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555eed89dc70. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555eed8a2850. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was notify on NMDeviceEthernet 0x555eed94c240. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: 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. déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: The offending signal was state-changed on NMDeviceEthernet 0x555eed94c240. déc. 16 11:32:21 jpb-MS-7A70 gvfsd[4192]: A connection to the bus can't be made déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-f[2878]: Error while sending AddMatch() message: La connexion est fermée déc. 16 11:32:21 jpb-MS-7A70 gvfsd[3242]: A connection to the bus can't be made déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 tracker-miner-fs[2878]: OK déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18) déc. 16 11:32:21 jpb-MS-7A70 evolution-calen[3197]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
Peut-être qu'en recherchant sur d'autres mots-clé on va trouver un problème connu.
===> https://bugs.launchpad.net/ubuntu/+sour … ug/1825197
Pourrais-tu rappeler ta version
cat /etc/lsb-releaseen tout cas, l'élément déclenchant la fermeture n'est pas listé. On va remonter un peu dans le temps
journalctl --no-pager --since "2020-12-16 11:30:00" --until "2020-12-16 11:32:20J'ai vu un contexte avec l'application wallpaperdownloader
Dernière modification par geole (Le 18/12/2020, à 19:52)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
En ligne
#20 Le 18/12/2020, à 19:37
- ar barzh paour
Re : journal pollué
jpb@jpb-MS-7A70:~$ journalctl --no-pager --since "2020-12-16 11:30:00" --until "2020-12-16 11:32:20"
-- Logs begin at Fri 2020-09-18 15:00:57 CEST, end at Fri 2020-12-18 18:36:34 CET. --
déc. 16 11:30:01 jpb-MS-7A70 CRON[10048]: pam_unix(cron:session): session opened for user root by (uid=0)
déc. 16 11:30:01 jpb-MS-7A70 CRON[10049]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
déc. 16 11:30:01 jpb-MS-7A70 CRON[10048]: pam_unix(cron:session): session closed for user root
déc. 16 11:30:56 jpb-MS-7A70 systemd[1]: Started Run anacron jobs.
déc. 16 11:30:56 jpb-MS-7A70 anacron[10057]: Anacron 2.3 started on 2020-12-16
déc. 16 11:30:56 jpb-MS-7A70 anacron[10057]: Normal exit (0 jobs run)
déc. 16 11:30:56 jpb-MS-7A70 systemd[1]: anacron.service: Succeeded.
déc. 16 11:31:55 jpb-MS-7A70 systemd[2866]: vte-spawn-c356fb2f-a23c-4d29-bbad-59b6678a91f3.scope: Succeeded.
déc. 16 11:32:09 jpb-MS-7A70 gnome-shell[6414]: 232 code : 1
déc. 16 11:32:09 jpb-MS-7A70 gnome-shell[6414]: effacer les fichiers temporaires
déc. 16 11:32:19 jpb-MS-7A70 dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.86' (uid=1000 pid=3113 comm="/usr/bin/gnome-shell " label="unconfined")
déc. 16 11:32:19 jpb-MS-7A70 systemd[1]: Starting PackageKit Daemon...
déc. 16 11:32:19 jpb-MS-7A70 PackageKit[10085]: daemon start
déc. 16 11:32:19 jpb-MS-7A70 dbus-daemon[490]: [system] Successfully activated service 'org.freedesktop.PackageKit'
déc. 16 11:32:19 jpb-MS-7A70 systemd[1]: Started PackageKit Daemon.
jpb@jpb-MS-7A70:~$ PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#21 Le 18/12/2020, à 22:19
- soshy
Re : journal pollué
déc. 16 11:32:21 jpb-MS-7A70 gnome-shell[3113]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
_init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
_onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45gnome-shell/extensions/desktop-icons
Moi j'aurai tendance à dire que ça vient de l'extension pour avoir des icones sur le bureau...
Hors ligne
#22 Le 19/12/2020, à 16:23
- ar barzh paour
Re : journal pollué
@ soshy
pourquoi pas
mais en tout cas ce n'est pas moi qui ait installé cette extension
et comment je peux voir si elle est installée ?
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#23 Le 19/12/2020, à 16:36
- ylag
Re : journal pollué
Bonjour,
et comment je peux voir si elle est installée ?
Ce serait soit dans ton dossier ~/.local/share/gnome-shell/extensions ou /usr/share/gnome-shell/extensions
Sinon, installer l'utilitaire «Ajustements» par le paquet gnome-tweaks, si pas déjà fait, et sélectionner «Extensions» dans la partie gauche de la fenêtre pour avoir accès aux extensions installées chez-toi...?
A+
Dernière modification par ylag (Le 19/12/2020, à 16:37)
Hors ligne
#24 Le 19/12/2020, à 17:55
- ar barzh paour
Re : journal pollué
quelques traces mais ça ne me dit pas grand chose !!
jpb@jpb-MS-7A70:/usr/share$ 2>/dev/null ls -ailR / |grep desktop-icon
2078965 lr-------- 1 jpb jpb 64 déc. 19 16:53 7fb948779000-7fb94877a000 -> /usr/share/locale-langpack/fr/LC_MESSAGES/desktop-icons.mo
1180331 -rwxr-xr-x 1 root root 20638 nov. 24 18:16 xdg-desktop-icon
1967721 drwxr-xr-x 2 root root 4096 sept. 7 18:48 gnome-shell-extension-desktop-icons
/usr/share/doc/gnome-shell-extension-desktop-icons:
1837417 -rw-r--r-- 1 root root 1051 avril 3 2020 org.gnome.shell.extensions.desktop-icons.gschema.xml
2232314 drwxr-xr-x 2 root root 4096 sept. 7 18:48 desktop-icons@csoriano
/usr/share/gnome-shell/extensions/desktop-icons@csoriano:
2104815 -rw-r--r-- 1 root root 1058 juil. 10 10:56 desktop-icons.mo
2100102 -rw-r--r-- 1 root root 3232 juil. 10 11:10 desktop-icons.mo
2521162 -rw-r--r-- 1 root root 2655 nov. 24 18:16 xdg-desktop-icon.1.gz
2232093 -rw-r--r-- 1 root root 1257 sept. 7 18:48 gnome-shell-extension-desktop-icons.list
2231960 -rw-r--r-- 1 root root 1472 juil. 21 18:30 gnome-shell-extension-desktop-icons.md5sums
jpb@jpb-MS-7A70:/usr/share$ Dernière modification par ar barzh paour (Le 19/12/2020, à 18:05)
PC : B760M DS3H DDR4, 12th Gen Intel(R) Core(TM) i3-12100, RAM DDR4 8GiB -2400 Ubuntu 20.04, 22.04, 24.04 (en test )
Portable1 : ThinkPad P50 I7-6820HQ, 16G0 Ram Ubuntu 22.04 Ubuntu 24.04 , W10-PRO( en voyage )
Portable2 : T5750 @ 2.00GHz RAM 1GiB DDR2 667 Mhz Ubuntu 20.04 ( batterie HS )
stourm a ran war bep tachenn (Angela Duval) ( Je combats sur tous les fronts )
Hors ligne
#25 Le 19/12/2020, à 18:07
- Compte anonymisé
Re : journal pollué
L’extension Desktop icons est installée avec l'environnement de bureau par défaut de Ubuntu. Pour vérifier qu’elle n'est pas responsable de la "pollution", il suffit de la désactiver, de redémarrer GNOME Shell, et de voir si il y a autant de logs.