Contenu | Rechercher | Menus

Annonce

DVD, clés USB et t-shirts Ubuntu-fr disponibles sur la boutique En Vente Libre

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.

#1 Le 09/09/2020, à 01:26

AMOR19

Ubuntu 20.04 lts ne s'éteint pas

Bonjour à tous et à toutes.
Mon problème est que j'ai installé ubuntu 20.04 lts sur mon pc acer et depuis il ne s'éteint plus jamais qu'en gardant le bouton on/off enfoncé manuellement. J'ai un peu lu sur ce forum des problèmes de ce genre mais il me semble que les corriger diffère d'un cas à l'autre, surtout que je suis débutant avec ubuntu.
Votre aide me serait très précieuse.
Merci à l'avance

Hors ligne

#2 Le 09/09/2020, à 12:26

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

Pas la moindre idée les amis ? J'attends toujours votre aide svp

Hors ligne

#3 Le 09/09/2020, à 12:29

xubu1957

Re : Ubuntu 20.04 lts ne s'éteint pas

Bonjour,

Montre, en te servant du Retour utilisable de commande :

echo; lsb_release -d ; echo -e "\nNoyau courant : $(uname -mr)"; echo $XDG_CURRENT_DESKTOP ; echo; ls -lt /usr/share/xsessions | awk '{print $6,$7,$8,$9}'

et :

dpkg -l | grep -v ^ii
cqfd93 a écrit :

Astuce pour copier / coller sans erreur :

  • triple clic gauche pour sélectionner et copier une ligne entière

  • clic molette pour coller dans le terminal


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.

Xubuntu 20.04 LTS - Lenovo T410 -18.04.1 LTS Toshiba Satellite A300  Membre de Linux-Azur

En ligne

#4 Le 09/09/2020, à 12:40

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

Merci beaucoup pour la réponse. Sinon, voilà ce que retournent les deux commandes

amor@amor:~$ echo; lsb_release -d ; echo -e "\nNoyau courant : $(uname -mr)"; echo $XDG_CURRENT_DESKTOP ; echo; ls -lt /usr/share/xsessions | awk '{print $6,$7,$8,$9}'

Description:	Ubuntu 20.04.1 LTS

Noyau courant : 5.4.0-47-generic x86_64
ubuntu:GNOME

   
مارس 26 13:22 ubuntu.desktop
amor@amor:~$ 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.4.0-26-generic                  5.4.0-26.30                           amd64        Signed kernel image generic
rc  linux-image-5.4.0-33-generic                  5.4.0-33.37                           amd64        Signed kernel image generic
rc  linux-image-5.4.0-37-generic                  5.4.0-37.41                           amd64        Signed kernel image generic
rc  linux-modules-5.4.0-26-generic                5.4.0-26.30                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
rc  linux-modules-5.4.0-33-generic                5.4.0-33.37                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
rc  linux-modules-5.4.0-37-generic                5.4.0-37.41                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.4.0-26-generic          5.4.0-26.30                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ri  linux-modules-extra-5.4.0-29-generic          5.4.0-29.33                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.4.0-33-generic          5.4.0-33.37                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.4.0-37-generic          5.4.0-37.41                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
amor@amor:~$ 

Hors ligne

#5 Le 09/09/2020, à 12:47

xubu1957

Re : Ubuntu 20.04 lts ne s'éteint pas

Fournis :

sudo apt update

- et les noyaux présents :

echo; dpkg -l | grep -Ei "linux-(g|h|i|lo|mo|si|t)" | grep -v ^rc | sort -k3 | awk '{print $1,$2,$3,$4}' | column -s" " -t ; echo ; uname -mr

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.

Xubuntu 20.04 LTS - Lenovo T410 -18.04.1 LTS Toshiba Satellite A300  Membre de Linux-Azur

En ligne

#6 Le 09/09/2020, à 12:50

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

Alors Xubu, pour la première commande ça donne ça :

amor@amor:~$ sudo apt update
[sudo] Mot de passe de amor : 
Err :1 http://tn.archive.ubuntu.com/ubuntu focal InRelease
  Erreur temporaire de résolution de « tn.archive.ubuntu.com »
Err :2 http://dl.google.com/linux/chrome/deb stable InRelease
  Erreur temporaire de résolution de « dl.google.com »
Err :3 http://security.ubuntu.com/ubuntu focal-security InRelease
  Erreur temporaire de résolution de « security.ubuntu.com »
Err :4 http://tn.archive.ubuntu.com/ubuntu focal-updates InRelease
  Erreur temporaire de résolution de « tn.archive.ubuntu.com »
Err :5 http://tn.archive.ubuntu.com/ubuntu focal-backports InRelease
  Erreur temporaire de résolution de « tn.archive.ubuntu.com »
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
10 paquets peuvent être mis à jour. Exécutez « apt list --upgradable » pour les voir.
W: Impossible de récupérer http://tn.archive.ubuntu.com/ubuntu/dists/focal/InRelease  Erreur temporaire de résolution de « tn.archive.ubuntu.com »
W: Impossible de récupérer http://tn.archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease  Erreur temporaire de résolution de « tn.archive.ubuntu.com »
W: Impossible de récupérer http://tn.archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease  Erreur temporaire de résolution de « tn.archive.ubuntu.com »
W: Impossible de récupérer http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease  Erreur temporaire de résolution de « security.ubuntu.com »
W: Impossible de récupérer http://dl.google.com/linux/chrome/deb/dists/stable/InRelease  Erreur temporaire de résolution de « dl.google.com »
W: Le téléchargement de quelques fichiers d'index a échoué, ils ont été ignorés, ou les anciens ont été utilisés à la place.

Tandis que pour a seconde ça retourne ça :

amor@amor:~$ echo; dpkg -l | grep -Ei "linux-(g|h|i|lo|mo|si|t)" | grep -v ^rc | sort -k3 | awk '{print $1,$2,$3,$4}' | column -s" " -t ; echo ; uname -mr

ii  binutils-x86-64-linux-gnu             2.34-6ubuntu1  amd64
ii  linux-headers-5.4.0-29                5.4.0-29.33    all
ii  linux-modules-5.4.0-29-generic        5.4.0-29.33    amd64
ri  linux-modules-extra-5.4.0-29-generic  5.4.0-29.33    amd64
ii  linux-headers-5.4.0-29-generic        5.4.0-29.33    amd64
ii  linux-image-5.4.0-29-generic          5.4.0-29.33    amd64
ii  linux-headers-5.4.0-42                5.4.0-42.46    all
ii  linux-modules-5.4.0-42-generic        5.4.0-42.46    amd64
ii  linux-modules-extra-5.4.0-42-generic  5.4.0-42.46    amd64
ii  linux-headers-5.4.0-42-generic        5.4.0-42.46    amd64
ii  linux-image-5.4.0-42-generic          5.4.0-42.46    amd64
ii  linux-headers-5.4.0-45                5.4.0-45.49    all
ii  linux-modules-5.4.0-45-generic        5.4.0-45.49    amd64
ii  linux-modules-extra-5.4.0-45-generic  5.4.0-45.49    amd64
ii  linux-headers-5.4.0-45-generic        5.4.0-45.49    amd64
ii  linux-image-5.4.0-45-generic          5.4.0-45.49    amd64
ii  linux-generic-hwe-20.04               5.4.0.47.50    amd64
ii  linux-headers-generic-hwe-20.04       5.4.0.47.50    amd64
ii  linux-image-generic-hwe-20.04         5.4.0.47.50    amd64
ii  linux-headers-5.4.0-47                5.4.0-47.51    all
ii  linux-modules-5.4.0-47-generic        5.4.0-47.51    amd64
ii  linux-modules-extra-5.4.0-47-generic  5.4.0-47.51    amd64
ii  linux-headers-5.4.0-47-generic        5.4.0-47.51    amd64
ii  linux-image-5.4.0-47-generic          5.4.0-47.51    amd64

5.4.0-47-generic x86_64
amor@amor:~$ 

Hors ligne

#7 Le 09/09/2020, à 12:54

xubu1957

Re : Ubuntu 20.04 lts ne s'éteint pas

Les serveurs ne sont pas accessibles.

ri  linux-modules-extra-5.4.0-29-generic  5.4.0-29.33    amd64

Il y a une anomalie sur ce noyau ancien.

Je ne sais pas la gérer.


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.

Xubuntu 20.04 LTS - Lenovo T410 -18.04.1 LTS Toshiba Satellite A300  Membre de Linux-Azur

En ligne

#8 Le 09/09/2020, à 12:56

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

Je te remercie fort Xubu pour tes tentatives.

Hors ligne

#9 Le 09/09/2020, à 19:26

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

Le problème n'est toujours pas résolu et je n'arrive même pas à terminer convenablement l'installation des différentes mises à jour du moment qu'on demande de redémarrer l'ordinateur. C'est intriguant.

Hors ligne

#10 Le 09/09/2020, à 19:29

xubu1957

Re : Ubuntu 20.04 lts ne s'éteint pas

Tu ne peux  pas redémarrer avec les touches_magiques ?

Le 15/03/2018, moko138 a écrit :

(...)
Plutôt que l'extinction mécanique forcée, qui détériore les composants et qui laisse en vrac les systèmes de fichiers des partitions montées, il faut préférer  les touches_magiques.

(...)

Concrètement, pour redémarrer:
Alt+Sys  r e i s  (*)    u (*)    b

(*) attendre quelques secondes.


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.

Xubuntu 20.04 LTS - Lenovo T410 -18.04.1 LTS Toshiba Satellite A300  Membre de Linux-Azur

En ligne

#11 Le 09/09/2020, à 20:48

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

xubu1957 a écrit :

Concrètement, pour redémarrer:
Alt+Sys  r e i s  (*)    u (*)    b
(*) attendre quelques secondes.

Celà a fonctionné, sauf que, en tentant d'éteindre le pc (non pas de le redémarrer) avec Alt+Sys  r e i s  (*)    u (*)    o ça plante et rien ne se passe. Obligé encore de l'éteindre manuellement

Hors ligne

#12 Le 09/09/2020, à 20:52

xubu1957

Re : Ubuntu 20.04 lts ne s'éteint pas

Pour les miracles, je n'ai pas la recette !


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.

Xubuntu 20.04 LTS - Lenovo T410 -18.04.1 LTS Toshiba Satellite A300  Membre de Linux-Azur

En ligne

#13 Le 09/09/2020, à 22:22

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

Niko, dans cette discussion à propos d'un problème similaire, a écrit ceci :

NicoApi73 a écrit :

[...]
A partir de ta session, peux tu faire un boot-info : https://doc.ubuntu-fr.org/tutoriel/boot-info. Copie le lien URL dans ta réponse.
[...]

Dans mon cas, voilà le boot-info correspondant si jamais ça pourrait aider.
Je le met ici aussi :

  boot-info-4ppa125                                              [20200909_2213]

============================== Boot Info Summary ===============================

 => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    for (,msdos5)/boot/grub. It also embeds following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos biosdisk
    ---------------------------------------------------------------------------

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sda2: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info: 

sda5: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Ubuntu 20.04.1 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub 
                       /boot/grub/i386-pc/core.img


================================ 1 OS detected =================================

OS#1:   L'OS actuellement utilisé - Ubuntu 20.04.1 LTS CurrentSession on sda5

============================ Architecture/Host Info ============================

CPU architecture: 64-bit
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-5.4.0-47-generic root=UUID=9d51d28d-08d8-4af5-b56f-2d6b44c983d5 ro quiet splash vt.handoff=7


===================================== UEFI =====================================

This installed-session is not in EFI-mode.
EFI in dmesg.
[    0.010700] ACPI: UEFI 0x00000000787B8000 000236 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.010753] ACPI: UEFI 0x00000000787A5000 000042 (v01 ACRSYS ACRPRDCT 00000000 1025 00040000)
[    3.164326] fb0: EFI VGA frame buffer device
[   25.362070] fb0: switching to inteldrmfb from EFI VGA



============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

sda	: notGPT,	no-BIOSboot,	has---ESP, 	not-usb,	not-mmc, has-os,	2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

sda5	: is-os,	64, apt-get,	grub-pc ,	grub2,	grub-install,	grubenv-ok,	update-grub,	farbios
sda1	: no-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	not-far

Partitions info (2/3): _________________________________________________________

sda5	: isnotESP,	fstab-has-goodEFI,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot
sda1	: is---ESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot

Partitions info (3/3): _________________________________________________________

sda5	: not-sepboot,	with-boot,	fstab-without-boot,	not-sep-usr,	with--usr,	fstab-without-usr,	std-grub.d,	sda
sda1	: not-sepboot,	no-boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	std-grub.d,	sda

fdisk -l (filtered): ___________________________________________________________

