Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

Pages : 1

#1 Le 18/02/2023, à 23:18

winguru

arret PC ne fonctionne pas

bonjour
j'ai décidé de dédier un pc a ubuntu pour decouvrir
j'ai telechargé puis installé la version 22.04 puis les mise a jour proposées
tout a l'air de bien fonctionner sauf que je ne peux plus arreter le PC
je n'ai pas trouvé de bouton d'arrêt
il n'y a que en cliquant sur l'icone de la batterie j'ai la fonction eteindre...
l'cran vire au noir mais le PC ne s'arrete pas
je dois maintenir le bouton arret jusqu'à l’extinction...
je suis débutant
merci pour votre aide

Hors ligne

#2 Le 18/02/2023, à 23:32

xubu1957

Re : arret PC ne fonctionne pas

Bonjour,

Donne le retour de :

sudo apt update

d'éventuels paquets cassés :

dpkg -l | grep -v ^ii

et :

ls -l /var/crash

en te servant du Retour utilisable de commande.

↓↓↓↓↓↓↓

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

En ligne

#3 Le 19/02/2023, à 09:39

Sciensous

Re : arret PC ne fonctionne pas

pour l'extinction: clic sur la flèche à coté du "bouton extinction" /Paramètres  puis à gauche Énergie
voir l'option proposée

sous ubuntu LTS de la 06 à la 22.04, puis arrêt pour Debian 12 et antiX 21 ou 23
( sous LXDE et gnome-shell )

Hors ligne

#4 Le 04/03/2023, à 09:28

winguru

Re : arret PC ne fonctionne pas

linux@Linux:~$ sudo apt update
[sudo] Mot de passe de linux :
Réception de :1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Atteint :2 http://fr.archive.ubuntu.com/ubuntu jammy InRelease       
Atteint :3 http://fr.archive.ubuntu.com/ubuntu jammy-updates InRelease
Atteint :4 http://fr.archive.ubuntu.com/ubuntu jammy-backports InRelease
110 ko réceptionnés en 1s (120 ko/s)                                 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait     
7 paquets peuvent être mis à jour. Exécutez « apt list --upgradable » pour les voir.
linux@Linux:~$ ^C
linux@Linux:~$ apt list --upgradable
En train de lister... Fait
gnome-remote-desktop/jammy-updates 42.7-0ubuntu1 amd64 [pouvant être mis à jour depuis : 42.3-0ubuntu1]
grub-efi-amd64-bin/jammy-updates 2.06-2ubuntu14.1 amd64 [pouvant être mis à jour depuis : 2.06-2ubuntu14]
grub-efi-amd64-signed/jammy-updates 1.187.3~22.04.1+2.06-2ubuntu14.1 amd64 [pouvant être mis à jour depuis : 1.187.2+2.06-2ubuntu14]
python3-software-properties/jammy-updates,jammy-updates 0.99.22.6 all [pouvant être mis à jour depuis : 0.99.22.2]
software-properties-common/jammy-updates,jammy-updates 0.99.22.6 all [pouvant être mis à jour depuis : 0.99.22.2]
software-properties-gtk/jammy-updates,jammy-updates 0.99.22.6 all [pouvant être mis à jour depuis : 0.99.22.2]
ubuntu-advantage-tools/jammy-updates 27.13.6~22.04.1 amd64 [pouvant être mis à jour depuis : 27.9~22.04.1]

Hors ligne

#5 Le 04/03/2023, à 09:31

winguru

Re : arret PC ne fonctionne pas

pkg -l | grep -v ^ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom                                        Version                                 Architecture Description
+++-==========================================-=======================================-============-================================================================================
rc  linux-image-5.15.0-43-generic              5.15.0-43.46                            amd64        Signed kernel image generic
rc  linux-modules-5.15.0-43-generic            5.15.0-43.46                            amd64        Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.15.0-43-generic      5.15.0-43.46                            amd64        Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP

Hors ligne

#6 Le 04/03/2023, à 09:32

xubu1957

Re : arret PC ne fonctionne pas

Pour ajouter toi-même les balises code à ton message #4 :

  • Cliquer sur  le lien « Modifier » en bas à droite du message

  • Sélectionner le texte

  • Cliquer sur le <> de l'éditeur de message

moko138 a écrit :

1) Les balises-code sont les < > (crochets bleus) de la barre de mise en forme.
Balisesmoko138.jpg
_ _ _

3) /!\  Si vous avez plusieurs retours à donner, séparez-les bien (toujours pour la lisibilité) :

comme
cela.
linux@Linux:~$ sudo apt update
[sudo] Mot de passe de linux :
Réception de :1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Atteint :2 http://fr.archive.ubuntu.com/ubuntu jammy InRelease       
Atteint :3 http://fr.archive.ubuntu.com/ubuntu jammy-updates InRelease
Atteint :4 http://fr.archive.ubuntu.com/ubuntu jammy-backports InRelease
110 ko réceptionnés en 1s (120 ko/s)                                 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait     
7 paquets peuvent être mis à jour. Exécutez « apt list --upgradable » pour les voir.
linux@Linux:~$ ^C
linux@Linux:~$ apt list --upgradable
En train de lister... Fait
gnome-remote-desktop/jammy-updates 42.7-0ubuntu1 amd64 [pouvant être mis à jour depuis : 42.3-0ubuntu1]
grub-efi-amd64-bin/jammy-updates 2.06-2ubuntu14.1 amd64 [pouvant être mis à jour depuis : 2.06-2ubuntu14]
grub-efi-amd64-signed/jammy-updates 1.187.3~22.04.1+2.06-2ubuntu14.1 amd64 [pouvant être mis à jour depuis : 1.187.2+2.06-2ubuntu14]
python3-software-properties/jammy-updates,jammy-updates 0.99.22.6 all [pouvant être mis à jour depuis : 0.99.22.2]
software-properties-common/jammy-updates,jammy-updates 0.99.22.6 all [pouvant être mis à jour depuis : 0.99.22.2]
software-properties-gtk/jammy-updates,jammy-updates 0.99.22.6 all [pouvant être mis à jour depuis : 0.99.22.2]
ubuntu-advantage-tools/jammy-updates 27.13.6~22.04.1 amd64 [pouvant être mis à jour depuis : 27.9~22.04.1]

