# Plantages sous Gnome

**URL:** <https://www.debian-fr.org/t/plantages-sous-gnome/77229>\
**Category:** Support Debian\
**Created:** [Juillet 18, 2018, 11:59 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229 "2018-07-18T11:59:21Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Le\_Barde](https://www.debian-fr.org/user_avatar/www.debian-fr.org/le_barde/32/4330_2.png) [@Le\_Barde](https://www.debian-fr.org/u/Le_Barde)\
**Post date:** [Juillet 18, 2018, 11:59 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/1 "2018-07-18T11:59:21Z")

</div>

Bonjour,

Depuis que je suis passé intégralement sous Buster, j’ai des plantages réguliers. Ça se traduit par des freezes de l’écran, et le son qui fait une boucle.

J’ai regardé syslog, et voici un extrait de ce qui se passe entre le moment où ça plante et le début du reboot :

```auto
Jul 18 13:42:00 white-hat minissdpd[1042]: peer 192.168.0.254:1900 is not from a LAN
Jul 18 13:42:00 white-hat minissdpd[1042]: peer 192.168.0.254:1900 is not from a LAN
Jul 18 13:42:00 white-hat minissdpd[1042]: peer 192.168.0.254:1900 is not from a LAN
Jul 18 13:42:00 white-hat minissdpd[1042]: peer 192.168.0.254:1900 is not from a LAN
Jul 18 13:42:00 white-hat minissdpd[1042]: peer 192.168.0.254:1900 is not from a LAN
Jul 18 13:42:14 white-hat minissdpd[1042]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
Jul 18 13:45:56 white-hat dbus-daemon[1649]: [session uid=1000 pid=1649] Activating service name='org.gnome.Nautilus' requested by ':1.10' (uid=1000 pid=1682 comm="/usr/bin/gnome-shell ")
Jul 18 13:45:56 white-hat dbus-daemon[1649]: [session uid=1000 pid=1649] Successfully activated service 'org.gnome.Nautilus'
Jul 18 13:45:56 white-hat org.gnome.Nautilus[1649]: Initializing nautilus-dropbox 2015.10.28
Jul 18 13:45:56 white-hat dbus-daemon[830]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.107' (uid=1000 pid=2994 comm="/usr/bin/nautilus --gapplication-service ")
Jul 18 13:45:56 white-hat systemd[1]: Starting Hostname Service...
Jul 18 13:45:57 white-hat dbus-daemon[830]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jul 18 13:45:57 white-hat systemd[1]: Started Hostname Service.
Jul 18 13:46:04 white-hat zeitgeist-datah[1929]: zeitgeist-datahub.vala:207: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
Jul 18 13:46:04 white-hat dbus-daemon[1649]: [session uid=1000 pid=1649] Activating via systemd: service name='org.gnome.evince.Daemon' unit='evince.service' requested by ':1.90' (uid=1000 pid=3018 comm="evince /home/adrien/Documents/Archives/2018/voitur")
Jul 18 13:46:04 white-hat systemd[1630]: Starting Evince document viewer...
Jul 18 13:46:04 white-hat dbus-daemon[1649]: [session uid=1000 pid=1649] Successfully activated service 'org.gnome.evince.Daemon'
Jul 18 13:46:04 white-hat systemd[1630]: Started Evince document viewer.
Jul 18 13:47:34 white-hat org.gnome.Shell.desktop[1682]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 2d (keycode 11).
Jul 18 13:44:01 white-hat kernel: [0.000000] microcode: microcode updated early to revision 0x1f, date = 2018-02-07
Jul 18 13:44:01 white-hat kernel: [0.000000] Linux version 4.16.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22)
Jul 18 13:44:01 white-hat kernel: [0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=UUID=377bd488-6309-4c52-9cf2-aa25c6d3dd65 ro quiet
Jul 18 13:44:01 white-hat kernel: [0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jul 18 13:44:01 white-hat kernel: [0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jul 18 13:44:01 white-hat kernel: [0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jul 18 13:44:01 white-hat kernel: [0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jul 18 13:44:01 white-hat kernel: [0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Jul 18 13:44:01 white-hat kernel: [0.000000] e820: BIOS-provided physical RAM map:
Jul 18 13:44:01 white-hat kernel: [0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Jul 18 13:44:01 white-hat kernel: [0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Jul 18 13:44:01 white-hat kernel: [0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 18 13:44:01 white-hat kernel: [0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable

```

Auriez-vous des idées ?

---

<div class="post-metadata">

**Author:** ![anon93295908](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b782af/32.png) [@anon93295908](https://www.debian-fr.org/u/anon93295908)\
**Post date:** [Juillet 18, 2018, 12:49 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/2 "2018-07-18T12:49:00Z")

</div>

Bonjour,

quel carte graphique as tu ?

---

<div class="post-metadata">

**Author:** ![Le\_Barde](https://www.debian-fr.org/user_avatar/www.debian-fr.org/le_barde/32/4330_2.png) [@Le\_Barde](https://www.debian-fr.org/u/Le_Barde)\
**Post date:** [Juillet 18, 2018, 1:03 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/3 "2018-07-18T13:03:41Z")

</div>

Bonjour @anon93295908, merci de ta réponse !

J’ai le processeur suivant : `Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz`. J’utilise le chipset graphique Intel intégré au processeur, le HD 2500.

---

<div class="post-metadata">

**Author:** ![anon93295908](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b782af/32.png) [@anon93295908](https://www.debian-fr.org/u/anon93295908)\
**Post date:** [Juillet 18, 2018, 2:55 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/4 "2018-07-18T14:55:36Z")

</div>

Quand tu passer intégralement c’est à dire ?

Je vais dire une connerie mais tu peut tester de faire un memtest dessus.

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Juillet 18, 2018, 3:21 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/5 "2018-07-18T15:21:03Z")

</div>

Salut  
_Jul 18 13:44:01 white-hat kernel: [0.000000] Linux version 4.16.0-2-amd64 ([debian-kernel@lists.debian.org](mailto:debian-kernel@lists.debian.org)) (gcc version 7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22)_  
_Jul 18 13:44:01 white-hat kernel: [0.000000] Command line: BOOT\_IMAGE=/vmlinuz-4.16.0-2-amd64 root=UUID=377bd488-6309-4c52-9cf2-aa25c6d3dd65 ro quiet_

As tu conservé le noyau 4.9 et si oui as tu le même problème avec?

je fonctionne comme ça

```auto
root@debian:/# lsb_release --all
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (buster)
Release:	testing
Codename:	buster
root@debian:/# uname -a
Linux debian 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux
root@debian:/#

```

---

<div class="post-metadata">

**Author:** ![Le\_Barde](https://www.debian-fr.org/user_avatar/www.debian-fr.org/le_barde/32/4330_2.png) [@Le\_Barde](https://www.debian-fr.org/u/Le_Barde)\
**Post date:** [Juillet 18, 2018, 10:32 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/6 "2018-07-18T22:32:23Z")

</div>

@anon93295908 je vais essayer de faire un memtest, au cas où… Concernant le passage sous Buster, j’ai eu récemment un problème audio et comme j’avais un système avec des paquets issus de plusieurs versions de Debian, j’ai tout ré-harmonisé en Buster.

@grandtoubab je n’ai pas le noyau 4.9.

```auto
~$ lsb_release --all
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (buster)
Release:	testing
Codename:	buster
~$ uname -a
Linux white-hat 4.16.0-2-amd64 #1 SMP Debian 4.16.16-2 (2018-06-22) x86_64 GNU/Linux

~~~En root :~~~
~# apt remove linux- [tab tab]
linux-base linux-headers-4.16.0-2-amd64 linux-headers-amd64 linux-image-amd64 linux-libc-dev
linux-compiler-gcc-7-x86 linux-headers-4.16.0-2-common linux-image-4.16.0-2-amd64 linux-kbuild-4.16              
root@white-hat:/~# apt install linux [tab tab]
Display all 110 possibilities? (y or n)
linux-base linux-image-4.14.0-3-amd64 linux-image-686-pae-dbg linux-libc-dev-mipsn32r6-cross
linuxbrew-wrapper linux-image-4.15.0-2-amd64 linux-image-amd64 linux-libc-dev-mipsn32r6el-cross
linux-compiler-gcc-7-x86 linux-image-4.15.0-3-amd64 linux-image-amd64-dbg linux-libc-dev-mipsr6-cross
linux-cpupower linux-image-4.16.0-1-amd64 linux-image-cloud-amd64 linux-libc-dev-mipsr6el-cross
linux-doc linux-image-4.16.0-2-686 linux-image-cloud-amd64-dbg linux-libc-dev-powerpc-cross
linux-doc-4.16 linux-image-4.16.0-2-686-dbg linux-image-rt-686-pae linux-libc-dev-powerpcspe-cross
linuxdoc-tools linux-image-4.16.0-2-686-pae linux-image-rt-686-pae-dbg linux-libc-dev-ppc64-cross
linuxdoc-tools-info linux-image-4.16.0-2-686-pae-dbg linux-image-rt-amd64 linux-libc-dev-ppc64el-cross
linuxdoc-tools-latex linux-image-4.16.0-2-amd64 linux-image-rt-amd64-dbg linux-libc-dev-riscv64-cross
linuxdoc-tools-text linux-image-4.16.0-2-amd64-dbg linuxinfo linux-libc-dev-s390x-cross
linux-headers-4.16.0-2-686 linux-image-4.16.0-2-cloud-amd64 linux-kbuild-4.16 linux-libc-dev-sh4-cross
linux-headers-4.16.0-2-686-pae linux-image-4.16.0-2-cloud-amd64-dbg linux-libc-dev linux-libc-dev-sparc64-cross
linux-headers-4.16.0-2-all linux-image-4.16.0-2-rt-686-pae linux-libc-dev-alpha-cross linux-libc-dev-x32-cross
linux-headers-4.16.0-2-all-amd64 linux-image-4.16.0-2-rt-686-pae-dbg linux-libc-dev-amd64-cross linuxlogo
linux-headers-4.16.0-2-all-i386 linux-image-4.16.0-2-rt-amd64 linux-libc-dev-arm64-cross linux-patch-debianlogo
linux-headers-4.16.0-2-amd64 linux-image-4.16.0-2-rt-amd64-dbg linux-libc-dev-armel-cross linux-patch-grsecurity2
linux-headers-4.16.0-2-cloud-amd64 linux-image-4.7.0-1-amd64 linux-libc-dev-armhf-cross linux-perf
linux-headers-4.16.0-2-common linux-image-4.8.0-1-amd64 linux-libc-dev-hppa-cross linux-perf-4.16
linux-headers-4.16.0-2-common-rt linux-image-4.8.0-2-amd64 linux-libc-dev-i386-cross linuxptp
linux-headers-4.16.0-2-rt-686-pae linux-image-4.9.0-1-amd64 linux-libc-dev-m68k-cross linux-show-player
linux-headers-4.16.0-2-rt-amd64 linux-image-4.9.0-2-amd64 linux-libc-dev-mips64-cross linux-source
linux-headers-686 linux-image-4.9.0-3-amd64 linux-libc-dev-mips64el-cross linux-source-4.16
linux-headers-amd64 linux-image-4.9.0-4-amd64 linux-libc-dev-mips64r6-cross linux-support-4.16.0-2
linux-headers-cloud-amd64 linux-image-4.9.0-5-amd64 linux-libc-dev-mips64r6el-cross linux-user-chroot
linux-headers-rt-686-pae linux-image-4.9.0-6-amd64 linux-libc-dev-mips-cross linux-user-chroot-dbg
linux-headers-rt-amd64 linux-image-686 linux-libc-dev-mipsel-cross linuxvnc
linux-igd linux-image-686-dbg linux-libc-dev-mipsn32-cross          
linux-image-3.16.0-4-amd64 linux-image-686-pae linux-libc-dev-mipsn32el-cross        
root@white-hat:/~# apt install linux-image-4.9.0-6-amd64 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Aucune version du paquet linux-image-4.9.0-6-amd64 n'est disponible, mais il existe dans la base
de données. Cela signifie en général que le paquet est manquant, qu'il est devenu obsolète
ou qu'il n'est disponible que sur une autre source

E: Le paquet « linux-image-4.9.0-6-amd64 » n'a pas de version susceptible d'être installée
root@white-hat:/~# apt-cache policy linux-image-4.9.0-6-amd64
linux-image-4.9.0-6-amd64:
  Installé : (aucun)
  Candidat : (aucun)
 Table de version :
     4.9.82-1+deb9u3 -1
        100 /var/lib/dpkg/status
root@white-hat:/~# 

```

---

<div class="post-metadata">

**Author:** ![gilles2](https://www.debian-fr.org/user_avatar/www.debian-fr.org/gilles2/32/7966_2.png) [@gilles2](https://www.debian-fr.org/u/gilles2)\
**Post date:** [Juillet 19, 2018, 7:02 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/7 "2018-07-19T07:02:23Z")

</div>

> [@extrait du syslog](#):
>
> Jul 18 13:46:04 white-hat zeitgeist-datah[1929]: zeitgeist-datahub.vala:207: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required

Je vois déjà cette erreur et comme zeitgeist-datah est buggué quelque soit les versions ( schéma en rose en haut à droite de cette page ) :

> **[\#856555 - zeitgeist-datahub will not stop on logout - Debian Bug report logs](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856555)**

même si peut-être cela n’aurait aucun lien avec ta panne, je serais à ta place je l’enlèverais déjà pour voir.

J’ai :  
`# lsb_release --all`  
`No LSB modules are available.`  
`Distributor ID:	Debian`  
`Description:	Debian GNU/Linux testing (buster)`  
`Release:	testing`  
`Codename:	buster`

et :  
`# uname -a`  
`Linux 4.16.0-2-amd64 #1 SMP Debian 4.16.16-2 (2018-06-22) x86_64 GNU/Linux`  
et gnome et c hez moi cela fonctionne.

> [@Le\_Barde](#):
>
> je suis passé intégralement sous Buster

Quel est ton sources.list ?

D’autre part, je vois que tu traînes du kernel 3.16, il faudrait faire le ménage dans tout cela

> [@Le\_Barde](#):
>
> linux-image-3.16.0-4-amd64

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Juillet 19, 2018, 7:03 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/8 "2018-07-19T07:03:22Z")

</div>

4.9 c’est le noyau de stretch (stable)

```auto
root@debian:/# apt policy linux-image-4.9.0-7-amd64
linux-image-4.9.0-7-amd64:
  Installé : 4.9.110-1
  Candidat : 4.9.110-1
 Table de version :
 *** 4.9.110-1 500
        500 http://deb.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status

```

---

<div class="post-metadata">

**Author:** ![Le\_Barde](https://www.debian-fr.org/user_avatar/www.debian-fr.org/le_barde/32/4330_2.png) [@Le\_Barde](https://www.debian-fr.org/u/Le_Barde)\
**Post date:** [Juillet 19, 2018, 7:43 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/9 "2018-07-19T07:43:05Z")

</div>

Merci à vous deux ! Bon, j’ai retiré `zeitgeist-datahub` et `zeitgeist`. Par contre `zeitgeist-core` dépend du métapaquet `gnome`.

Mon sources.list est des plus simples :

```auto
# Buster
deb http://ftp.fr.debian.org/debian/ buster main contrib non-free

```

1. Alors comment retirer les traces des paquets précédents ?
2. Je rajoute Stretch dans les sources pour essayer le noyau 4.9 ?

---

<div class="post-metadata">

**Author:** ![gilles2](https://www.debian-fr.org/user_avatar/www.debian-fr.org/gilles2/32/7966_2.png) [@gilles2](https://www.debian-fr.org/u/gilles2)\
**Post date:** [Juillet 19, 2018, 8:27 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/10 "2018-07-19T08:27:25Z")

</div>

Justement, il est trop simple à mon avis. Il te faudrait aussi :

`deb http://security.debian.org/debian-security buster/updates main contrib non-free`

`# buster-updates, previously known as 'volatile'`  
`deb http://ftp.de.debian.org/debian/ buster-updates main contrib non-free`

Ensuite :  
`# aptitude update`  
`# aptitude safe-upgrade`  
pour mettre à jour.

Tu peux retirer les traces des paquets précédents de manière simple avec synaptic avec le choix “État” tu auras une ligne “Paquets installés manuellement ou obsolètes” qui tu serviras à afficher les paquets à supprimer et ensuite à les supprimer avec les commandes de synaptic.

Ne pas utiliser le noyau 4.16 est une idée de grandtoubab qui est peut-être justifiée pour son usage particulier, mais qui assez peu partagée. En ce qui me concerne, je ne la partage pas puisque le noyau 4.16 me va comme un gant et je ne pense que cela soit la cause de ta panne, mais plutôt ce que je viens juste d’écrire plus haut.

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Juillet 19, 2018, 9:01 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/11 "2018-07-19T09:01:35Z")

</div>

pour le sources.list concernant Buster j’ai ça

```auto
root@debian:/etc/apt# egrep buster sources.list
deb http://deb.debian.org/debian-security/ buster/updates contrib main non-free
deb http://deb.debian.org/debian/ buster contrib main non-free
deb http://deb.debian.org/debian/ buster-updates contrib main non-free
deb http://deb.debian.org/debian buster-proposed-updates contrib main non-free
root@debian:/etc/apt# 

```

Les gel du bureau c’est très souvent un problème de driver graphique et/ou de noyau  
Il s’agissait simplement d’avoir un point de comparaison

Tu peux aussi verifier que tous les services systemd fonctionnent

```auto
systemctl --failed

```

et voir s’il n’y a pas d’erreur

```auto
journalctl -xb -p err --no-pager

```

---

<div class="post-metadata">

**Author:** ![Le\_Barde](https://www.debian-fr.org/user_avatar/www.debian-fr.org/le_barde/32/4330_2.png) [@Le\_Barde](https://www.debian-fr.org/u/Le_Barde)\
**Post date:** [Juillet 19, 2018, 9:21 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/12 "2018-07-19T09:21:52Z")

</div>

Du coup, j’ai étendu mon sources.list et mis à jour :

```auto
Les paquets suivants seront mis à jour :
  cups-browsed cups-filters cups-filters-core-drivers espeak-ng-data kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools libcupsfilters1 libespeak-ng1
  libfontembed1 libgpgme++2v5 libjs-sphinxdoc libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4
  libkemoticons4 libkfile4 libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkpty4
  libkrosscore4 libktexteditor4 libnepomuk4 libnepomukquery4a libnepomukutils4 libopencv-calib3d3.2 libopencv-contrib3.2 libopencv-core3.2
  libopencv-features2d3.2 libopencv-flann3.2 libopencv-highgui3.2 libopencv-imgcodecs3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-objdetect3.2
  libopencv-photo3.2 libopencv-shape3.2 libopencv-stitching3.2 libopencv-superres3.2 libopencv-video3.2 libopencv-videoio3.2 libopencv-videostab3.2
  libopencv-viz3.2 libplasma3 libsolid4 libthreadweaver4 libwww-perl tor tor-geoipdb
62 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 28,9 Mo dans les archives.
Après cette opération, 818 ko d'espace disque supplémentaires seront utilisés.

```

J’ai retiré comme dit précédemment les `zeitgeist-*`. Je vais rebooter pour voir si c’est stable.  
Comme je pars bientôt en vacances, il est possible qu’il n’y ait pas de problème supplémentaire pour le moment.

```auto
# systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION                 
● configure-printer@usb-002-005.service loaded failed failed Configure Plugged-In Printer

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

# journalctl -xb -p err --no-pager
-- Logs begin at Wed 2018-07-18 15:03:03 CEST, end at Thu 2018-07-19 11:19:15 CEST. --
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 18 15:03:03 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 18 15:03:03 white-hat systemd-udevd[317]: Invalid rule /etc/udev/rules.d/60-brother-libsane-type1.rules:17: unknown key 'SYSFS{idVendor}'
juil. 18 15:03:11 white-hat bluetoothd[766]: Sap driver initialization failed.
juil. 18 15:03:11 white-hat bluetoothd[766]: sap-server: Operation not permitted (1)
juil. 18 15:03:11 white-hat kernel: r8169 0000:03:00.0: firmware: failed to load rtl_nic/rtl8168f-1.fw (-2)
juil. 18 15:03:11 white-hat kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
juil. 18 15:03:12 white-hat /hpfax[993]: [993]: error: Failed to create /var/spool/cups/tmp/.hplip
juil. 18 15:03:13 white-hat minissdpd[1065]: ssdpDiscover: sendto: Cannot assign requested address
juil. 18 15:03:15 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:03:16 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:11:35 white-hat bluetoothd[766]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
juil. 18 15:11:35 white-hat bluetoothd[766]: RFCOMM server failed for :1.88/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: rfcomm_bind: Address already in use (98)
juil. 18 15:20:01 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:26:01 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:32:38 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:40:23 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:43:47 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:51:35 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 15:58:19 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 16:03:16 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 16:07:51 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 16:13:01 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 18 16:18:40 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 00:18:52 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:52 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:18:52 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:52 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:18:52 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:52 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:18:52 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:52 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:18:52 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:52 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:18:52 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:52 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:18:53 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:53 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:18:53 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 00:18:53 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 00:21:48 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 00:28:40 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 00:37:24 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 00:46:34 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 00:51:39 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 00:59:11 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 01:08:10 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 01:12:30 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 01:18:14 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 09:35:14 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:14 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:35:14 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:14 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:35:14 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:14 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:35:14 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:14 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:35:16 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:16 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:35:16 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:16 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:35:18 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:18 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:35:18 white-hat kernel: ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
juil. 19 09:35:18 white-hat kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180105/psparse-550)
juil. 19 09:41:34 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 09:50:32 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 09:59:58 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:03:25 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:13:00 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:19:58 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:24:56 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:32:39 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:37:18 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:46:06 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:55:13 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 10:57:24 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 11:01:46 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 11:06:03 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 11:13:25 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use
juil. 19 11:17:06 white-hat minissdpd[1065]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, ): Address already in use

```

---

<div class="post-metadata">

**Author:** ![Le\_Barde](https://www.debian-fr.org/user_avatar/www.debian-fr.org/le_barde/32/4330_2.png) [@Le\_Barde](https://www.debian-fr.org/u/Le_Barde)\
**Post date:** [Juillet 21, 2018, 6:30 UTC](https://www.debian-fr.org/t/plantages-sous-gnome/77229/13 "2018-07-21T06:30:55Z")

</div>

Pour le moment j’ai fait des mises à jour en étendant mon sources.list, comme vous me l’avez proposé. Il semble que je n’ai plus de plantage. Je vais mettre en résolu pour le moment, et si ça survient de nouveau en septembre je rouvrirai ce fil.

Merci à vous deux pour cette investigation !