Disk sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: 0x9cd56d0e
      Boot   Start       End   Sectors   Size Id Type
sda1  *       2048   1050623   1048576   512M  b W95 FAT32
sda2       1052670 976771071 975718402 465.3G  5 Extended
sda5       1052672 976771071 975718400 465.3G 83 Linux

parted -lm (filtered): _________________________________________________________

sda:500GB:scsi:512:4096:msdos:ATA WDC WD5000LPVX-2:;
1:1049kB:538MB:537MB:fat32::boot;
2:539MB:500GB:500GB:::;
5:539MB:500GB:500GB:ext4::;

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL PARTLABEL
sda                                                                                             
├─sda1 vfat     ACE3-1EAD                            9cd56d0e-01                                
├─sda2                                               9cd56d0e-02                                
└─sda5 ext4     9d51d28d-08d8-4af5-b56f-2d6b44c983d5 9cd56d0e-05                                

df (filtered): _________________________________________________________________

                   Avail Use% Mounted on
sda5              405.1G   6% /

Mount options: __________________________________________________________________

sda5              rw,relatime,errors=remount-ro

====================== sda5/boot/grub/grub.cfg (filtered) ======================

Ubuntu   9d51d28d-08d8-4af5-b56f-2d6b44c983d5
Ubuntu, avec Linux 5.4.0-47-generic   9d51d28d-08d8-4af5-b56f-2d6b44c983d5
Ubuntu, avec Linux 5.4.0-45-generic   9d51d28d-08d8-4af5-b56f-2d6b44c983d5
Ubuntu, avec Linux 5.4.0-29-generic   9d51d28d-08d8-4af5-b56f-2d6b44c983d5
### END /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_uefi-firmware ###

========================== sda5/etc/fstab (filtered) ===========================

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda5 during installation
UUID=9d51d28d-08d8-4af5-b56f-2d6b44c983d5 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=ACE3-1EAD  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

======================= sda5/etc/default/grub (filtered) =======================

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

==================== sda5: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
 200.714366913 = 215.515410432  boot/grub/grub.cfg                             1
 200.635070801 = 215.430266880  boot/grub/i386-pc/core.img                     1
  29.005008698 = 31.143890944   boot/vmlinuz                                   1
  72.809684753 = 78.178803712   boot/vmlinuz-5.4.0-29-generic                  1
  19.200321198 = 20.616187904   boot/vmlinuz-5.4.0-45-generic                  1
  29.005008698 = 31.143890944   boot/vmlinuz-5.4.0-47-generic                  1
  19.200321198 = 20.616187904   boot/vmlinuz.old                               1
  18.103511810 = 19.438497792   boot/initrd.img                                7
  21.848945618 = 23.460126720   boot/initrd.img-5.4.0-29-generic               1
  28.323684692 = 30.412324864   boot/initrd.img-5.4.0-45-generic               6
  18.103511810 = 19.438497792   boot/initrd.img-5.4.0-47-generic               7
  28.323684692 = 30.412324864   boot/initrd.img.old                            6

===================== sda5: ls -l /etc/grub.d/ (filtered) ======================

-rwxr-xr-x 1 root root 17622 أوت    17 15:04 10_linux
-rwxr-xr-x 1 root root 42359 أوت    17 15:04 10_linux_zfs
-rwxr-xr-x 1 root root 12894 أفريل  15 12:31 20_linux_xen
-rwxr-xr-x 1 root root 12059 أفريل  15 12:31 30_os-prober
-rwxr-xr-x 1 root root  1424 أفريل  15 12:31 30_uefi-firmware
-rwxr-xr-x 1 root root   214 أفريل  15 12:31 40_custom
-rwxr-xr-x 1 root root   216 أفريل  15 12:31 41_custom


Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi-amd64-signed of
sda5,
using the following options:        sda1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s  use-standard-efi-file    

Blockers in case of suggested repair: __________________________________________

 The current session is in BIOS-compatibility mode. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB) that is compatible with UEFI booting mode. For example, use a live-USB of Boot-Repair-Disk-64bit (www.sourceforge.net/p/boot-repair-cd), after making sure your BIOS is set up to boot USB in EFI mode. This will enable this feature.

Confirmation request before suggested repair: __________________________________

The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to EFI mode.
Alternatively, you may want to retry after deactivating the [Separate /usr partition:] option.
Are you sure you want to continue anyway?

Final advice in case of suggested repair: ______________________________________


Please do not forget to make your UEFI firmware boot on the L'OS actuellement utilisé - Ubuntu 20.04.1 LTS CurrentSession entry (sda1/efi/****/shim****.efi (**** will be updated in the final message) file) !
The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to UEFI mode.

Dernière modification par AMOR19 (Le 09/09/2020, à 22:25)

Hors ligne

#14 Le 10/09/2020, à 06:22

NicoApi73

Re : Ubuntu 20.04 lts ne s'éteint pas

Bonjour,

Peux tu donner le retour des commandes

dmesg -lerr
sudo lshw

Quelle est la référence exacte de ta machine?

Avant la 20.04, utilisais tu Ubuntu?

Dernière modification par NicoApi73 (Le 10/09/2020, à 06:34)

Hors ligne

#15 Le 10/09/2020, à 11:16

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

Merci Nico de venir à mon aide.

NicoApi73 a écrit :

Quelle est la référence exacte de ta machine?

C'est écrit sur le bas du pc : acer ES1-512 series

NicoApi73 a écrit :

Avant la 20.04, utilisais tu Ubuntu?

Oui, 18.04 lts y était installé.

Pour le retour des commandes, voilà ce que ça donne :