#5 :

dpkg -l | grep -v ^ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom                                        Version                                 Architecture Description
+++-==========================================-=======================================-============-================================================================================
rc  linux-image-5.15.0-43-generic              5.15.0-43.46                            amd64        Signed kernel image generic
rc  linux-modules-5.15.0-43-generic            5.15.0-43.46                            amd64        Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.15.0-43-generic      5.15.0-43.46                            amd64        Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP

        _ _ _

(edit=messages regroupés)
        _ _ _

Lance :

sudo apt full-upgrade

Indique aussi la carte graphique :

lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"

Méthode détaillée :

cqfd93 a écrit :

Bonjour,

Entrer des commandes dans un terminal et donner le résultat - Voilà la marche à suivre :

  1. Ouvre le terminal avec ctrl-alt-t

  2. Sélectionne la commande voulue avec un triple clic (ça sélectionne toute la ligne, même la fin si on ne la voit pas)

  3. Colle-la dans le terminal avec un clic molette, valide avec Entrée

  4. Sélectionne et copie tout ce que te dit le terminal depuis la commande jusqu'à la dernière ligne incluse

  5. Clique sur le <> de l'éditeur de message

    1642675956.jpg

  6. Colle là où se trouve le curseur (entre le ] et le [)

  7. Refais toutes les étapes depuis la 2 pour les autres commandes.

Lecture conseillée > memento des balises code.

Dernière modification par xubu1957 (Le 04/03/2023, à 10:08)

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

En ligne

#7 Le 04/03/2023, à 09:33

winguru

Re : arret PC ne fonctionne pas

linux@Linux:~$ ls -l /var/crash
total 0

Hors ligne

#8 Le 04/03/2023, à 09:39

winguru

Re : arret PC ne fonctionne pas

carte graphique
linux@Linux:~$ lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT216M [GeForce GT 320M] [10de:0a2d] (rev a2) (prog-if 00 [VGA controller])
    Kernel driver in use: nouveau
    Kernel modules: nvidiafb, nouveau

Hors ligne

#9 Le 04/03/2023, à 09:43

winguru

Re : arret PC ne fonctionne pas

je comprends pas les mots balise et codes... je fais des copie coller c'est pasq bien ?

linux@Linux:~$ lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT216M [GeForce GT 320M] [10de:0a2d] (rev a2) (prog-if 00 [VGA controller])
	Kernel driver in use: nouveau
	Kernel modules: nvidiafb, nouveau

Hors ligne

#10 Le 04/03/2023, à 09:47

winguru

Re : arret PC ne fonctionne pas

haaa ok

Hors ligne

#11 Le 04/03/2023, à 09:50

winguru

Re : arret PC ne fonctionne pas

linux@Linux:~$ sudo apt full-upgrade
[sudo] Mot de passe de linux : 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait      
Calcul de la mise à jour... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
  libflashrom1 libftdi1-2 libllvm13
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
Les paquets suivants ont été conservés :
  gnome-remote-desktop grub-efi-amd64-bin grub-efi-amd64-signed
  python3-software-properties software-properties-common
  software-properties-gtk ubuntu-advantage-tools
0 mis à jour, 0 nouvellement installés, 0 à enlever et 7 non mis à jour.

Hors ligne

#12 Le 04/03/2023, à 09:56

winguru

Re : arret PC ne fonctionne pas

3 petites choses...
1 - grand merci pour votre aide et compréhension...
2 - j'ai essayé d'eteindre le PC après les maj maisça marche pas
3- l'interface linux me plait beaucoup

Hors ligne

#13 Le 04/03/2023, à 09:59

winguru

Re : arret PC ne fonctionne pas

je peux peut être telecharger une version plus ancienne et reinstaller le PC

Hors ligne

#14 Le 04/03/2023, à 10:03

xubu1957

Re : arret PC ne fonctionne pas

Montre aussi :

ubuntu-drivers devices

et :

echo $XDG_SESSION_TYPE

pour voir si c'est Wayland ou x11.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

En ligne

#15 Le 04/03/2023, à 10:13

geole

Re : arret PC ne fonctionne pas

Bonjour.
Merci de donner la fin de la trace de la dernière session

journalctl  -b -1 | tail -500

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity

Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#16 Le 04/03/2023, à 10:14

winguru

Re : arret PC ne fonctionne pas

le premier n'a rien fait
le deuxieme : Wayland

linux@Linux:~$ ubuntu-drivers devices
linux@Linux:~$ echo $XDG_SESSION_TYPE
wayland
linux@Linux:~$

Hors ligne

#17 Le 04/03/2023, à 10:17

winguru

Re : arret PC ne fonctionne pas