amor@amor:~$ dmesg -lerr
amor@amor:~$ sudo lshw
[sudo] Mot de passe de amor : 
amor                        
    description: Ordinateur Bloc-notes
    produit: Aspire ES1-512 (EA53_BM_083D_1.10)
    fabricant: Acer
    version: V1.10
    numéro de série: NXMRWEM00850902A916600
    bits: 64 bits
    fonctionnalités: smbios-2.7 dmi-2.7 smp vsyscall32
    configuration : chassis=notebook family=BayTrail sku=EA53_BM_083D_1.10 uuid=BB5D49A6-F87E-4A03-8EA2-6FD050606DF1
  *-core
       description: Carte mère
       produit: Aspire ES1-512
       fabricant: Acer
       identifiant matériel: 0
       version: V1.10
       numéro de série: NXMRWEM00850902A916600
       emplacement: Type2 - Board Chassis Location
     *-firmware
          description: BIOS
          fabricant: Insyde Corp.
          identifiant matériel: 0
          version: V1.10
          date: 12/15/2014
          taille: 64KiB
          capacité: 3MiB
          fonctionnalités: pci upgrade shadowing cdboot bootselect edd int9keyboard int14serial int17printer int10video acpi usb zipboot biosbootspecification netboot
     *-cpu
          description: CPU
          produit: Intel(R) Celeron(R) CPU  N2840  @ 2.16GHz
          fabricant: Intel Corp.
          identifiant matériel: 4
          information bus: cpu@0
          version: Intel(R) Celeron(R) CPU  N2840  @ 2.16GHz
          emplacement: CPU 1
          taille: 690MHz
          capacité: 2582MHz
          bits: 64 bits
          horloge: 83MHz
          fonctionnalités: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat md_clear cpufreq
          configuration : cores=2 enabledcores=2 threads=1
        *-cache:0
             description: L1 cache
             identifiant matériel: 8
             emplacement: Unknown
             taille: 32KiB
             capacité: 32KiB
             fonctionnalités: synchronous internal write-back instruction
             configuration : level=1
        *-cache:1
             description: L2 cache
             identifiant matériel: 9
             emplacement: Unknown
             taille: 1MiB
             capacité: 1MiB
             fonctionnalités: synchronous internal write-back unified
             configuration : level=2
     *-cache
          description: L1 cache
          identifiant matériel: 7
          emplacement: Unknown
          taille: 24KiB
          capacité: 24KiB
          fonctionnalités: synchronous internal write-back data
          configuration : level=1
     *-memory
          description: Mémoire Système
          identifiant matériel: f
          emplacement: Carte mère
          taille: 2GiB
        *-bank:0
             description: SODIMM DDR3 Synchrone 1333 MHz (0.8 ns)
             produit: ACR16D3LFS1KBG/2G
             fabricant: Kingston
             identifiant matériel: 0
             numéro de série: 23311811
             emplacement: DIMM0
             taille: 2GiB
             bits: 64 bits
             horloge: 1333MHz (0.8ns)
        *-bank:1
             description: SODIMMProject-Id-Version: @(#) $Id$Report-Msgid-Bugs-To: PO-Revision-Date: 2020-04-03 08:20+0000Last-Translator: Lyonel Vincent <Unknown>Language-Team: MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2020-07-09 17:42+0000X-Generator: Launchpad (build 4809fcb62f445aaa3ae919f7f6c3cc7d156ea57a) [vide]
             identifiant matériel: 1
             emplacement: DIMM1
     *-pci
          description: Host bridge
          produit: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register
          fabricant: Intel Corporation
          identifiant matériel: 100
          information bus: pci@0000:00:00.0
          version: 0e
          bits: 32 bits
          horloge: 33MHz
          configuration : driver=iosf_mbi_pci
          ressources : irq:0
        *-display
             description: VGA compatible controller
             produit: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
             fabricant: Intel Corporation
             identifiant matériel: 2
             information bus: pci@0000:00:02.0
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: pm msi vga_controller bus_master cap_list rom
             configuration : driver=i915 latency=0
             ressources : irq:94 mémoire:90000000-903fffff mémoire:80000000-8fffffff portE/S:2050(taille=8) mémoire:c0000-dffff
        *-sata
             description: SATA controller
             produit: Atom Processor E3800 Series SATA AHCI Controller
             fabricant: Intel Corporation
             identifiant matériel: 13
             information bus: pci@0000:00:13.0
             nom logique: scsi0
             nom logique: scsi1
             version: 0e
             bits: 32 bits
             horloge: 66MHz
             fonctionnalités: sata msi pm ahci_1.0 bus_master cap_list emulated
             configuration : driver=ahci latency=0
             ressources : irq:91 portE/S:2048(taille=8) portE/S:205c(taille=4) portE/S:2040(taille=8) portE/S:2058(taille=4) portE/S:2020(taille=32) mémoire:9091d000-9091d7ff
           *-disk
                description: ATA Disk
                produit: WDC WD5000LPVX-2
                fabricant: Western Digital
                identifiant matériel: 0
                information bus: scsi@0:0.0.0
                nom logique: /dev/sda
                version: 1A01
                numéro de série: WD-WX91AC4N3EVN
                taille: 465GiB (500GB)
                fonctionnalités: partitioned partitioned:dos
                configuration : ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=9cd56d0e
              *-volume:0
                   description: Windows FAT volume
                   fabricant: mkfs.fat
                   identifiant matériel: 1
                   information bus: scsi@0:0.0.0,1
                   nom logique: /dev/sda1
                   nom logique: /boot/efi
                   version: FAT32
                   numéro de série: ace3-1ead
                   taille: 510MiB
                   capacité: 512MiB
                   fonctionnalités: primary bootable fat initialized
                   configuration : FATs=2 filesystem=fat mount.fstype=vfat mount.options=rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro state=mounted
              *-volume:1
                   description: Extended partition
                   identifiant matériel: 2
                   information bus: scsi@0:0.0.0,2
                   nom logique: /dev/sda2
                   taille: 465GiB
                   capacité: 465GiB
                   fonctionnalités: primary extended partitioned partitioned:extended
                 *-logicalvolume
                      description: Volume EXT4
                      fabricant: Linux
                      identifiant matériel: 5
                      nom logique: /dev/sda5
                      nom logique: /
                      version: 1.0
                      numéro de série: 9d51d28d-08d8-4af5-b56f-2d6b44c983d5
                      taille: 465GiB
                      capacité: 465GiB
                      fonctionnalités: journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized
                      configuration : created=2020-05-05 02:01:02 filesystem=ext4 lastmountpoint=/ modified=2020-09-10 10:24:41 mount.fstype=ext4 mount.options=rw,relatime,errors=remount-ro mounted=2020-09-10 10:24:49 state=mounted
           *-cdrom
                description: DVD-RAM writer
                produit: DVD-RAM UJ8HC
                fabricant: MATSHITA
                identifiant matériel: 1
                information bus: scsi@1:0.0.0
                nom logique: /dev/cdrom
                nom logique: /dev/cdrw
                nom logique: /dev/dvd
                nom logique: /dev/dvdrw
                nom logique: /dev/sr0
                version: 1.00
                fonctionnalités: removable audio cd-r cd-rw dvd dvd-r dvd-ram
                configuration : ansiversion=5 status=nodisc
        *-usb:0
             description: USB controller
             produit: Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI
             fabricant: Intel Corporation
             identifiant matériel: 14
             information bus: pci@0000:00:14.0
             version: 0e
             bits: 64 bits
             horloge: 33MHz
             fonctionnalités: pm msi xhci bus_master cap_list
             configuration : driver=xhci_hcd latency=0
             ressources : irq:90 mémoire:90900000-9090ffff
           *-usbhost:0
                produit: xHCI Host Controller
                fabricant: Linux 5.4.0-47-generic xhci-hcd
                identifiant matériel: 0
                information bus: usb@2
                nom logique: usb2
                version: 5.04
                fonctionnalités: usb-2.00
                configuration : driver=hub slots=6 speed=480Mbit/s
              *-usb:0
                   description: Souris
                   produit: USB OPTICAL MOUSE
                   identifiant matériel: 1
                   information bus: usb@2:1
                   version: 1.00
                   fonctionnalités: usb-1.10
                   configuration : driver=usbhid maxpower=100mA speed=2Mbit/s
              *-usb:1
                   description: Concentrateur USB
                   produit: USB2.0 Hub
                   fabricant: Genesys Logic, Inc.
                   identifiant matériel: 3
                   information bus: usb@2:3
                   version: 85.37
                   fonctionnalités: usb-2.00
                   configuration : driver=hub maxpower=100mA slots=4 speed=480Mbit/s
                 *-usb:0
                      description: Interface sans fil Bluetooth
                      produit: Atheros AR3012 Bluetooth
                      fabricant: Lite-On Technology Corp.
                      identifiant matériel: 1
                      information bus: usb@2:3.1
                      version: 0.02
                      fonctionnalités: bluetooth usb-1.10
                      configuration : driver=btusb maxpower=100mA speed=12Mbit/s
                 *-usb:1
                      description: Périphérique USB générique
                      produit: USB2.0-CRW
                      fabricant: Generic
                      identifiant matériel: 4
                      information bus: usb@2:3.4
                      version: 39.60
                      numéro de série: 20100201396000000
                      fonctionnalités: usb-2.00
                      configuration : driver=rtsx_usb maxpower=500mA speed=480Mbit/s
              *-usb:2
                   description: Vidéo
                   produit: VGA Webcam
                   fabricant: NC2141102N5031D41DLM21
                   identifiant matériel: 4
                   information bus: usb@2:4
                   version: 3.21
                   numéro de série: 200901010001
                   fonctionnalités: usb-2.00
                   configuration : driver=uvcvideo maxpower=500mA speed=480Mbit/s
           *-usbhost:1
                produit: xHCI Host Controller
                fabricant: Linux 5.4.0-47-generic xhci-hcd
                identifiant matériel: 1
                information bus: usb@3
                nom logique: usb3
                version: 5.04
                fonctionnalités: usb-3.00
                configuration : driver=hub slots=1 speed=5000Mbit/s
        *-generic
             description: Encryption controller
             produit: Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine
             fabricant: Intel Corporation
             identifiant matériel: 1a
             information bus: pci@0000:00:1a.0
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: pm msi bus_master cap_list
             configuration : driver=mei_txe latency=0
             ressources : irq:93 mémoire:90800000-908fffff mémoire:90700000-907fffff
        *-multimedia
             description: Audio device
             produit: Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller
             fabricant: Intel Corporation
             identifiant matériel: 1b
             information bus: pci@0000:00:1b.0
             version: 0e
             bits: 64 bits
             horloge: 33MHz
             fonctionnalités: pm msi bus_master cap_list
             configuration : driver=snd_hda_intel latency=0
             ressources : irq:95 mémoire:90910000-90913fff
        *-pci:0
             description: PCI bridge
             produit: Atom Processor E3800 Series PCI Express Root Port 1
             fabricant: Intel Corporation
             identifiant matériel: 1c
             information bus: pci@0000:00:1c.0
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration : driver=pcieport
             ressources : irq:87 portE/S:3000(taille=4096)
        *-pci:1
             description: PCI bridge
             produit: Atom Processor E3800 Series PCI Express Root Port 3
             fabricant: Intel Corporation
             identifiant matériel: 1c.2
             information bus: pci@0000:00:1c.2
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration : driver=pcieport
             ressources : irq:88 portE/S:4000(taille=4096) mémoire:90600000-906fffff
           *-network
                description: Interface réseau sans fil
                produit: QCA9565 / AR9565 Wireless Network Adapter
                fabricant: Qualcomm Atheros
                identifiant matériel: 0
                information bus: pci@0000:02:00.0
                nom logique: wls2
                version: 01
                numéro de série: d0:53:49:8a:35:10
                bits: 64 bits
                horloge: 33MHz
                fonctionnalités: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
                configuration : broadcast=yes driver=ath9k driverversion=5.4.0-47-generic firmware=N/A ip=192.168.1.12 latency=0 link=yes multicast=yes wireless=IEEE 802.11
                ressources : irq:18 mémoire:90600000-9067ffff mémoire:90680000-9068ffff
        *-pci:2
             description: PCI bridge
             produit: Atom Processor E3800 Series PCI Express Root Port 4
             fabricant: Intel Corporation
             identifiant matériel: 1c.3
             information bus: pci@0000:00:1c.3
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration : driver=pcieport
             ressources : irq:89 portE/S:1000(taille=4096) mémoire:90500000-905fffff portE/S:90400000(taille=1048576)
           *-network
                description: Ethernet interface
                produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
                fabricant: Realtek Semiconductor Co., Ltd.
                identifiant matériel: 0
                information bus: pci@0000:03:00.0
                nom logique: ens3
                version: 0c
                numéro de série: 30:65:ec:6e:b9:35
                capacité: 1Gbit/s
                bits: 64 bits
                horloge: 33MHz
                fonctionnalités: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
                configuration : autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168g-2_0.0.1 02/06/13 latency=0 link=no multicast=yes port=MII
                ressources : irq:19 portE/S:1000(taille=256) mémoire:90500000-90500fff mémoire:90400000-90403fff
        *-usb:1
             description: USB controller
             produit: Atom Processor Z36xxx/Z37xxx Series USB EHCI
             fabricant: Intel Corporation
             identifiant matériel: 1d
             information bus: pci@0000:00:1d.0
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: pm debug ehci bus_master cap_list
             configuration : driver=ehci-pci latency=0
             ressources : irq:23 mémoire:90918000-909183ff
           *-usbhost
                produit: EHCI Host Controller
                fabricant: Linux 5.4.0-47-generic ehci_hcd
                identifiant matériel: 1
                information bus: usb@1
                nom logique: usb1
                version: 5.04
                fonctionnalités: usb-2.00
                configuration : driver=hub slots=8 speed=480Mbit/s
              *-usb
                   description: Concentrateur USB
                   fabricant: Intel Corp.
                   identifiant matériel: 1
                   information bus: usb@1:1
                   version: 0.14
                   fonctionnalités: usb-2.00
                   configuration : driver=hub slots=4 speed=480Mbit/s
        *-isa
             description: ISA bridge
             produit: Atom Processor Z36xxx/Z37xxx Series Power Control Unit
             fabricant: Intel Corporation
             identifiant matériel: 1f
             information bus: pci@0000:00:1f.0
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: isa bus_master cap_list
             configuration : driver=lpc_ich latency=0
             ressources : irq:0
        *-serial
             description: SMBus
             produit: Atom Processor E3800 Series SMBus Controller
             fabricant: Intel Corporation
             identifiant matériel: 1f.3
             information bus: pci@0000:00:1f.3
             version: 0e
             bits: 32 bits
             horloge: 33MHz
             fonctionnalités: pm cap_list
             configuration : driver=i801_smbus latency=0
             ressources : irq:18 mémoire:90919000-9091901f portE/S:2000(taille=32)
     *-pnp00:00
          produit: PnP device PNP0b00
          identifiant matériel: 1
          fonctionnalités: pnp
          configuration : driver=rtc_cmos
     *-pnp00:01
          produit: PnP device PNP0c02
          identifiant matériel: 2
          fonctionnalités: pnp
          configuration : driver=system
     *-pnp00:02
          produit: PnP device PNP0303
          identifiant matériel: 3
          fonctionnalités: pnp
          configuration : driver=i8042 kbd
     *-pnp00:03
          produit: PnP device ETD050a
          identifiant matériel: 5
          fonctionnalités: pnp
          configuration : driver=i8042 aux
     *-pnp00:04
          produit: PnP device PNP0c02
          identifiant matériel: 6
          fonctionnalités: pnp
          configuration : driver=system

Hors ligne

#16 Le 10/09/2020, à 14:11

geole

Re : Ubuntu 20.04 lts ne s'éteint pas

Bonjour
Peux-tu donner le jour et approximativement l'heure de l'impossibilité d'arrêt afin de tenter d'extraire la trace de cet arrêt pour éviter qu'elle soit trop volumineuse.

Dernière modification par geole (Le 10/09/2020, à 14:12)

En ligne

#17 Le 10/09/2020, à 14:44

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

geole a écrit :

Bonjour
Peux-tu donner le jour et approximativement l'heure de l'impossibilité d'arrêt afin de tenter d'extraire la trace de cet arrêt pour éviter qu'elle soit trop volumineuse.

Bonjour Geole
Là c'est vraiment pas possible, ça date d'un bon moment. Au début j'utilisais le bouton on/off croyant que ça fait l'affaire mais là ça devient embettant pour moi

Hors ligne

#18 Le 10/09/2020, à 15:08

geole

Re : Ubuntu 20.04 lts ne s'éteint pas

La dernière fois que tu as appuyé sur ce fameux bouton...

En ligne

#19 Le 10/09/2020, à 15:13

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

geole a écrit :

La dernière fois que tu as appuyé sur ce fameux bouton...

Hier vers 23h30 environ

Hors ligne

#20 Le 10/09/2020, à 15:23

geole

Re : Ubuntu 20.04 lts ne s'éteint pas

journalctl    --no-pager --since  "2020-09-09 23:15" --until  "2020-09-09 23:45" 

En ligne

#21 Le 10/09/2020, à 15:32

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

geole a écrit :
journalctl    --no-pager --since  "2020-09-09 23:15" --until  "2020-09-09 23:45" 

ça renvoie ceci :

amor@amor:~$ journalctl    --no-pager --since  "2020-09-09 23:15" --until  "2020-09-09 23:45" 
-- Logs begin at Fri 2020-07-24 14:46:38 CET, end at Thu 2020-09-10 15:31:12 CET. --
-- No entries --
amor@amor:~$

Hors ligne

#22 Le 10/09/2020, à 15:38

geole

Re : Ubuntu 20.04 lts ne s'éteint pas

journalctl    --no-pager --since  "2020-09-09 12:15" --until  "2020-09-09 23:45"  | tail -1000

En ligne

#23 Le 10/09/2020, à 15:40

AMOR19

Re : Ubuntu 20.04 lts ne s'éteint pas

geole a écrit :
journalctl    --no-pager --since  "2020-09-09 12:15" --until  "2020-09-09 23:45"  | tail -1000

Voilà

amor@amor:~$ journalctl    --no-pager --since  "2020-09-09 12:15" --until  "2020-09-09 23:45"  | tail -1000
سبتمبر 09 21:46:07 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 21:46:07 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 21:47:44 amor PackageKit[4456]: daemon quit
سبتمبر 09 21:47:44 amor systemd[1]: packagekit.service: Succeeded.
سبتمبر 09 21:50:45 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 21:50:45 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 21:57:23 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 21:57:23 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 21:58:49 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 21:58:49 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:00:12 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:00:12 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:00:33 amor sudo[4867]: pam_unix(sudo:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type
سبتمبر 09 22:00:37 amor sudo[4867]: pam_unix(sudo:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type
سبتمبر 09 22:00:37 amor sudo[4867]:     amor : TTY=pts/0 ; PWD=/home/amor ; USER=root ; COMMAND=/usr/bin/lshw -class display
سبتمبر 09 22:00:37 amor sudo[4867]: pam_unix(sudo:session): session opened for user root by (uid=0)
سبتمبر 09 22:00:40 amor sudo[4867]: pam_unix(sudo:session): session closed for user root
سبتمبر 09 22:09:01 amor CRON[4895]: pam_unix(cron:session): session opened for user root by (uid=0)
سبتمبر 09 22:09:01 amor CRON[4896]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
سبتمبر 09 22:09:01 amor CRON[4895]: pam_unix(cron:session): session closed for user root
سبتمبر 09 22:09:31 amor systemd[1]: Starting Clean php session files...
سبتمبر 09 22:09:33 amor systemd[1]: phpsessionclean.service: Succeeded.
سبتمبر 09 22:09:33 amor systemd[1]: Finished Clean php session files.
سبتمبر 09 22:10:33 amor kernel: wls2: AP 24:00:ba:94:da:d4 changed bandwidth, new config is 2412 MHz, width 2 (2422/0 MHz)
سبتمبر 09 22:11:25 amor sudo[4994]:     amor : TTY=pts/0 ; PWD=/home/amor ; USER=root ; COMMAND=/usr/bin/add-apt-repository -y ppa:yannubuntu/boot-repair
سبتمبر 09 22:11:25 amor sudo[4994]: pam_unix(sudo:session): session opened for user root by (uid=0)
سبتمبر 09 22:11:34 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.115' (uid=0 pid=5415 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined")
سبتمبر 09 22:11:34 amor systemd[1]: Starting PackageKit Daemon...
سبتمبر 09 22:11:34 amor PackageKit[5418]: daemon start
سبتمبر 09 22:11:34 amor dbus-daemon[641]: [system] Successfully activated service 'org.freedesktop.PackageKit'
سبتمبر 09 22:11:34 amor systemd[1]: Started PackageKit Daemon.
سبتمبر 09 22:11:50 amor sudo[4994]: pam_unix(sudo:session): session closed for user root
سبتمبر 09 22:11:51 amor sudo[5474]:     amor : TTY=pts/0 ; PWD=/home/amor ; USER=root ; COMMAND=/usr/bin/apt update
سبتمبر 09 22:11:51 amor sudo[5474]: pam_unix(sudo:session): session opened for user root by (uid=0)
سبتمبر 09 22:11:59 amor sudo[5474]: pam_unix(sudo:session): session closed for user root
سبتمبر 09 22:11:59 amor sudo[5912]:     amor : TTY=pts/0 ; PWD=/home/amor ; USER=root ; COMMAND=/usr/bin/apt install -y boot-info
سبتمبر 09 22:11:59 amor sudo[5912]: pam_unix(sudo:session): session opened for user root by (uid=0)
سبتمبر 09 22:12:25 amor kernel: perf: interrupt took too long (2537 > 2500), lowering kernel.perf_event_max_sample_rate to 78750
سبتمبر 09 22:12:31 amor dbus-daemon[1014]: [session uid=1000 pid=1014] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.3' (uid=1000 pid=989 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
سبتمبر 09 22:12:32 amor systemd[941]: Starting Tracker metadata database store and lookup manager...
سبتمبر 09 22:12:36 amor dbus-daemon[1014]: [session uid=1000 pid=1014] Successfully activated service 'org.freedesktop.Tracker1'
سبتمبر 09 22:12:36 amor systemd[941]: Started Tracker metadata database store and lookup manager.
سبتمبر 09 22:12:54 amor dbus-daemon[1014]: [session uid=1000 pid=1014] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.3' (uid=1000 pid=989 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
سبتمبر 09 22:12:54 amor systemd[941]: Starting Tracker metadata extractor...
سبتمبر 09 22:12:54 amor tracker-extract[6111]: Set scheduler policy to SCHED_IDLE
سبتمبر 09 22:12:54 amor tracker-extract[6111]: Setting priority nice level to 19
سبتمبر 09 22:12:58 amor dbus-daemon[1014]: [session uid=1000 pid=1014] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
سبتمبر 09 22:12:58 amor systemd[941]: Started Tracker metadata extractor.
سبتمبر 09 22:13:10 amor systemd[941]: tracker-extract.service: Succeeded.
سبتمبر 09 22:13:27 amor sudo[5912]: pam_unix(sudo:session): session closed for user root
سبتمبر 09 22:13:28 amor sudo[6751]:     amor : TTY=pts/0 ; PWD=/home/amor ; USER=root ; COMMAND=/usr/sbin/boot-info-bin
سبتمبر 09 22:13:29 amor sudo[6751]: pam_unix(sudo:session): session opened for user root by (uid=0)
سبتمبر 09 22:13:37 amor dbus-daemon[6796]: [session uid=0 pid=6763] AppArmor D-Bus mediation is enabled
سبتمبر 09 22:13:37 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.120' (uid=0 pid=6754 comm="/usr/bin/python3 /usr/bin/glade2script-python3 -g " label="unconfined")
سبتمبر 09 22:13:39 amor systemd[1]: Starting Hostname Service...
سبتمبر 09 22:13:41 amor dbus-daemon[641]: [system] Successfully activated service 'org.freedesktop.hostname1'
سبتمبر 09 22:13:41 amor systemd[1]: Started Hostname Service.
سبتمبر 09 22:13:50 amor pkexec[8339]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
سبتمبر 09 22:13:50 amor pkexec[8339]: amor: Executing command [USER=root] [TTY=unknown] [CWD=/home/amor] [COMMAND=/usr/lib/update-notifier/package-system-locked]
سبتمبر 09 22:13:54 amor kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
سبتمبر 09 22:13:54 amor kernel: JFS: nTxBlock = 8192, nTxLock = 65536
سبتمبر 09 22:13:54 amor kernel: ntfs: driver 2.1.32 [Flags: R/O MODULE].
سبتمبر 09 22:13:55 amor kernel: QNX4 filesystem 0.2.3 registered.
سبتمبر 09 22:13:55 amor kernel: raid6: sse2x4   gen()  1097 MB/s
سبتمبر 09 22:13:55 amor kernel: raid6: sse2x4   xor()  1303 MB/s
سبتمبر 09 22:13:55 amor kernel: raid6: sse2x2   gen()  1009 MB/s
سبتمبر 09 22:13:55 amor kernel: raid6: sse2x2   xor()  3030 MB/s
سبتمبر 09 22:13:55 amor kernel: raid6: sse2x1   gen()  1001 MB/s
سبتمبر 09 22:13:55 amor kernel: raid6: sse2x1   xor()  2545 MB/s
سبتمبر 09 22:13:55 amor kernel: raid6: using algorithm sse2x4 gen() 1097 MB/s
سبتمبر 09 22:13:55 amor kernel: raid6: .... xor() 1303 MB/s, rmw enabled
سبتمبر 09 22:13:55 amor kernel: raid6: using ssse3x2 recovery algorithm
سبتمبر 09 22:13:56 amor kernel: xor: measuring software checksum speed
سبتمبر 09 22:13:56 amor tracker-store[6007]: OK
سبتمبر 09 22:13:56 amor kernel:    prefetch64-sse:  9049.000 MB/sec
سبتمبر 09 22:13:56 amor kernel:    generic_sse:  8077.000 MB/sec
سبتمبر 09 22:13:56 amor kernel: xor: using function: prefetch64-sse (9049.000 MB/sec)
سبتمبر 09 22:13:56 amor systemd[941]: tracker-store.service: Succeeded.
سبتمبر 09 22:13:56 amor kernel: Btrfs loaded, crc32c=crc32c-intel
سبتمبر 09 22:13:56 amor os-prober[8753]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/sda1
سبتمبر 09 22:13:56 amor 05efi[8755]: debug: Not on UEFI platform
سبتمبر 09 22:13:56 amor os-prober[8756]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/sda1
سبتمبر 09 22:13:56 amor 10freedos[8758]: debug: /dev/sda1 is a FAT32 partition
سبتمبر 09 22:13:56 amor os-prober[8761]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/sda1
سبتمبر 09 22:13:56 amor 10qnx[8764]: debug: /dev/sda1 is not a QNX4 partition: exiting
سبتمبر 09 22:13:56 amor os-prober[8765]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/sda1
سبتمبر 09 22:13:56 amor macosx-prober[8767]: debug: /dev/sda1 is not an HFS+ partition: exiting
سبتمبر 09 22:13:56 amor os-prober[8768]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/sda1
سبتمبر 09 22:13:56 amor 20microsoft[8770]: debug: /dev/sda1 is a FAT32 partition
سبتمبر 09 22:13:56 amor os-prober[8779]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/sda1
سبتمبر 09 22:13:56 amor 30utility[8781]: debug: /dev/sda1 is a FAT32 partition
سبتمبر 09 22:13:56 amor os-prober[8786]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sda1
سبتمبر 09 22:13:56 amor os-prober[8788]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/sda1
سبتمبر 09 22:13:56 amor os-prober[8791]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/sda1
سبتمبر 09 22:13:56 amor os-prober[8793]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/sda1
سبتمبر 09 22:13:56 amor 83haiku[8795]: debug: /dev/sda1 is not a BeFS partition: exiting
سبتمبر 09 22:13:56 amor os-prober[8796]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/sda1
سبتمبر 09 22:13:56 amor os-prober[8800]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sda1
سبتمبر 09 22:13:57 amor os-prober[8807]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
سبتمبر 09 22:13:57 amor 50mounted-tests[8816]: debug: /dev/sda2 type not recognised; skipping
سبتمبر 09 22:13:57 amor os-prober[8817]: debug: os detected by /usr/lib/os-probes/50mounted-tests
سبتمبر 09 22:13:57 amor os-prober[8993]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/sda1
سبتمبر 09 22:13:57 amor 05efi[8995]: debug: Not on UEFI platform
سبتمبر 09 22:13:57 amor os-prober[8996]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/sda1
سبتمبر 09 22:13:57 amor 10freedos[8998]: debug: /dev/sda1 is a FAT32 partition
سبتمبر 09 22:13:58 amor os-prober[9001]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/sda1
سبتمبر 09 22:13:58 amor 10qnx[9003]: debug: /dev/sda1 is not a QNX4 partition: exiting
سبتمبر 09 22:13:58 amor os-prober[9004]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/sda1
سبتمبر 09 22:13:58 amor macosx-prober[9006]: debug: /dev/sda1 is not an HFS+ partition: exiting
سبتمبر 09 22:13:58 amor os-prober[9007]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/sda1
سبتمبر 09 22:13:58 amor 20microsoft[9009]: debug: /dev/sda1 is a FAT32 partition
سبتمبر 09 22:13:58 amor os-prober[9018]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/sda1
سبتمبر 09 22:13:58 amor 30utility[9021]: debug: /dev/sda1 is a FAT32 partition
سبتمبر 09 22:13:58 amor os-prober[9026]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sda1
سبتمبر 09 22:13:58 amor os-prober[9028]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/sda1
سبتمبر 09 22:13:58 amor os-prober[9030]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/sda1
سبتمبر 09 22:13:58 amor os-prober[9032]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/sda1
سبتمبر 09 22:13:58 amor 83haiku[9034]: debug: /dev/sda1 is not a BeFS partition: exiting
سبتمبر 09 22:13:58 amor os-prober[9035]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/sda1
سبتمبر 09 22:13:58 amor os-prober[9039]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sda1
سبتمبر 09 22:13:58 amor os-prober[9046]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
سبتمبر 09 22:13:58 amor 50mounted-tests[9054]: debug: /dev/sda2 type not recognised; skipping
سبتمبر 09 22:13:58 amor os-prober[9055]: debug: os detected by /usr/lib/os-probes/50mounted-tests
سبتمبر 09 22:14:12 amor systemd[1]: systemd-hostnamed.service: Succeeded.
سبتمبر 09 22:14:45 amor systemd[941]: boot-efi.mount: Succeeded.
سبتمبر 09 22:14:45 amor systemd[1]: boot-efi.mount: Succeeded.
سبتمبر 09 22:14:48 amor systemd[1]: mnt-BootInfo-sda1.mount: Succeeded.
سبتمبر 09 22:14:48 amor systemd[941]: mnt-BootInfo-sda1.mount: Succeeded.
سبتمبر 09 22:15:33 amor sudo[6751]: pam_unix(sudo:session): session closed for user root
سبتمبر 09 22:17:01 amor CRON[18230]: pam_unix(cron:session): session opened for user root by (uid=0)
سبتمبر 09 22:17:01 amor CRON[18231]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
سبتمبر 09 22:17:01 amor CRON[18230]: pam_unix(cron:session): session closed for user root
سبتمبر 09 22:18:14 amor PackageKit[5418]: daemon quit
سبتمبر 09 22:18:14 amor systemd[1]: packagekit.service: Succeeded.
سبتمبر 09 22:20:40 amor freshclam[917]: Wed Sep  9 22:20:40 2020 -> Received signal: wake up
سبتمبر 09 22:20:40 amor freshclam[917]: Wed Sep  9 22:20:40 2020 -> ClamAV update process started at Wed Sep  9 22:20:40 2020
سبتمبر 09 22:20:44 amor freshclam[917]: Wed Sep  9 22:20:44 2020 -> daily.cld database is up to date (version: 25925, sigs: 4302711, f-level: 63, builder: raynman)
سبتمبر 09 22:20:44 amor freshclam[917]: Wed Sep  9 22:20:44 2020 -> main.cvd database is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
سبتمبر 09 22:20:44 amor freshclam[917]: Wed Sep  9 22:20:44 2020 -> bytecode.cvd database is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
سبتمبر 09 22:22:33 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:22:33 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:22:46 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:22:46 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:24:52 amor kernel: perf: interrupt took too long (3179 > 3171), lowering kernel.perf_event_max_sample_rate to 62750
سبتمبر 09 22:30:01 amor CRON[18408]: pam_unix(cron:session): session opened for user root by (uid=0)
سبتمبر 09 22:30:01 amor CRON[18409]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
سبتمبر 09 22:30:01 amor CRON[18408]: pam_unix(cron:session): session closed for user root
سبتمبر 09 22:30:04 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:30:04 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:30:51 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:30:51 amor rtkit-daemon[1008]: Supervising 4 threads of 2 processes of 1 users.
سبتمبر 09 22:34:09 amor systemd[1]: Condition check resulted in Run anacron jobs being skipped.
سبتمبر 09 22:34:17 amor systemd[941]: gnome-launched-firefox.desktop-3219.scope: Succeeded.
سبتمبر 09 22:34:19 amor systemd[941]: gnome-terminal-server.service: Succeeded.
سبتمبر 09 22:35:00 amor gnome-shell[2252]: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
سبتمبر 09 22:35:19 amor gnome-session[2224]: gnome-session-binary[2224]: WARNING: Client '/org/gnome/SessionManager/Client23' failed to reply before timeout
سبتمبر 09 22:35:19 amor gnome-session-binary[2224]: WARNING: Client '/org/gnome/SessionManager/Client23' failed to reply before timeout
سبتمبر 09 22:35:19 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.53' (uid=1000 pid=2252 comm="/usr/bin/gnome-shell " label="unconfined")
سبتمبر 09 22:35:19 amor systemd[1]: Starting PackageKit Daemon...
سبتمبر 09 22:35:20 amor PackageKit[18555]: daemon start
سبتمبر 09 22:35:21 amor dbus-daemon[641]: [system] Successfully activated service 'org.freedesktop.PackageKit'
سبتمبر 09 22:35:21 amor systemd[1]: Started PackageKit Daemon.
سبتمبر 09 22:35:22 amor gnome-shell[2252]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 1
سبتمبر 09 22:35:22 amor gnome-shell[2252]: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor1
سبتمبر 09 22:35:28 amor systemd[941]: at-spi-dbus-bus.service: Succeeded.
سبتمبر 09 22:35:28 amor systemd[941]: gsd-a11y-settings.service: Succeeded.
سبتمبر 09 22:35:29 amor kernel: rfkill: input handler enabled
سبتمبر 09 22:35:28 amor systemd[941]: gsd-housekeeping.service: Succeeded.
سبتمبر 09 22:35:28 amor systemd[941]: Stopped GNOME Maintenance of expirable data.
سبتمبر 09 22:35:28 amor systemd[941]: gsd-print-notifications.service: Succeeded.
سبتمبر 09 22:35:28 amor systemd[941]: gsd-screensaver-proxy.service: Succeeded.
سبتمبر 09 22:35:28 amor systemd[941]: gsd-sound.service: Succeeded.
سبتمبر 09 22:35:28 amor systemd[941]: gsd-usb-protection.service: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: gsd-rfkill.service: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped GNOME RFKill handling.
سبتمبر 09 22:35:30 amor systemd[941]: gsd-sharing.service: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: gsd-wacom.service: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: gsd-wwan.service: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME X11 Session (session: ubuntu).
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target Current graphical user session.
سبتمبر 09 22:35:30 amor systemd[941]: unicast-local-avahi.path: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped Path trigger for Avahi .local domain notifications.
سبتمبر 09 22:35:30 amor systemd[941]: update-notifier-crash.path: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped Path trigger for Apport crash notifications.
سبتمبر 09 22:35:30 amor systemd[941]: update-notifier-release.path: Succeeded.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped Path trigger for new release of Ubuntu notifications.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Session.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME X11 Session.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Session (session: ubuntu).
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Accessibility settings.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Color management.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Date & Time handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Maintenance of expirable data.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Keyboard handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Media keys handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Power management handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Printer notifications.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME RFKill handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Freedesktop screensaver handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Sharing handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Smartcard handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Sound sample caching handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME USB protection handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME Wacom handling.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME WWan management.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME XSettings.
سبتمبر 09 22:35:30 amor systemd[941]: Stopped target GNOME session X11 services.
سبتمبر 09 22:35:30 amor systemd[941]: Stopping GNOME Smartcard handling...
سبتمبر 09 22:35:31 amor systemd[941]: gsd-keyboard.service: Succeeded.
سبتمبر 09 22:35:31 amor systemd[941]: Stopped GNOME Keyboard handling.
سبتمبر 09 22:35:31 amor systemd[941]: gsd-power.service: Succeeded.
سبتمبر 09 22:35:31 amor systemd[941]: Stopped GNOME Power management handling.
سبتمبر 09 22:35:31 amor systemd[941]: gsd-color.service: Succeeded.
سبتمبر 09 22:35:31 amor systemd[941]: Stopped GNOME Color management.
سبتمبر 09 22:35:31 amor pulseaudio[986]: ICE default IO error handler doing an exit(), pid = 986, errno = 32
سبتمبر 09 22:35:32 amor systemd[941]: gsd-xsettings.service: Succeeded.
سبتمبر 09 22:35:32 amor systemd[941]: Stopped GNOME XSettings.
سبتمبر 09 22:35:32 amor systemd[941]: gsd-datetime.service: Succeeded.
سبتمبر 09 22:35:32 amor systemd[941]: Stopped GNOME Date & Time handling.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: State 'stop-sigterm' timed out. Killing.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Killing process 2373 (gsd-media-keys) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Killing process 2425 (gmain) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Killing process 2429 (gdbus) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Killing process 2470 (dconf worker) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: State 'stop-sigterm' timed out. Killing.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Killing process 2379 (gsd-smartcard) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Killing process 2406 (gmain) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Killing process 2428 (gdbus) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Killing process 2455 (pool-gsd-smartc) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Killing process 2456 (dconf worker) with signal SIGKILL.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Main process exited, code=killed, status=9/KILL
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Failed with result 'timeout'.
سبتمبر 09 22:35:36 amor systemd[941]: Stopped GNOME Media keys handling.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Triggering OnFailure= dependencies.
سبتمبر 09 22:35:36 amor systemd[941]: Requested transaction contradicts existing jobs: Transaction for gnome-session-failed.target/start is destructive (gnome-session-pre.target has 'stop' job queued, but 'start' is included in transaction).
سبتمبر 09 22:35:36 amor systemd[941]: gsd-media-keys.service: Failed to enqueue OnFailure= job, ignoring: Transaction for gnome-session-failed.target/start is destructive (gnome-session-pre.target has 'stop' job queued, but 'start' is included in transaction).
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Main process exited, code=killed, status=9/KILL
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Failed with result 'timeout'.
سبتمبر 09 22:35:36 amor systemd[941]: Stopped GNOME Smartcard handling.
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Triggering OnFailure= dependencies.
سبتمبر 09 22:35:36 amor systemd[941]: Requested transaction contradicts existing jobs: Transaction for gnome-session-failed.target/start is destructive (gnome-session-shutdown.target has 'start' job queued, but 'stop' is included in transaction).
سبتمبر 09 22:35:36 amor systemd[941]: gsd-smartcard.service: Failed to enqueue OnFailure= job, ignoring: Transaction for gnome-session-failed.target/start is destructive (gnome-session-shutdown.target has 'start' job queued, but 'stop' is included in transaction).
سبتمبر 09 22:35:36 amor systemd[941]: Stopped target GNOME Session is initialized.
سبتمبر 09 22:35:36 amor systemd[941]: Stopped target GNOME Shell on X11.
سبتمبر 09 22:35:36 amor systemd[941]: Stopping GNOME Shell on X11...
سبتمبر 09 22:35:36 amor gnome-shell[2252]: Object Meta.BackgroundActor (0x55582326cee0), 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.
سبتمبر 09 22:35:36 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:36 amor gnome-shell[2252]: #0   7ffd2dd57cf0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (31154abb6c40 @ 25)
سبتمبر 09 22:35:36 amor gnome-shell[2252]: #1   555823ea57c0 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (254b9e2a6088 @ 85)
سبتمبر 09 22:35:36 amor gnome-shell[2252]: #2   555823ea5738 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (254b9e2a0e20 @ 12)
سبتمبر 09 22:35:36 amor gnome-shell[2252]: 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
سبتمبر 09 22:35:36 amor gnome-shell[2252]: meta_get_stage_for_display: assertion 'compositor' failed
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555826879610.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826790180.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826790180.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826792310.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826aeee20.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826aeee20.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826af05d0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826af6c30.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826af6c30.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826af8450.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55582676ff30.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55582676ff30.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5558267712c0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267a3680.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267a3680.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5558267a4f90.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826b08000.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826b08000.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826b09310.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826768da0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826768da0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55582676a100.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267998c0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267998c0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55582679b200.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558223d6b60.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558223d6b60.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5558223d7eb0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267778b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267778b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826779430.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826787490.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826787490.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55582678a5a0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267ac110.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267ac110.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5558267ad4a0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826b000b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826b000b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826b01a10.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55582677ed50.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55582677ed50.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826780880.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826759490.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x555826759490.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55582675af50.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267608e0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5558267608e0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x555826762530.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x555826acc8b0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was notify on NMDeviceEthernet 0x5558247b61e0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: == Stack trace for context 0x555821d5c700 ==
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was notify on NMDeviceWifi 0x5558247ba280.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was notify on NMActiveConnection 0x5558247c1180.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was state-changed on NMDeviceEthernet 0x5558247b61e0.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
سبتمبر 09 22:35:38 amor gnome-shell[2252]: The offending signal was state-changed on NMDeviceWifi 0x5558247ba280.
سبتمبر 09 22:35:39 amor systemd[941]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
سبتمبر 09 22:35:39 amor systemd[941]: pulseaudio.service: Failed with result 'exit-code'.
سبتمبر 09 22:35:39 amor systemd[941]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
سبتمبر 09 22:35:39 amor systemd[941]: Stopped Sound Service.
سبتمبر 09 22:35:39 amor systemd[941]: Starting Sound Service...
سبتمبر 09 22:35:39 amor bluetoothd[638]: Endpoint unregistered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc
سبتمبر 09 22:35:39 amor bluetoothd[638]: Endpoint unregistered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc
سبتمبر 09 22:35:40 amor rtkit-daemon[1008]: Successfully made thread 18588 of process 18588 owned by '1000' high priority at nice level -11.
سبتمبر 09 22:35:40 amor rtkit-daemon[1008]: Supervising 1 threads of 1 processes of 1 users.
سبتمبر 09 22:35:40 amor pulseaudio[18588]: Stale PID file, overwriting.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: State 'stop-sigterm' timed out. Killing.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2252 (gnome-shell) with signal SIGKILL.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2264 (gmain) with signal SIGKILL.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2268 (gdbus) with signal SIGKILL.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2269 (dconf worker) with signal SIGKILL.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2272 (gnome-s:disk$2) with signal SIGKILL.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2273 (gnome-s:disk$3) with signal SIGKILL.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2279 (JS Helper) with signal SIGKILL.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Killing process 2280 (JS Helper) with signal SIGKILL.
سبتمبر 09 22:35:41 amor polkitd(authority=local)[653]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.53, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus)
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Main process exited, code=killed, status=9/KILL
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Failed with result 'timeout'.
سبتمبر 09 22:35:41 amor systemd[941]: Stopped GNOME Shell on X11.
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Triggering OnFailure= dependencies.
سبتمبر 09 22:35:41 amor systemd[941]: Requested transaction contradicts existing jobs: Transaction for gnome-session-failed.target/start is destructive (gnome-session-pre.target has 'stop' job queued, but 'start' is included in transaction).
سبتمبر 09 22:35:41 amor systemd[941]: gnome-shell-x11.service: Failed to enqueue OnFailure= job, ignoring: Transaction for gnome-session-failed.target/start is destructive (gnome-session-pre.target has 'stop' job queued, but 'start' is included in transaction).
سبتمبر 09 22:35:41 amor systemd[941]: Stopped target GNOME Session Manager is ready.
سبتمبر 09 22:35:41 amor systemd[941]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped.
سبتمبر 09 22:35:42 amor systemd[941]: gnome-session-manager@ubuntu.service: Succeeded.
سبتمبر 09 22:35:42 amor systemd[941]: Stopped GNOME Session Manager (session: ubuntu).
سبتمبر 09 22:35:42 amor systemd[941]: Stopped target Tasks to be run before GNOME Session starts.
سبتمبر 09 22:35:42 amor systemd[941]: Stopped target Session services which should run early before the graphical session is brought up.
سبتمبر 09 22:35:42 amor systemd[941]: Reached target Shutdown running GNOME Session.
سبتمبر 09 22:35:42 amor systemd[941]: Stopping Start gnome-keyring as SSH agent...
سبتمبر 09 22:35:42 amor systemd[941]: Stopping Monitor Session leader for GNOME Session...
سبتمبر 09 22:35:42 amor systemd[941]: Starting Restart DBus after GNOME Session shutdown...
سبتمبر 09 22:35:42 amor systemd[941]: gnome-keyring-ssh.service: Succeeded.
سبتمبر 09 22:35:42 amor systemd[941]: Stopped Start gnome-keyring as SSH agent.
سبتمبر 09 22:35:42 amor systemd[941]: Stopped target Shutdown running GNOME Session.
سبتمبر 09 22:35:42 amor systemd[941]: Started Restart DBus after GNOME Session shutdown.
سبتمبر 09 22:35:42 amor systemd[941]: Reached target Shutdown running GNOME Session.
سبتمبر 09 22:35:43 amor gvfsd[1584]: A connection to the bus can't be made
سبتمبر 09 22:35:43 amor tracker-miner-fs[989]: Received signal:15->'Complété'
سبتمبر 09 22:35:43 amor gvfsd[2487]: A connection to the bus can't be made
سبتمبر 09 22:35:43 amor systemd[941]: Stopping D-Bus User Message Bus...
سبتمبر 09 22:35:43 amor systemd[941]: gvfs-udisks2-volume-monitor.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: gvfs-mtp-volume-monitor.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: gvfs-gphoto2-volume-monitor.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: xdg-desktop-portal.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: gnome-session-monitor.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: Stopped Monitor Session leader for GNOME Session.
سبتمبر 09 22:35:43 amor systemd[941]: xdg-desktop-portal-gtk.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: gnome-session-restart-dbus.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: dbus.service: Succeeded.
سبتمبر 09 22:35:43 amor systemd[941]: Stopped D-Bus User Message Bus.
سبتمبر 09 22:35:43 amor systemd[941]: Stopped target Shutdown running GNOME Session.
سبتمبر 09 22:35:43 amor systemd[941]: Started D-Bus User Message Bus.
سبتمبر 09 22:35:44 amor tracker-miner-f[989]: Error while sending AddMatch() message: La connexion est fermée
سبتمبر 09 22:35:44 amor tracker-miner-f[989]: Error while sending AddMatch() message: La connexion est fermée
سبتمبر 09 22:35:44 amor tracker-miner-f[989]: Error while sending AddMatch() message: La connexion est fermée
سبتمبر 09 22:35:44 amor systemd[941]: gvfs-metadata.service: Succeeded.
سبتمبر 09 22:35:44 amor systemd[941]: gvfs-goa-volume-monitor.service: Succeeded.
سبتمبر 09 22:35:45 amor systemd[941]: gvfs-afc-volume-monitor.service: Succeeded.
سبتمبر 09 22:35:45 amor systemd[941]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
سبتمبر 09 22:35:45 amor systemd[941]: xdg-permission-store.service: Failed with result 'exit-code'.
سبتمبر 09 22:35:46 amor tracker-miner-fs[989]: OK
سبتمبر 09 22:35:46 amor systemd[1]: run-user-1000-gvfs.mount: Succeeded.
سبتمبر 09 22:35:46 amor systemd[941]: run-user-1000-gvfs.mount: Succeeded.
سبتمبر 09 22:35:46 amor systemd[941]: run-user-1000-doc.mount: Succeeded.
سبتمبر 09 22:35:46 amor systemd[941]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
سبتمبر 09 22:35:46 amor systemd[941]: xdg-document-portal.service: Failed with result 'exit-code'.
سبتمبر 09 22:35:46 amor systemd[1]: run-user-1000-doc.mount: Succeeded.
سبتمبر 09 22:35:46 amor systemd[941]: gvfs-daemon.service: Succeeded.
سبتمبر 09 22:35:47 amor evolution-calen[2347]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
سبتمبر 09 22:35:48 amor evolution-addre[2514]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: La connexion est fermée (g-io-error-quark, 18)
سبتمبر 09 22:35:48 amor systemd[941]: tracker-miner-fs.service: Succeeded.
سبتمبر 09 22:35:48 amor systemd[941]: vte-spawn-2fa18670-2d76-4d7d-97d7-fb0bbd16451b.scope: Succeeded.
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "22"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event3  - Power Button: device removed
سبتمبر 09 22:35:49 amor systemd[941]: evolution-source-registry.service: Succeeded.
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "25"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event7  - Video Bus: device removed
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "26"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event0  - Power Button: device removed
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "27"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event1  - Sleep Button: device removed
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "28"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event6  - USB OPTICAL MOUSE : device removed
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "29"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event9  - VGA Webcam: VGA Webcam: device removed
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "30"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event4  - AT Translated Set 2 keyboard: device removed
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "31"
سبتمبر 09 22:35:49 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event5  - ETPS/2 Elantech Touchpad: device removed
سبتمبر 09 22:35:50 amor /usr/lib/gdm3/gdm-x-session[1004]: (**) Option "fd" "32"
سبتمبر 09 22:35:50 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) event8  - Acer WMI hotkeys: device removed
سبتمبر 09 22:35:50 amor systemd[941]: evolution-calendar-factory.service: Succeeded.
سبتمبر 09 22:35:51 amor systemd[941]: evolution-addressbook-factory.service: Succeeded.
سبتمبر 09 22:35:51 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:51 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:72
سبتمبر 09 22:35:51 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:51 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:69
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:68
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:73
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:70
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:65
سبتمبر 09 22:35:52 amor systemd-logind[684]: System is powering down.
سبتمبر 09 22:35:52 amor systemd[1]: unattended-upgrades.service: Succeeded.
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:64
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:52 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:71
سبتمبر 09 22:35:53 amor dbus-daemon[18596]: [session uid=1000 pid=18596] AppArmor D-Bus mediation is enabled
سبتمبر 09 22:35:53 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) UnloadModule: "libinput"
سبتمبر 09 22:35:53 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) systemd-logind: releasing fd for 13:67
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Session 1 of user amor.
سبتمبر 09 22:35:53 amor systemd[1]: Removed slice system-getty.slice.
سبتمبر 09 22:35:53 amor systemd[1]: Removed slice system-modprobe.slice.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped target Bluetooth.
سبتمبر 09 22:35:53 amor freshclam[917]: Wed Sep  9 22:35:53 2020 -> Update process terminated
سبتمبر 09 22:35:53 amor bluetoothd[638]: Terminating
سبتمبر 09 22:35:53 amor systemd[1]: Stopped target Graphical Interface.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped target Multi-User System.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped target Login Prompts.
سبتمبر 09 22:35:53 amor ModemManager[813]: <info>  Caught signal, shutting down...
سبتمبر 09 22:35:53 amor systemd[1]: Stopped target Sound Card.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped target Timers.
سبتمبر 09 22:35:53 amor systemd[1]: anacron.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Trigger anacron every hour.
سبتمبر 09 22:35:53 amor systemd[1]: apt-daily-upgrade.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Daily apt upgrade and clean activities.
سبتمبر 09 22:35:53 amor systemd[1]: apt-daily.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Daily apt download activities.
سبتمبر 09 22:35:53 amor systemd[1]: e2scrub_all.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
سبتمبر 09 22:35:53 amor systemd[1]: fstrim.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Discard unused blocks once a week.
سبتمبر 09 22:35:53 amor systemd[1]: fwupd-refresh.timer: Succeeded.
سبتمبر 09 22:35:53 amor bluetoothd[638]: Stopping SDP server
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Refresh fwupd metadata regularly.
سبتمبر 09 22:35:53 amor bluetoothd[638]: Exit
سبتمبر 09 22:35:54 amor systemd-memcached-wrapper[784]: Signal handled: Terminated.
سبتمبر 09 22:35:54 amor thermald[685]: [WARN]Terminating ...
سبتمبر 09 22:35:53 amor systemd[1]: logrotate.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Daily rotation of log files.
سبتمبر 09 22:35:53 amor systemd[1]: man-db.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Daily man-db regeneration.
سبتمبر 09 22:35:53 amor systemd[1]: motd-news.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Message of the Day.
سبتمبر 09 22:35:53 amor systemd[1]: phpsessionclean.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Clean PHP session files every 30 mins.
سبتمبر 09 22:35:53 amor systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Daily Cleanup of Temporary Directories.
سبتمبر 09 22:35:53 amor systemd[1]: systemd-rfkill.socket: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Modem Manager...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Accounts Service...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping ACPI event daemon...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Save/Restore Sound Card State...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping The Apache HTTP Server...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping LSB: automatic crash report generation...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Bluetooth service...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping ClamAV virus database updater...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Manage, Install and Generate Color Profiles...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Regular background program processing daemon...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Make remote CUPS printers available locally...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping GNOME Display Manager...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping LSB: Record successful boot for GRUB...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping irqbalance daemon...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Tool to automatically collect and submit kernel crash signatures...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping memcached daemon...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping MySQL Community Server...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Dispatcher daemon for systemd-networkd...
سبتمبر 09 22:35:53 amor systemd[1]: openvpn.service: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped OpenVPN service.
سبتمبر 09 22:35:53 amor systemd[1]: Stopping PackageKit Daemon...
سبتمبر 09 22:35:53 amor systemd[1]: postfix.service: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Postfix Mail Transport Agent.
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Postfix Mail Transport Agent (instance -)...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping System Logging Service...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping LSB: saslauthd startup script...
سبتمبر 09 22:35:53 amor systemd[1]: snapd.seeded.service: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped Wait until snapd is fully seeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Snap Daemon...
سبتمبر 09 22:35:53 amor systemd[1]: Condition check resulted in Ubuntu core (all-snaps) system shutdown helper setup service being skipped.
سبتمبر 09 22:35:53 amor systemd[1]: systemd-fsck@dev-disk-by\x2duuid-ACE3\x2d1EAD.service: Succeeded.
سبتمبر 09 22:35:53 amor systemd[1]: Stopped File System Check on /dev/disk/by-uuid/ACE3-1EAD.
سبتمبر 09 22:35:54 amor gdm3[825]: Child process 872 was already dead.
سبتمبر 09 22:35:53 amor systemd[1]: Removed slice system-systemd\x2dfsck.slice.
سبتمبر 09 22:35:54 amor gdm3[825]: Unable to kill session worker process
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Load/Save Random Seed...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Thermal Daemon Service...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Disk Manager...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping Daemon for power management...
سبتمبر 09 22:35:53 amor systemd[1]: Stopping crash report submission daemon...
سبتمبر 09 22:35:54 amor udisksd[686]: udisks daemon version 2.8.4 exiting
سبتمبر 09 22:35:55 amor thermald[685]: [WARN]terminating on user request ..
سبتمبر 09 22:35:55 amor systemd[1]: acpid.service: Succeeded.
سبتمبر 09 22:35:55 amor systemd[1]: Stopped ACPI event daemon.
سبتمبر 09 22:35:56 amor pulseaudio[18588]: No UCM verb is valid for hw:0
سبتمبر 09 22:35:57 amor systemd[1]: accounts-daemon.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped Accounts Service.
سبتمبر 09 22:35:57 amor systemd[1]: bluetooth.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped Bluetooth service.
سبتمبر 09 22:35:57 amor systemd[1]: cron.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped Regular background program processing daemon.
سبتمبر 09 22:35:57 amor systemd[1]: irqbalance.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped irqbalance daemon.
سبتمبر 09 22:35:57 amor systemd[1]: networkd-dispatcher.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped Dispatcher daemon for systemd-networkd.
سبتمبر 09 22:35:57 amor systemd[1]: udisks2.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped Disk Manager.
سبتمبر 09 22:35:57 amor systemd[1]: memcached.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped memcached daemon.
سبتمبر 09 22:35:57 amor systemd[1]: rtkit-daemon.service: Succeeded.
سبتمبر 09 22:35:57 amor systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
سبتمبر 09 22:35:58 amor systemd[1]: upower.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped Daemon for power management.
سبتمبر 09 22:35:58 amor systemd[1]: colord.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped Manage, Install and Generate Color Profiles.
سبتمبر 09 22:35:58 amor systemd[1]: thermald.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped Thermal Daemon Service.
سبتمبر 09 22:35:58 amor systemd[1]: packagekit.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped PackageKit Daemon.
سبتمبر 09 22:35:58 amor systemd[1]: alsa-restore.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped Save/Restore Sound Card State.
سبتمبر 09 22:35:58 amor systemd[1]: systemd-random-seed.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped Load/Save Random Seed.
سبتمبر 09 22:35:58 amor systemd[1]: kerneloops.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped Tool to automatically collect and submit kernel crash signatures.
سبتمبر 09 22:35:58 amor systemd[1]: whoopsie.service: Succeeded.
سبتمبر 09 22:35:58 amor systemd[1]: Stopped crash report submission daemon.
سبتمبر 09 22:35:59 amor systemd[1]: clamav-freshclam.service: Succeeded.
سبتمبر 09 22:35:59 amor systemd[1]: Stopped ClamAV virus database updater.
سبتمبر 09 22:35:59 amor /usr/lib/gdm3/gdm-x-session[1004]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
سبتمبر 09 22:35:59 amor /usr/lib/gdm3/gdm-x-session[1004]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
سبتمبر 09 22:35:59 amor /usr/lib/gdm3/gdm-x-session[1004]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
سبتمبر 09 22:35:59 amor rsyslogd[660]: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="660" x-info="https://www.rsyslog.com"] exiting on signal 15.
سبتمبر 09 22:35:59 amor systemd-logind[684]: Session 1 logged out. Waiting for processes to exit.
سبتمبر 09 22:35:59 amor systemd[1]: Stopped target System Time Synchronized.
سبتمبر 09 22:35:59 amor systemd[1]: Stopped target System Time Set.
سبتمبر 09 22:35:59 amor systemd[1]: Stopping Switcheroo Control Proxy service...
سبتمبر 09 22:35:59 amor /usr/lib/gdm3/gdm-x-session[1004]: (II) Server terminated successfully (0). Closing log file.
سبتمبر 09 22:35:59 amor systemd[1]: switcheroo-control.service: Succeeded.
سبتمبر 09 22:35:59 amor systemd[1]: Stopped Switcheroo Control Proxy service.
سبتمبر 09 22:35:59 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.27' (uid=0 pid=825 comm="/usr/sbin/gdm3 " label="unconfined")
سبتمبر 09 22:35:59 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:35:59 amor systemd[1]: gdm.service: Succeeded.
سبتمبر 09 22:35:59 amor gdm3[825]: Failed to contact accountsservice: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.Accounts : Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:35:59 amor systemd[1]: Stopped GNOME Display Manager.
سبتمبر 09 22:35:59 amor gdm3[825]: GLib: g_hash_table_foreach: assertion 'version == hash_table->version' failed
سبتمبر 09 22:35:59 amor systemd[1]: Stopping Firmware update daemon...
سبتمبر 09 22:35:59 amor systemd[1]: Starting Show Plymouth Power Off Screen...
سبتمبر 09 22:35:59 amor systemd[1]: rsyslog.service: Succeeded.
سبتمبر 09 22:35:59 amor systemd[1]: Stopped System Logging Service.
سبتمبر 09 22:35:59 amor systemd[1]: grub-common.service: Succeeded.
سبتمبر 09 22:35:59 amor systemd[1]: Stopped LSB: Record successful boot for GRUB.
سبتمبر 09 22:35:59 amor apport[18619]:  * Stopping automatic crash report generation: apport
سبتمبر 09 22:35:59 amor apport[18619]:    ...done.
سبتمبر 09 22:36:00 amor systemd[1]: apport.service: Succeeded.
سبتمبر 09 22:36:00 amor systemd[1]: Stopped LSB: automatic crash report generation.
سبتمبر 09 22:36:00 amor systemd[1]: Received SIGRTMIN+20 from PID 18654 (plymouthd).
سبتمبر 09 22:36:00 amor ModemManager[813]: <info>  ModemManager is shut down
سبتمبر 09 22:36:00 amor saslauthd[18622]:  * Stopping SASL Authentication Daemon saslauthd
سبتمبر 09 22:36:00 amor saslauthd[18622]:    ...done.
سبتمبر 09 22:36:00 amor systemd[1]: saslauthd.service: Succeeded.
سبتمبر 09 22:36:00 amor systemd[1]: Stopped LSB: saslauthd startup script.
سبتمبر 09 22:36:00 amor NetworkManager[642]: <info>  [1599687360.2836] modem-manager: ModemManager no longer available
سبتمبر 09 22:36:00 amor systemd[1]: cups-browsed.service: Succeeded.
سبتمبر 09 22:36:00 amor systemd[1]: Stopped Make remote CUPS printers available locally.
سبتمبر 09 22:36:00 amor systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
سبتمبر 09 22:36:00 amor systemd[1]: Stopping CUPS Scheduler...
سبتمبر 09 22:36:00 amor systemd[1]: ModemManager.service: Succeeded.
سبتمبر 09 22:36:00 amor systemd[1]: Stopped Modem Manager.
سبتمبر 09 22:36:00 amor systemd[1]: Stopping Authorization Manager...
سبتمبر 09 22:36:00 amor systemd[1]: polkit.service: Succeeded.
سبتمبر 09 22:36:00 amor systemd[1]: Stopped Authorization Manager.
سبتمبر 09 22:36:01 amor postfix/postfix-script[18673]: stopping the Postfix mail system
سبتمبر 09 22:36:01 amor avahi-daemon[637]: Got SIGTERM, quitting.
سبتمبر 09 22:36:01 amor avahi-daemon[637]: Leaving mDNS multicast group on interface wls2.IPv6 with address fd24:ba:94da:cd00:d06e:fd9b:5e44:f83.
سبتمبر 09 22:36:01 amor avahi-daemon[637]: Leaving mDNS multicast group on interface wls2.IPv4 with address 192.168.1.12.
سبتمبر 09 22:36:01 amor avahi-daemon[637]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
سبتمبر 09 22:36:01 amor avahi-daemon[637]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
سبتمبر 09 22:36:01 amor avahi-daemon[637]: avahi-daemon 0.7 exiting.
سبتمبر 09 22:36:01 amor postfix/postfix-script[18680]: waiting for the Postfix mail system to terminate
سبتمبر 09 22:36:01 amor postfix/master[2040]: terminating on signal 15
سبتمبر 09 22:36:01 amor systemd[1]: avahi-daemon.service: Succeeded.
سبتمبر 09 22:36:01 amor systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
سبتمبر 09 22:36:02 amor systemd[1]: postfix@-.service: Succeeded.
سبتمبر 09 22:36:02 amor systemd[1]: Stopped Postfix Mail Transport Agent (instance -).
سبتمبر 09 22:36:02 amor systemd[1]: Removed slice system-postfix.slice.
سبتمبر 09 22:36:02 amor systemd[1]: Stopped target Network is Online.
سبتمبر 09 22:36:02 amor systemd[1]: NetworkManager-wait-online.service: Succeeded.
سبتمبر 09 22:36:02 amor systemd[1]: Stopped Network Manager Wait Online.
سبتمبر 09 22:36:02 amor systemd[1]: Started Show Plymouth Power Off Screen.
سبتمبر 09 22:36:03 amor systemd[1]: cups.service: Succeeded.
سبتمبر 09 22:36:03 amor systemd[1]: Stopped CUPS Scheduler.
سبتمبر 09 22:36:03 amor snapd[682]: main.go:155: Exiting on terminated signal.
سبتمبر 09 22:36:03 amor snapd[682]: udevmon.go:149: udev event error: Unable to parse uevent, err: no buffer space available
سبتمبر 09 22:36:03 amor systemd[1]: fwupd.service: Succeeded.
سبتمبر 09 22:36:03 amor systemd[1]: Stopped Firmware update daemon.
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.130' (uid=1000 pid=18588 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.131' (uid=1000 pid=18588 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.132' (uid=1000 pid=18588 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.133' (uid=1000 pid=18588 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.134' (uid=1000 pid=18588 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.135' (uid=1000 pid=18588 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
سبتمبر 09 22:36:03 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:03 amor systemd[941]: Started Sound Service.
سبتمبر 09 22:36:03 amor pulseaudio[18588]: GetManagedObjects() failed: org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:04 amor apachectl[18632]: [Wed Sep 09 22:36:04.484012 2020] [so:warn] [pid 18632] AH01574: module dav_module is already loaded, skipping
سبتمبر 09 22:36:05 amor systemd[1]: session-1.scope: Succeeded.
سبتمبر 09 22:36:05 amor systemd[1]: Stopped Session 1 of user amor.
سبتمبر 09 22:36:05 amor systemd[1]: Stopping Login Service...
سبتمبر 09 22:36:05 amor systemd[1]: Stopping User Manager for UID 1000...
سبتمبر 09 22:36:05 amor systemd[1]: snapd.service: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Removed slice apps-org.gnome.Terminal.slice.
سبتمبر 09 22:36:05 amor systemd[1]: Stopped Snap Daemon.
سبتمبر 09 22:36:05 amor systemd[941]: Removed slice apps.slice.
سبتمبر 09 22:36:05 amor systemd[941]: Removed slice gnome\x2dsession\x2dmanager.slice.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped target Main User Target.
سبتمبر 09 22:36:05 amor systemd[941]: Stopping D-Bus User Message Bus...
سبتمبر 09 22:36:05 amor systemd[941]: Stopping Sound Service...
سبتمبر 09 22:36:05 amor systemd[941]: dbus.service: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped D-Bus User Message Bus.
سبتمبر 09 22:36:05 amor systemd[941]: pulseaudio.service: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped Sound Service.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped target Basic System.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped target Paths.
سبتمبر 09 22:36:05 amor systemd[941]: ubuntu-report.path: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped Pending report trigger for Ubuntu Report.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped target Sockets.
سبتمبر 09 22:36:05 amor systemd[941]: Stopped target Timers.
سبتمبر 09 22:36:05 amor systemd[941]: dbus.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed D-Bus User Message Bus Socket.
سبتمبر 09 22:36:05 amor systemd[941]: dirmngr.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed GnuPG network certificate management daemon.
سبتمبر 09 22:36:05 amor systemd[941]: gpg-agent-browser.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
سبتمبر 09 22:36:05 amor systemd[941]: gpg-agent-extra.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
سبتمبر 09 22:36:05 amor systemd[941]: gpg-agent-ssh.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed GnuPG cryptographic agent (ssh-agent emulation).
سبتمبر 09 22:36:05 amor systemd[941]: gpg-agent.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed GnuPG cryptographic agent and passphrase cache.
سبتمبر 09 22:36:05 amor systemd[941]: pk-debconf-helper.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed debconf communication socket.
سبتمبر 09 22:36:05 amor systemd[941]: pulseaudio.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed Sound System.
سبتمبر 09 22:36:05 amor systemd[941]: snapd.session-agent.socket: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Closed REST API socket for snapd user session agent.
سبتمبر 09 22:36:05 amor systemd[941]: Reached target Shutdown.
سبتمبر 09 22:36:05 amor systemd[941]: systemd-exit.service: Succeeded.
سبتمبر 09 22:36:05 amor systemd[941]: Finished Exit the Session.
سبتمبر 09 22:36:05 amor systemd[941]: Reached target Exit the Session.
سبتمبر 09 22:36:05 amor systemd[1]: user@1000.service: Succeeded.
سبتمبر 09 22:36:05 amor systemd[1]: Stopped User Manager for UID 1000.
سبتمبر 09 22:36:05 amor systemd[1]: Stopping User Runtime Directory /run/user/1000...
سبتمبر 09 22:36:05 amor systemd[1]: run-user-1000.mount: Succeeded.
سبتمبر 09 22:36:05 amor systemd[1]: Unmounted /run/user/1000.
سبتمبر 09 22:36:05 amor systemd[1]: user-runtime-dir@1000.service: Succeeded.
سبتمبر 09 22:36:05 amor systemd[1]: Stopped User Runtime Directory /run/user/1000.
سبتمبر 09 22:36:05 amor systemd[1]: Removed slice User Slice of UID 1000.
سبتمبر 09 22:36:05 amor systemd[1]: Stopping Permit User Sessions...
سبتمبر 09 22:36:05 amor systemd[1]: systemd-user-sessions.service: Succeeded.
سبتمبر 09 22:36:05 amor systemd[1]: Stopped Permit User Sessions.
سبتمبر 09 22:36:06 amor systemd[1]: systemd-logind.service: Succeeded.
سبتمبر 09 22:36:06 amor systemd[1]: Stopped Login Service.
سبتمبر 09 22:36:06 amor systemd[1]: Stopped target User and Group Name Lookups.
سبتمبر 09 22:36:07 amor apachectl[18632]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
سبتمبر 09 22:36:14 amor systemd[1]: apache2.service: Succeeded.
سبتمبر 09 22:36:14 amor systemd[1]: Stopped The Apache HTTP Server.
سبتمبر 09 22:36:14 amor systemd[1]: Stopped target Host and Network Name Lookups.
سبتمبر 09 22:36:14 amor systemd[1]: Stopped target Remote File Systems.
سبتمبر 09 22:36:18 amor systemd[1]: mysql.service: Succeeded.
سبتمبر 09 22:36:18 amor systemd[1]: Stopped MySQL Community Server.
سبتمبر 09 22:36:18 amor systemd[1]: Stopped target Network.
سبتمبر 09 22:36:18 amor systemd[1]: Stopping Network Manager...
سبتمبر 09 22:36:18 amor NetworkManager[642]: <info>  [1599687378.9709] caught SIGTERM, shutting down normally.
سبتمبر 09 22:36:18 amor systemd[1]: Stopping Network Name Resolution...
سبتمبر 09 22:36:18 amor systemd[1]: Stopping WPA supplicant...
سبتمبر 09 22:36:19 amor kernel: wls2: deauthenticating from 24:00:ba:94:da:d4 by local choice (Reason: 3=DEAUTH_LEAVING)
سبتمبر 09 22:36:19 amor wpa_supplicant[687]: wls2: CTRL-EVENT-DISCONNECTED bssid=24:00:ba:94:da:d4 reason=3 locally_generated=1
سبتمبر 09 22:36:19 amor NetworkManager[642]: <info>  [1599687379.3848] dhcp4 (wls2): canceled DHCP transaction
سبتمبر 09 22:36:19 amor NetworkManager[642]: <info>  [1599687379.3851] dhcp4 (wls2): state changed bound -> done
سبتمبر 09 22:36:19 amor NetworkManager[642]: <info>  [1599687379.4266] device (wls2): DHCPv4: trying to acquire a new lease within 90 seconds
سبتمبر 09 22:36:19 amor NetworkManager[642]: <info>  [1599687379.4308] manager: NetworkManager state is now CONNECTED_SITE
سبتمبر 09 22:36:19 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=642 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
سبتمبر 09 22:36:19 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:19 amor NetworkManager[642]: <info>  [1599687379.5507] device (p2p-dev-wls2): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed')
سبتمبر 09 22:36:19 amor dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=642 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
سبتمبر 09 22:36:19 amor dbus-daemon[641]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
سبتمبر 09 22:36:19 amor wpa_supplicant[687]: nl80211: deinit ifname=wls2 disabled_11b_rates=0
سبتمبر 09 22:36:20 amor NetworkManager[642]: <info>  [1599687380.0005] exiting (success)
سبتمبر 09 22:36:20 amor wpa_supplicant[687]: wls2: CTRL-EVENT-TERMINATING
سبتمبر 09 22:36:20 amor systemd[1]: wpa_supplicant.service: Succeeded.
سبتمبر 09 22:36:20 amor systemd[1]: Stopped WPA supplicant.
سبتمبر 09 22:36:21 amor systemd[1]: NetworkManager.service: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped Network Manager.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped target Network (Pre).
سبتمبر 09 22:36:21 amor systemd[1]: Stopping D-Bus System Message Bus...
سبتمبر 09 22:36:21 amor systemd[1]: dbus.service: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped D-Bus System Message Bus.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped target Basic System.
سبتمبر 09 22:36:21 amor systemd[1]: systemd-ask-password-plymouth.path: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped target Paths.
سبتمبر 09 22:36:21 amor systemd[1]: acpid.path: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped ACPI Events Check.
سبتمبر 09 22:36:21 amor systemd[1]: cups.path: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped CUPS Scheduler.
سبتمبر 09 22:36:21 amor systemd[1]: resolvconf-pull-resolved.path: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped resolvconf-pull-resolved.path.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped target Slices.
سبتمبر 09 22:36:21 amor systemd[1]: Removed slice User and Session Slice.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped target Sockets.
سبتمبر 09 22:36:21 amor systemd[1]: acpid.socket: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Closed ACPID Listen Socket.
سبتمبر 09 22:36:21 amor systemd[1]: avahi-daemon.socket: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
سبتمبر 09 22:36:21 amor systemd[1]: cups.socket: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Closed CUPS Scheduler.
سبتمبر 09 22:36:21 amor systemd[1]: dbus.socket: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Closed D-Bus System Message Bus Socket.
سبتمبر 09 22:36:21 amor systemd[1]: snapd.socket: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Closed Socket activation for snappy daemon.
سبتمبر 09 22:36:21 amor systemd[1]: syslog.socket: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Closed Syslog Socket.
سبتمبر 09 22:36:21 amor systemd[1]: uuidd.socket: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Closed UUID daemon activation socket.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped target System Initialization.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped target Local Encrypted Volumes.
سبتمبر 09 22:36:21 amor systemd[1]: systemd-ask-password-wall.path: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
سبتمبر 09 22:36:21 amor systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:intel_backlight...
سبتمبر 09 22:36:21 amor systemd[1]: systemd-sysctl.service: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped Apply Kernel Variables.
سبتمبر 09 22:36:21 amor systemd[1]: systemd-modules-load.service: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped Load Kernel Modules.
سبتمبر 09 22:36:21 amor systemd[1]: Stopping Network Time Synchronization...
سبتمبر 09 22:36:21 amor systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
سبتمبر 09 22:36:21 amor systemd[1]: systemd-update-utmp.service: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
سبتمبر 09 22:36:21 amor systemd[1]: systemd-backlight@backlight:intel_backlight.service: Succeeded.
سبتمبر 09 22:36:21 amor systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight.
سبتمبر 09 22:36:21 amor systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
سبتمبر 09 22:36:22 amor systemd[1]: systemd-timesyncd.service: Succeeded.
سبتمبر 09 22:36:22 amor systemd[1]: Stopped Network Time Synchronization.
سبتمبر 09 22:36:23 amor systemd[1]: systemd-resolved.service: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Stopped Network Name Resolution.
سبتمبر 09 22:36:23 amor systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Stopped Create Volatile Files and Directories.
سبتمبر 09 22:36:23 amor systemd[1]: Stopped target Local File Systems.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting /run/snapd/ns/snap-store.mnt...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for core18, revision 1880...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for core18, revision 1885...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for gnome-3-34-1804, revision 33...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for gnome-3-34-1804, revision 36...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for gtk-common-themes, revision 1506...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for kate, revision 64...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for kde-frameworks-5-qt-5-14-core18, revision 4...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for kdenlive, revision 24...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for octave, revision 29...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for octave, revision 30...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for snap-store, revision 454...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for snap-store, revision 467...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for snapd, revision 8542...
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting Mount unit for snapd, revision 8790...
سبتمبر 09 22:36:23 amor systemd[1]: run-snapd-ns-snap\x2dstore.mnt.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted /run/snapd/ns/snap-store.mnt.
سبتمبر 09 22:36:23 amor systemd[1]: snap-core18-1885.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for core18, revision 1885.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounting /run/snapd/ns...
سبتمبر 09 22:36:23 amor systemd[1]: run-snapd-ns.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted /run/snapd/ns.
سبتمبر 09 22:36:23 amor systemd[1]: Stopped target Swap.
سبتمبر 09 22:36:23 amor systemd[1]: Deactivating swap /swapfile...
سبتمبر 09 22:36:23 amor systemd[1]: snap-gnome\x2d3\x2d34\x2d1804-33.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for gnome-3-34-1804, revision 33.
سبتمبر 09 22:36:23 amor systemd[1]: snap-gtk\x2dcommon\x2dthemes-1506.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for gtk-common-themes, revision 1506.
سبتمبر 09 22:36:23 amor systemd[1]: snap-kate-64.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for kate, revision 64.
سبتمبر 09 22:36:23 amor systemd[1]: snap-core18-1880.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for core18, revision 1880.
سبتمبر 09 22:36:23 amor systemd[1]: snap-gnome\x2d3\x2d34\x2d1804-36.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for gnome-3-34-1804, revision 36.
سبتمبر 09 22:36:23 amor systemd[1]: snap-kde\x2dframeworks\x2d5\x2dqt\x2d5\x2d14\x2dcore18-4.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for kde-frameworks-5-qt-5-14-core18, revision 4.
سبتمبر 09 22:36:23 amor systemd[1]: snap-kdenlive-24.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for kdenlive, revision 24.
سبتمبر 09 22:36:23 amor systemd[1]: snap-octave-29.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for octave, revision 29.
سبتمبر 09 22:36:23 amor systemd[1]: snap-octave-30.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for octave, revision 30.
سبتمبر 09 22:36:23 amor systemd[1]: snap-snap\x2dstore-454.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for snap-store, revision 454.
سبتمبر 09 22:36:23 amor systemd[1]: snap-snap\x2dstore-467.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for snap-store, revision 467.
سبتمبر 09 22:36:23 amor systemd[1]: snap-snapd-8542.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for snapd, revision 8542.
سبتمبر 09 22:36:23 amor systemd[1]: snap-snapd-8790.mount: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Unmounted Mount unit for snapd, revision 8790.
سبتمبر 09 22:36:23 amor systemd[1]: Stopped target Local File Systems (Pre).
سبتمبر 09 22:36:23 amor systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Stopped Create Static Device Nodes in /dev.
سبتمبر 09 22:36:23 amor systemd[1]: systemd-sysusers.service: Succeeded.
سبتمبر 09 22:36:23 amor systemd[1]: Stopped Create System Users.
سبتمبر 09 22:36:24 amor systemd[1]: swapfile.swap: Succeeded.
سبتمبر 09 22:36:24 amor systemd[1]: Deactivated swap /swapfile.
سبتمبر 09 22:36:24 amor systemd[1]: Reached target Unmount All Filesystems.
سبتمبر 09 22:36:24 amor systemd[1]: systemd-remount-fs.service: Succeeded.
سبتمبر 09 22:36:24 amor systemd[1]: Stopped Remount Root and Kernel File Systems.
سبتمبر 09 22:36:24 amor systemd[1]: Reached target Shutdown.
سبتمبر 09 22:36:24 amor systemd[1]: Reached target Final Step.
سبتمبر 09 22:36:24 amor systemd[1]: systemd-poweroff.service: Succeeded.
سبتمبر 09 22:36:24 amor systemd[1]: Finished Power-Off.
سبتمبر 09 22:36:24 amor systemd[1]: Reached target Power-Off.
سبتمبر 09 22:36:24 amor systemd[1]: Shutting down.
سبتمبر 09 22:36:24 amor systemd-shutdown[1]: Syncing filesystems and block devices.
سبتمبر 09 22:36:25 amor systemd-shutdown[1]: Sending SIGTERM to remaining processes...
سبتمبر 09 22:36:25 amor systemd-journald[240]: Journal stopped
amor@amor:~$ 

Hors ligne

#24 Le 10/09/2020, à 16:13

geole

Re : Ubuntu 20.04 lts ne s'éteint pas

amor@amor:~$ journalctl    --no-pager --since  "2020-09-09 12:15" --until  "2020-09-09 23:45"  | tail -1000
سبتمب .....
سبتمبر 09 22:36:24 amor systemd[1]: Stopped Remount Root and Kernel File Systems.
سبتمبر 09 22:36:24 amor systemd[1]: Reached target Shutdown.
سبتمبر 09 22:36:24 amor systemd[1]: Reached target Final Step.
سبتمبر 09 22:36:24 amor systemd[1]: systemd-poweroff.service: Succeeded.
سبتمبر 09 22:36:24 amor systemd[1]: Finished Power-Off.
سبتمبر 09 22:36:24 amor systemd[1]: Reached target Power-Off.
سبتمبر 09 22:36:24 amor systemd[1]: Shutting down.
سبتمبر 09 22:36:24 amor systemd-shutdown[1]: Syncing filesystems and block devices.
سبتمبر 09 22:36:25 amor systemd-shutdown[1]: Sending SIGTERM to remaining processes...
سبتمبر 09 22:36:25 amor systemd-journald[240]: Journal stopped

En théorie, tout semble normal.
Probablement  que certains process ne veulent pas se terminer malgré le signal "Sending SIGTERM to remaining processes"
Je ne sais pas  les identifier.

En ligne

#25 Le 10/09/2020, à 17:29

Sisiphe

Re : Ubuntu 20.04 lts ne s'éteint pas

Bonsoir
Bien que pas  je ne soits pas un grand toubab, celà m'est parfois arrivé, de ne pas pouvoir éteindre!
Sous contrôle des "manitou", je lance , sur le terminal, la commande
shutdown.
Et pour moi, ça a toujours fonctionné! arret au bout de2 ou 3 minutes, pendant lesquelles tu peux annuler la commande, par cancel.La commande par un appui long sur la touche arrêt , qui est obligatoire sur tout apppareil à programme, est je pense plus "brutale"

Hors ligne