linux@Linux:~$ journalctl  -b -1 | tail -500
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5559ed1f6440.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed605fc0.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed605fc0.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed605fc0.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed605fc0.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5559ed5e2460.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5559ed1f6440.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ee19d070.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ee19d070.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ee19d070.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ee19d070.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5559ed6536f0.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5559ed1f6440.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed681c60.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed681c60.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed681c60.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ed681c60.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5559ed654600.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5559ed1f6440.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ec816980.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ec816980.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ec816980.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ec816980.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5559edf676a0.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5559ed1f6440.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ecbe8100.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ecbe8100.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ecbe8100.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559ecbe8100.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5559ed202390.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5559ed1f6440.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559f0b78c30.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559f0b78c30.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559f0b78c30.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5559f0b78c30.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5559edb835a0.
mars 04 08:51:41 Linux gnome-shell[1074]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5559ed1f6440.
mars 04 08:51:41 Linux systemd[1]: Stopping PackageKit Daemon...
mars 04 08:51:41 Linux systemd[1]: plymouth-quit-wait.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Hold until boot process finishes up.
mars 04 08:51:41 Linux systemd[1]: Stopping Power Profiles daemon...
mars 04 08:51:41 Linux systemd[1]: Stopping System Logging Service...
mars 04 08:51:41 Linux systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
mars 04 08:51:41 Linux systemd[1]: snapd.seeded.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Wait until snapd is fully seeded.
mars 04 08:51:41 Linux systemd[1]: Stopping Snap Daemon...
mars 04 08:51:41 Linux systemd[1]: Condition check resulted in Ubuntu core (all-snaps) system shutdown helper setup service being skipped.
mars 04 08:51:41 Linux gnome-shell[1074]: 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.
mars 04 08:51:41 Linux gnome-shell[1074]: The offending callback was set_container(), a vfunc.
mars 04 08:51:41 Linux systemd[1]: Stopping Load/Save Random Seed...
mars 04 08:51:41 Linux systemd[1]: Stopping Desktop service for Ubuntu Advantage...
mars 04 08:51:41 Linux systemd[1]: Stopping Disk Manager...
mars 04 08:51:41 Linux systemd[1]: Stopping Daemon for power management...
mars 04 08:51:41 Linux unknown[689]: udisks daemon version 2.9.4 exiting
mars 04 08:51:41 Linux systemd[1]: accounts-daemon.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Accounts Service.
mars 04 08:51:41 Linux systemd[1]: cron.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Regular background program processing daemon.
mars 04 08:51:41 Linux systemd[1]: irqbalance.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped irqbalance daemon.
mars 04 08:51:41 Linux systemd[1]: networkd-dispatcher.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Dispatcher daemon for systemd-networkd.
mars 04 08:51:41 Linux systemd[1]: power-profiles-daemon.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Power Profiles daemon.
mars 04 08:51:41 Linux systemd[1]: rsyslog.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped System Logging Service.
mars 04 08:51:41 Linux systemd[1]: snapd.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Snap Daemon.
mars 04 08:51:41 Linux systemd[1]: snapd.service: Consumed 3.646s CPU time.
mars 04 08:51:41 Linux systemd[1]: udisks2.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Disk Manager.
mars 04 08:51:41 Linux systemd[1]: udisks2.service: Consumed 1.618s CPU time.
mars 04 08:51:41 Linux systemd[1]: ModemManager.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Modem Manager.
mars 04 08:51:41 Linux systemd[1]: colord.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Manage, Install and Generate Color Profiles.
mars 04 08:51:41 Linux systemd[1]: rtkit-daemon.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
mars 04 08:51:41 Linux systemd[1]: upower.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Daemon for power management.
mars 04 08:51:41 Linux systemd[1]: geoclue.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Location Lookup Service.
mars 04 08:51:41 Linux systemd[1]: packagekit.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped PackageKit Daemon.
mars 04 08:51:41 Linux systemd[1]: packagekit.service: Consumed 12.888s CPU time.
mars 04 08:51:41 Linux systemd[1]: ubuntu-advantage-desktop-daemon.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Desktop service for Ubuntu Advantage.
mars 04 08:51:41 Linux systemd[1]: alsa-restore.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Save/Restore Sound Card State.
mars 04 08:51:41 Linux systemd[1]: systemd-random-seed.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Load/Save Random Seed.
mars 04 08:51:41 Linux systemd[1]: kerneloops.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Tool to automatically collect and submit kernel crash signatures.
mars 04 08:51:41 Linux systemd[1]: session-1.scope: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Session 1 of User linux.
mars 04 08:51:41 Linux systemd-logind[680]: Session 1 logged out. Waiting for processes to exit.
mars 04 08:51:41 Linux dbus-daemon[644]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.36' (uid=0 pid=914 comm="/usr/sbin/gdm3 " label="unconfined")
mars 04 08:51:41 Linux systemd[1]: Requested transaction contradicts existing jobs: Transaction for colord.service/start is destructive (system-systemd\x2dfsck.slice has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:41 Linux dbus-daemon[644]: [system] Activation via systemd failed for unit 'colord.service': Transaction for colord.service/start is destructive (system-systemd\x2dfsck.slice has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:41 Linux systemd[1]: Requested transaction contradicts existing jobs: Transaction for accounts-daemon.service/start is destructive (local-fs-pre.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:41 Linux dbus-daemon[644]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Transaction for accounts-daemon.service/start is destructive (local-fs-pre.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:41 Linux systemd[1]: Stopped target Host and Network Name Lookups.
mars 04 08:51:41 Linux gdm3[914]: Gdm: Failed to contact accountsservice: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.Accounts : Transaction for accounts-daemon.service/start is destructive (local-fs-pre.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:41 Linux systemd[1]: Stopped target System Time Set.
mars 04 08:51:41 Linux systemd[1]: Stopping Authorization Manager...
mars 04 08:51:41 Linux systemd[1]: Stopping Switcheroo Control Proxy service...
mars 04 08:51:41 Linux systemd[1]: Stopping User Login Management...
mars 04 08:51:41 Linux systemd[1]: Stopping User Manager for UID 1000...
mars 04 08:51:41 Linux systemd[924]: Stopping Application launched by gnome-session-binary...
mars 04 08:51:41 Linux systemd[924]: Stopping Application launched by gnome-session-binary...
mars 04 08:51:41 Linux systemd[924]: Stopping Application launched by gnome-session-binary...
mars 04 08:51:41 Linux systemd[924]: Stopping Application launched by gnome-session-binary...
mars 04 08:51:41 Linux apport[4212]:  * Stopping automatic crash report generation: apport
mars 04 08:51:41 Linux systemd[924]: Stopping snap.snap-store.ubuntu-software.57cbd3cf-6ff1-4852-8280-08ee62f156b3.scope...
mars 04 08:51:41 Linux systemd[924]: Removed slice Slice /app/gnome-session-manager.
mars 04 08:51:41 Linux systemd[924]: Removed slice Slice /app/org.gnome.Terminal.
mars 04 08:51:41 Linux systemd[924]: app-org.gnome.Terminal.slice: Consumed 15.457s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopped target Main User Target.
mars 04 08:51:41 Linux systemd[1]: acpid.service: Deactivated successfully.
mars 04 08:51:41 Linux io.snapcraft.Settings[3329]: Exiting on terminated.
mars 04 08:51:41 Linux systemd[924]: Stopping D-Bus User Message Bus...
mars 04 08:51:41 Linux apport[4212]:    ...done.
mars 04 08:51:41 Linux systemd[1]: Stopped ACPI event daemon.
mars 04 08:51:41 Linux systemd[1]: polkit.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Authorization Manager.
mars 04 08:51:41 Linux systemd[1]: switcheroo-control.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[924]: Stopping User preferences database...
mars 04 08:51:41 Linux systemd[924]: Stopping Evolution address book service...
mars 04 08:51:41 Linux systemd[924]: Stopping Evolution calendar service...
mars 04 08:51:41 Linux systemd[924]: Stopping Evolution source registry...
mars 04 08:51:41 Linux systemd[924]: Stopping Virtual filesystem service - Apple File Conduit monitor...
mars 04 08:51:41 Linux systemd[924]: Stopping Virtual filesystem service...
mars 04 08:51:41 Linux systemd[924]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
mars 04 08:51:41 Linux systemd[1]: Stopped Switcheroo Control Proxy service.
mars 04 08:51:41 Linux systemd[924]: Stopping Virtual filesystem service - digital camera monitor...
mars 04 08:51:41 Linux systemd[924]: Stopping Virtual filesystem metadata service...
mars 04 08:51:41 Linux systemd[924]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
mars 04 08:51:41 Linux systemd[924]: Stopping Virtual filesystem service - disk device monitor...
mars 04 08:51:41 Linux systemd[924]: Stopping PipeWire Media Session Manager...
mars 04 08:51:41 Linux systemd[924]: Stopping Sound Service...
mars 04 08:51:41 Linux systemd[924]: Stopping Service for snap application snapd-desktop-integration.snapd-desktop-integration...
mars 04 08:51:41 Linux systemd[924]: Stopping Tracker file system data miner...
mars 04 08:51:41 Linux systemd[924]: Stopping Portal service (GNOME implementation)...
mars 04 08:51:41 Linux systemd[924]: Stopping Portal service (GTK/GNOME implementation)...
mars 04 08:51:41 Linux systemd[924]: Stopping Portal service...
mars 04 08:51:41 Linux systemd[924]: Stopping flatpak document portal service...
mars 04 08:51:41 Linux systemd[924]: Stopping sandboxed app permission store...
mars 04 08:51:41 Linux xdg-document-po[998]: Error releasing name org.freedesktop.portal.Documents: La connexion est fermée
mars 04 08:51:41 Linux systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Unmounted /run/user/1000/gvfs.
mars 04 08:51:41 Linux systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Unmounted /run/user/1000/doc.
mars 04 08:51:41 Linux systemd[924]: Stopped PipeWire Media Session Manager.
mars 04 08:51:41 Linux tracker-miner-fs-3[1583]: OK
mars 04 08:51:41 Linux systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
mars 04 08:51:41 Linux systemd[1]: gdm.service: Failed with result 'exit-code'.
mars 04 08:51:41 Linux systemd[1]: Stopped GNOME Display Manager.
mars 04 08:51:41 Linux systemd[1]: gdm.service: Triggering OnFailure= dependencies.
mars 04 08:51:41 Linux systemd[924]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Main process exited, code=exited, status=143/n/a
mars 04 08:51:41 Linux systemd[924]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'.
mars 04 08:51:41 Linux systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (swap.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:41 Linux systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (swap.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:41 Linux systemd[1]: apport.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped LSB: automatic crash report generation.
mars 04 08:51:41 Linux systemd[924]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration.
mars 04 08:51:41 Linux systemd[924]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 2.467s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopped Virtual filesystem service.
mars 04 08:51:41 Linux systemd-logind[680]: Removed session 1.
mars 04 08:51:41 Linux systemd[924]: Stopped D-Bus User Message Bus.
mars 04 08:51:41 Linux systemd[924]: dbus.service: Consumed 4.262s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopped flatpak document portal service.
mars 04 08:51:41 Linux systemd[924]: Stopped sandboxed app permission store.
mars 04 08:51:41 Linux systemd[924]: Stopped Portal service.
mars 04 08:51:41 Linux systemd[924]: Stopped Portal service (GNOME implementation).
mars 04 08:51:41 Linux systemd[924]: Stopped Evolution source registry.
mars 04 08:51:41 Linux systemd[1]: Stopping Firmware update daemon...
mars 04 08:51:41 Linux systemd[1]: Starting Show Plymouth Power Off Screen...
mars 04 08:51:41 Linux systemd[1]: cups-browsed.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[924]: Stopped User preferences database.
mars 04 08:51:41 Linux systemd[924]: Stopped Virtual filesystem metadata service.
mars 04 08:51:41 Linux systemd[924]: Stopped Evolution calendar service.
mars 04 08:51:41 Linux systemd[1]: Stopped Make remote CUPS printers available locally.
mars 04 08:51:41 Linux systemd[924]: Stopped Virtual filesystem service - disk device monitor.
mars 04 08:51:41 Linux systemd[924]: Stopped Virtual filesystem service - digital camera monitor.
mars 04 08:51:41 Linux systemd[924]: Stopped Evolution address book service.
mars 04 08:51:41 Linux systemd[924]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
mars 04 08:51:41 Linux systemd[924]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
mars 04 08:51:41 Linux systemd[924]: Stopped Virtual filesystem service - Apple File Conduit monitor.
mars 04 08:51:41 Linux systemd[924]: Stopped Portal service (GTK/GNOME implementation).
mars 04 08:51:41 Linux systemd[924]: Stopped Tracker file system data miner.
mars 04 08:51:41 Linux systemd[924]: tracker-miner-fs-3.service: Consumed 1.052s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopped snap.snap-store.ubuntu-software.57cbd3cf-6ff1-4852-8280-08ee62f156b3.scope.
mars 04 08:51:41 Linux systemd[924]: snap.snap-store.ubuntu-software.57cbd3cf-6ff1-4852-8280-08ee62f156b3.scope: Consumed 9.026s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopped Application launched by gnome-session-binary.
mars 04 08:51:41 Linux systemd[924]: Stopped Application launched by gnome-session-binary.
mars 04 08:51:41 Linux systemd[924]: app-gnome-update\x2dnotifier-1979.scope: Consumed 5.251s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopped Application launched by gnome-session-binary.
mars 04 08:51:41 Linux systemd[924]: Stopped Application launched by gnome-session-binary.
mars 04 08:51:41 Linux systemd[924]: Removed slice User Background Tasks Slice.
mars 04 08:51:41 Linux systemd[924]: background.slice: Consumed 1.279s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopping PipeWire Multimedia Service...
mars 04 08:51:41 Linux systemd[1]: Received SIGRTMIN+20 from PID 4242 (plymouthd).
mars 04 08:51:41 Linux systemd[1]: Stopped target Network is Online.
mars 04 08:51:41 Linux systemd[924]: Stopped PipeWire Multimedia Service.
mars 04 08:51:41 Linux gnome-shell[3166]: (EE) failed to read Wayland events: Broken pipe
mars 04 08:51:41 Linux pulseaudio[933]: Error opening PCM device front:0: Aucun fichier ou dossier de ce type
mars 04 08:51:41 Linux pulseaudio[933]: Error opening PCM device front:0: Aucun fichier ou dossier de ce type
mars 04 08:51:41 Linux systemd[1]: NetworkManager-wait-online.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Network Manager Wait Online.
mars 04 08:51:41 Linux systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
mars 04 08:51:41 Linux avahi-daemon[640]: Got SIGTERM, quitting.
mars 04 08:51:41 Linux avahi-daemon[640]: Leaving mDNS multicast group on interface wlp4s0.IPv6 with address fe80::b146:8daa:23da:adf5.
mars 04 08:51:41 Linux avahi-daemon[640]: Leaving mDNS multicast group on interface wlp4s0.IPv4 with address 192.168.1.27.
mars 04 08:51:41 Linux systemd[1]: Stopping CUPS Scheduler...
mars 04 08:51:41 Linux avahi-daemon[640]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
mars 04 08:51:41 Linux avahi-daemon[640]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
mars 04 08:51:41 Linux avahi-daemon[640]: avahi-daemon 0.8 exiting.
mars 04 08:51:41 Linux systemd[924]: Stopped Sound Service.
mars 04 08:51:41 Linux systemd[1]: avahi-daemon.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
mars 04 08:51:41 Linux systemd[1]: systemd-logind.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped User Login Management.
mars 04 08:51:41 Linux systemd[1]: cups.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped CUPS Scheduler.
mars 04 08:51:41 Linux systemd[1]: fwupd.service: Deactivated successfully.
mars 04 08:51:41 Linux systemd[1]: Stopped Firmware update daemon.
mars 04 08:51:41 Linux systemd[1]: fwupd.service: Consumed 1.209s CPU time.
mars 04 08:51:41 Linux systemd[924]: Stopped GNOME keyboard configuration service.
mars 04 08:51:41 Linux systemd[924]: Stopped GNOME color management service.
mars 04 08:51:41 Linux systemd[924]: Stopped GNOME power management service.
mars 04 08:51:41 Linux systemd[924]: Stopped GNOME keyboard shortcuts service.
mars 04 08:51:41 Linux systemd[924]: Stopped GNOME Wacom tablet support service.
mars 04 08:51:41 Linux systemd[924]: Stopped target GNOME Session is initialized.
mars 04 08:51:41 Linux systemd[924]: Stopped target GNOME Shell.
mars 04 08:51:41 Linux systemd[924]: Stopping GNOME Shell on Wayland...
mars 04 08:51:41 Linux systemd[1]: Started Show Plymouth Power Off Screen.
mars 04 08:51:41 Linux systemd[1]: Condition check resulted in Tell Plymouth To Jump To initramfs being skipped.
mars 04 08:51:42 Linux systemd[924]: Stopped GNOME Shell on Wayland.
mars 04 08:51:42 Linux systemd[924]: org.gnome.Shell@wayland.service: Consumed 3min 9.285s CPU time.
mars 04 08:51:42 Linux systemd[924]: Removed slice User Core Session Slice.
mars 04 08:51:42 Linux systemd[924]: session.slice: Consumed 3min 21.469s CPU time.
mars 04 08:51:42 Linux systemd[924]: Stopped target GNOME Session Manager is ready.
mars 04 08:51:42 Linux systemd[924]: Stopped target Tasks to be run before GNOME Session starts.
mars 04 08:51:42 Linux systemd[924]: Stopped target Session services which should run early before the graphical session is brought up.
mars 04 08:51:42 Linux systemd[924]: Reached target Shutdown running GNOME Session.
mars 04 08:51:42 Linux systemd[924]: Stopping Start gnome-keyring as SSH agent...
mars 04 08:51:42 Linux systemd[924]: Starting Restart DBus after GNOME Session shutdown...
mars 04 08:51:42 Linux systemd[924]: Stopped target Shutdown running GNOME Session.
mars 04 08:51:42 Linux sh[4266]: dbus-update-activation-environment: error: unable to connect to D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
mars 04 08:51:42 Linux systemd[924]: gnome-keyring-ssh.service: Control process exited, code=exited, status=71/OSERR
mars 04 08:51:42 Linux systemd[924]: gnome-keyring-ssh.service: Failed with result 'exit-code'.
mars 04 08:51:42 Linux systemd[924]: Stopped Start gnome-keyring as SSH agent.
mars 04 08:51:42 Linux systemd[924]: Stopped target Basic System.
mars 04 08:51:42 Linux systemd[924]: Stopped target Paths.
mars 04 08:51:42 Linux systemd[924]: Stopped Pending report trigger for Ubuntu Report.
mars 04 08:51:42 Linux systemd[924]: Stopped target Sockets.
mars 04 08:51:42 Linux systemd[924]: Stopped target Timers.
mars 04 08:51:42 Linux gnome-session-c[4265]: Couldn't connect to session bus: Erreur lors de la réception des données : Connexion ré-initialisée par le correspondant
mars 04 08:51:42 Linux systemd[924]: Closed D-Bus User Message Bus Socket.
mars 04 08:51:42 Linux systemd[924]: Closed GnuPG network certificate management daemon.
mars 04 08:51:42 Linux systemd[924]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
mars 04 08:51:42 Linux systemd[924]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
mars 04 08:51:42 Linux systemd[924]: Closed GnuPG cryptographic agent (ssh-agent emulation).
mars 04 08:51:42 Linux systemd[924]: Closed GnuPG cryptographic agent and passphrase cache.
mars 04 08:51:42 Linux systemd[924]: Closed PipeWire Multimedia System Socket.
mars 04 08:51:42 Linux systemd[924]: Closed debconf communication socket.
mars 04 08:51:42 Linux systemd[924]: Closed Sound System.
mars 04 08:51:42 Linux systemd[924]: Closed REST API socket for snapd user session agent.
mars 04 08:51:42 Linux systemd[924]: Removed slice User Application Slice.
mars 04 08:51:42 Linux systemd[924]: app.slice: Consumed 6min 58.456s CPU time.
mars 04 08:51:42 Linux systemd[924]: Reached target Shutdown.
mars 04 08:51:42 Linux systemd[924]: Finished Exit the Session.
mars 04 08:51:42 Linux systemd[924]: Reached target Exit the Session.
mars 04 08:51:42 Linux systemd[1]: user@1000.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped User Manager for UID 1000.
mars 04 08:51:42 Linux systemd[1]: user@1000.service: Consumed 10min 22.533s CPU time.
mars 04 08:51:42 Linux systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Killer...
mars 04 08:51:42 Linux systemd[1]: Stopping User Runtime Directory /run/user/1000...
mars 04 08:51:42 Linux systemd[1]: systemd-oomd.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
mars 04 08:51:42 Linux systemd[1]: systemd-oomd.service: Consumed 5.139s CPU time.
mars 04 08:51:42 Linux systemd[1]: run-user-1000.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted /run/user/1000.
mars 04 08:51:42 Linux systemd[1]: user-runtime-dir@1000.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped User Runtime Directory /run/user/1000.
mars 04 08:51:42 Linux systemd[1]: Removed slice User Slice of UID 1000.
mars 04 08:51:42 Linux systemd[1]: user-1000.slice: Consumed 10min 22.934s CPU time.
mars 04 08:51:42 Linux systemd[1]: Stopping Permit User Sessions...
mars 04 08:51:42 Linux systemd[1]: systemd-user-sessions.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Permit User Sessions.
mars 04 08:51:42 Linux systemd[1]: Stopped target Network.
mars 04 08:51:42 Linux systemd[1]: Stopped target User and Group Name Lookups.
mars 04 08:51:42 Linux systemd[1]: Stopped target Remote File Systems.
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.3614] caught SIGTERM, shutting down normally.
mars 04 08:51:42 Linux systemd[1]: Stopping Network Manager...
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.3630] device (wlp4s0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed')
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.3635] manager: NetworkManager state is now DISCONNECTING
mars 04 08:51:42 Linux systemd[1]: Stopping Network Name Resolution...
mars 04 08:51:42 Linux dbus-daemon[644]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=645 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
mars 04 08:51:42 Linux systemd[1]: Stopping WPA supplicant...
mars 04 08:51:42 Linux systemd[1]: Requested transaction contradicts existing jobs: Transaction for NetworkManager-dispatcher.service/start is destructive (local-fs.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:42 Linux dbus-daemon[644]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Transaction for NetworkManager-dispatcher.service/start is destructive (local-fs.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:42 Linux kernel: wlp4s0: deauthenticating from 08:87:c6:7e:96:e0 by local choice (Reason: 3=DEAUTH_LEAVING)
mars 04 08:51:42 Linux NetworkManager[645]: <warn>  [1677916302.3727] dispatcher: (8) failed: Transaction for NetworkManager-dispatcher.service/start is destructive (local-fs.target has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.3731] device (wlp4s0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed')
mars 04 08:51:42 Linux dbus-daemon[644]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.4' (uid=0 pid=645 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
mars 04 08:51:42 Linux systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-resolved.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
mars 04 08:51:42 Linux dbus-daemon[644]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Transaction for systemd-resolved.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.3888] dhcp4 (wlp4s0): canceled DHCP transaction
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.3889] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.3889] dhcp4 (wlp4s0): state changed no lease
mars 04 08:51:42 Linux systemd[1]: systemd-resolved.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Network Name Resolution.
mars 04 08:51:42 Linux wpa_supplicant[691]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=08:87:c6:7e:96:e0 reason=3 locally_generated=1
mars 04 08:51:42 Linux wpa_supplicant[691]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
mars 04 08:51:42 Linux wpa_supplicant[691]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
mars 04 08:51:42 Linux wpa_supplicant[691]: nl80211: deinit ifname=wlp4s0 disabled_11b_rates=0
mars 04 08:51:42 Linux wpa_supplicant[691]: wlp4s0: CTRL-EVENT-TERMINATING
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.4660] manager: NetworkManager state is now DISCONNECTED
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.4686] device (p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
mars 04 08:51:42 Linux systemd[1]: wpa_supplicant.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped WPA supplicant.
mars 04 08:51:42 Linux dbus-daemon[644]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=645 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
mars 04 08:51:42 Linux systemd[1]: Requested transaction contradicts existing jobs: Transaction for NetworkManager-dispatcher.service/start is destructive (systemd-sysusers.service has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:42 Linux dbus-daemon[644]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Transaction for NetworkManager-dispatcher.service/start is destructive (systemd-sysusers.service has 'stop' job queued, but 'start' is included in transaction).
mars 04 08:51:42 Linux NetworkManager[645]: <info>  [1677916302.4905] exiting (success)
mars 04 08:51:42 Linux systemd[1]: NetworkManager.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Network Manager.
mars 04 08:51:42 Linux systemd[1]: NetworkManager.service: Consumed 1.030s CPU time.
mars 04 08:51:42 Linux systemd[1]: Stopped target Basic System.
mars 04 08:51:42 Linux systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
mars 04 08:51:42 Linux systemd[1]: Stopped target Preparation for Network.
mars 04 08:51:42 Linux systemd[1]: Stopped target Path Units.
mars 04 08:51:42 Linux systemd[1]: acpid.path: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped ACPI Events Check.
mars 04 08:51:42 Linux systemd[1]: cups.path: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped CUPS Scheduler.
mars 04 08:51:42 Linux systemd[1]: whoopsie.path: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Start whoopsie on modification of the /var/crash directory.
mars 04 08:51:42 Linux systemd[1]: Stopped target Slice Units.
mars 04 08:51:42 Linux systemd[1]: Removed slice User and Session Slice.
mars 04 08:51:42 Linux systemd[1]: user.slice: Consumed 10min 22.934s CPU time.
mars 04 08:51:42 Linux systemd[1]: Stopped target Socket Units.
mars 04 08:51:42 Linux systemd[1]: acpid.socket: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Closed ACPID Listen Socket.
mars 04 08:51:42 Linux systemd[1]: avahi-daemon.socket: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
mars 04 08:51:42 Linux systemd[1]: cups.socket: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Closed CUPS Scheduler.
mars 04 08:51:42 Linux systemd[1]: snapd.socket: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Closed Socket activation for snappy daemon.
mars 04 08:51:42 Linux systemd[1]: syslog.socket: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Closed Syslog Socket.
mars 04 08:51:42 Linux systemd[1]: uuidd.socket: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Closed UUID daemon activation socket.
mars 04 08:51:42 Linux systemd[1]: Stopped target System Initialization.
mars 04 08:51:42 Linux systemd[1]: proc-sys-fs-binfmt_misc.automount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unset automount Arbitrary Executable File Formats File System Automount Point.
mars 04 08:51:42 Linux systemd[1]: Stopped target Local Encrypted Volumes.
mars 04 08:51:42 Linux systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
mars 04 08:51:42 Linux systemd[1]: Stopped target Local Verity Protected Volumes.
mars 04 08:51:42 Linux systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:acpi_video0...
mars 04 08:51:42 Linux systemd[1]: systemd-sysctl.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Apply Kernel Variables.
mars 04 08:51:42 Linux systemd[1]: systemd-modules-load.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Load Kernel Modules.
mars 04 08:51:42 Linux systemd[1]: Stopping Network Time Synchronization...
mars 04 08:51:42 Linux systemd[1]: Stopping Record System Boot/Shutdown in UTMP...
mars 04 08:51:42 Linux systemd[1]: proc-sys-fs-binfmt_misc.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: systemd-timesyncd.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Network Time Synchronization.
mars 04 08:51:42 Linux systemd[1]: systemd-backlight@backlight:acpi_video0.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:acpi_video0.
mars 04 08:51:42 Linux systemd[1]: Removed slice Slice /system/systemd-backlight.
mars 04 08:51:42 Linux systemd[1]: systemd-update-utmp.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Record System Boot/Shutdown in UTMP.
mars 04 08:51:42 Linux systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Create Volatile Files and Directories.
mars 04 08:51:42 Linux systemd[1]: Stopped target Local File Systems.
mars 04 08:51:42 Linux systemd[1]: Stopped target Mounted snaps.
mars 04 08:51:42 Linux systemd[1]: Unmounting /boot/efi...
mars 04 08:51:42 Linux systemd[1]: Unmounting /run/credentials/systemd-sysusers.service...
mars 04 08:51:42 Linux systemd[1]: Unmounting /run/snapd/ns/firefox.mnt...
mars 04 08:51:42 Linux systemd[1]: Unmounting /run/snapd/ns/snap-store.mnt...
mars 04 08:51:42 Linux systemd[1]: Unmounting /run/snapd/ns/snapd-desktop-integration.mnt...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for bare, revision 5...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for core20, revision 1587...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for core20, revision 1822...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for firefox, revision 1635...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for firefox, revision 2391...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for gnome-3-38-2004, revision 112...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for gnome-3-38-2004, revision 119...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for gtk-common-themes, revision 1535...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for snap-store, revision 582...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for snapd, revision 18357...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for snapd-desktop-integration, revision 14...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for snapd-desktop-integration, revision 49...
mars 04 08:51:42 Linux systemd[1]: Unmounting Mount unit for firefox, revision 2391 via mount-control...
mars 04 08:51:42 Linux systemd[1]: boot-efi.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted /boot/efi.
mars 04 08:51:42 Linux systemd[1]: run-credentials-systemd\x2dsysusers.service.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted /run/credentials/systemd-sysusers.service.
mars 04 08:51:42 Linux systemd[1]: run-snapd-ns-firefox.mnt.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted /run/snapd/ns/firefox.mnt.
mars 04 08:51:42 Linux systemd[1]: run-snapd-ns-snap\x2dstore.mnt.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted /run/snapd/ns/snap-store.mnt.
mars 04 08:51:42 Linux systemd[1]: run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted /run/snapd/ns/snapd-desktop-integration.mnt.
mars 04 08:51:42 Linux systemd[1]: snap-bare-5.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for bare, revision 5.
mars 04 08:51:42 Linux systemd[1]: snap-core20-1587.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for core20, revision 1587.
mars 04 08:51:42 Linux systemd[1]: snap-core20-1822.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for core20, revision 1822.
mars 04 08:51:42 Linux systemd[1]: snap-firefox-1635.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for firefox, revision 1635.
mars 04 08:51:42 Linux systemd[1]: snap-firefox-2391.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for firefox, revision 2391.
mars 04 08:51:42 Linux systemd[1]: snap-gnome\x2d3\x2d38\x2d2004-112.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for gnome-3-38-2004, revision 112.
mars 04 08:51:42 Linux systemd[1]: snap-gnome\x2d3\x2d38\x2d2004-119.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for gnome-3-38-2004, revision 119.
mars 04 08:51:42 Linux systemd[1]: snap-gtk\x2dcommon\x2dthemes-1535.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for gtk-common-themes, revision 1535.
mars 04 08:51:42 Linux systemd[1]: snap-snap\x2dstore-582.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for snap-store, revision 582.
mars 04 08:51:42 Linux systemd[1]: snap-snapd-18357.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for snapd, revision 18357.
mars 04 08:51:42 Linux systemd[1]: snap-snapd\x2ddesktop\x2dintegration-14.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for snapd-desktop-integration, revision 14.
mars 04 08:51:42 Linux systemd[1]: snap-snapd\x2ddesktop\x2dintegration-49.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for snapd-desktop-integration, revision 49.
mars 04 08:51:42 Linux systemd[1]: var-snap-firefox-common-host\x2dhunspell.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted Mount unit for firefox, revision 2391 via mount-control.
mars 04 08:51:42 Linux systemd[1]: Stopped target Mounting snaps.
mars 04 08:51:42 Linux systemd[1]: Unmounting /run/snapd/ns...
mars 04 08:51:42 Linux systemd[1]: systemd-fsck@dev-disk-by\x2duuid-DF98\x2dDBC0.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped File System Check on /dev/disk/by-uuid/DF98-DBC0.
mars 04 08:51:42 Linux systemd[1]: Removed slice Slice /system/systemd-fsck.
mars 04 08:51:42 Linux systemd[1]: run-snapd-ns.mount: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Unmounted /run/snapd/ns.
mars 04 08:51:42 Linux systemd[1]: Stopped target Preparation for Local File Systems.
mars 04 08:51:42 Linux systemd[1]: Stopped target Swaps.
mars 04 08:51:42 Linux systemd[1]: Deactivating swap /swapfile...
mars 04 08:51:42 Linux systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Create Static Device Nodes in /dev.
mars 04 08:51:42 Linux systemd[1]: systemd-sysusers.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Create System Users.
mars 04 08:51:42 Linux systemd[1]: swapfile.swap: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Deactivated swap /swapfile.
mars 04 08:51:42 Linux systemd[1]: Reached target Unmount All Filesystems.
mars 04 08:51:42 Linux systemd[1]: systemd-remount-fs.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Stopped Remount Root and Kernel File Systems.
mars 04 08:51:42 Linux systemd[1]: Reached target System Shutdown.
mars 04 08:51:42 Linux systemd[1]: Reached target Late Shutdown Services.
mars 04 08:51:42 Linux systemd[1]: systemd-poweroff.service: Deactivated successfully.
mars 04 08:51:42 Linux systemd[1]: Finished System Power Off.
mars 04 08:51:42 Linux systemd[1]: Reached target System Power Off.
mars 04 08:51:42 Linux systemd[1]: Shutting down.
mars 04 08:51:42 Linux systemd-shutdown[1]: Syncing filesystems and block devices.
mars 04 08:51:42 Linux systemd-shutdown[1]: Sending SIGTERM to remaining processes...
mars 04 08:51:42 Linux systemd-journald[250]: Journal stopped

Hors ligne

#18 Le 04/03/2023, à 10:19

winguru

Re : arret PC ne fonctionne pas

wouaou c'est Champolion ton nom de famille ?

Hors ligne

#19 Le 04/03/2023, à 10:23

xubu1957

Re : arret PC ne fonctionne pas

@geole

Salut !

Vu le fil Nomodeset et Hivernation

Serait-il judicieux de passer sur le pilote nvidia-340, en ajoutant le ppa ?

Pour info :

Le 28/08/2021, philippélyvia a écrit :

https://launchpad.net/~kelebek333/+arch … dia-legacy
je pose ça là pour ceux qui voudrait qd meme le noyau de 20.04 et les vieux drivers

bonne journée

> [Résolu] Impossible d'installer le driver nvidia-340 sur Xubuntu 20.04 et versions suivantes.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

En ligne

#20 Le 04/03/2023, à 10:49

geole

Re : arret PC ne fonctionne pas

Les quatre dernières lignes montrent que le logiciel s'est très bien terminé.
Il ne lui restait plus qu'à lancer la commande d'arrêt électrique. Ce qu'il a fait mais qui n'a pas été comprise. Donc tu peux couper le courant électrique sans scrupule.

Bonjour xubu1957.
Pour les cartes graphiques, je sais juste les faire lister mais  je suis incapable de dire quel pilote est préférable. Souvent ils sont accompagnés d'un commentaire. Je ne sais pas s'il est sytématiquement judicieux.

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity

Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#21 Le 04/03/2023, à 11:03

xubu1957

Re : arret PC ne fonctionne pas

@winguru

Fournis les noyaux présents :

echo; dpkg -l | awk '!/^rc/ && / linux-(c|g|h|i|lo|m|si|t)/{print $1,$2,$3,$4 | "sort -k3V | column -t"}' ; echo -e "\nNoyau courant : $(uname -mr)"

Vu :

mars 04 08:51:41 Linux gnome-shell[3166]: (EE) failed to read Wayland events: Broken pipe

@geole


C'est comme moi, je sais donner des commandes informatives, mais pour les correctives !!! roll

Et la Doc veille_et_hibernation n'est pas simple.

Tester avec xorg en changeant de session, avec la roue crantée ?

Dernière modification par xubu1957 (Le 04/03/2023, à 11:05)

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

En ligne

#22 Le 04/03/2023, à 16:58

winguru

Re : arret PC ne fonctionne pas

cho; dpkg -l | awk '!/^rc/ && / linux-(c|g|h|i|lo|m|si|t)/{print $1,$2,$3,$4 | "sort -k3V | column -t"}' ; echo -e "\nNoyau courant : $(uname -mr)"

ii  linux-hwe-5.19-headers-5.19.0-32       5.19.0-32.33~22.04.1   all
ii  linux-headers-5.19.0-32-generic        5.19.0-32.33~22.04.1   amd64
ii  linux-image-5.19.0-32-generic          5.19.0-32.33~22.04.1   amd64
ii  linux-modules-5.19.0-32-generic        5.19.0-32.33~22.04.1   amd64
ii  linux-modules-extra-5.19.0-32-generic  5.19.0-32.33~22.04.1   amd64
ii  linux-hwe-5.19-headers-5.19.0-35       5.19.0-35.36~22.04.1   all
ii  linux-headers-5.19.0-35-generic        5.19.0-35.36~22.04.1   amd64
ii  linux-image-5.19.0-35-generic          5.19.0-35.36~22.04.1   amd64
ii  linux-modules-5.19.0-35-generic        5.19.0-35.36~22.04.1   amd64
ii  linux-modules-extra-5.19.0-35-generic  5.19.0-35.36~22.04.1   amd64
ii  linux-generic-hwe-22.04                5.19.0.35.36~22.04.10  amd64
ii  linux-headers-generic-hwe-22.04        5.19.0.35.36~22.04.10  amd64
ii  linux-image-generic-hwe-22.04          5.19.0.35.36~22.04.10  amd64

Noyau courant : 5.19.0-35-generic x86_64

Hors ligne

Pages : 1