# Lightdm ne se lance pas

**URL:** <https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742>\
**Category:** Support Debian\
**Created:** [Septembre 1, 2020, 9:25 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742 "2020-09-01T09:25:20Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Almtesh](https://www.debian-fr.org/user_avatar/www.debian-fr.org/almtesh/32/10312_2.png) [@Almtesh](https://www.debian-fr.org/u/Almtesh)\
**Post date:** [Septembre 1, 2020, 9:25 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742/1 "2020-09-01T09:25:20Z")

</div>

Bonjour,

J’ai actuellement un nouveau PC portable avec lequel je rencontre un problème lors du démarrage de lightdm.

J’ai commencé par tenter de le démarrer à la main avec la commande `systemctl start lightdm`, mais ça n’a rien fait du tout.  
Ensuite, j’ai voulu savoir ce qu’il se passait, j’ai donc lancé `systemctl status lightdm` :

```nohighlight
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-01 11:14:55 CEST; 49s ago
     Docs: man:lightdm(1)
  Process: 1895 ExecStartPre=/bin/sh -c ["$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm"] (code=exited, status=0/SUCCESS)
  Process: 1897 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
 Main PID: 1897 (code=exited, status=1/FAILURE)

sept. 01 11:14:55 PC336 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
sept. 01 11:14:55 PC336 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
sept. 01 11:14:55 PC336 systemd[1]: Stopped Light Display Manager.
sept. 01 11:14:55 PC336 systemd[1]: lightdm.service: Start request repeated too quickly.
sept. 01 11:14:55 PC336 systemd[1]: lightdm.service: Failed with result 'exit-code'.
sept. 01 11:14:55 PC336 systemd[1]: Failed to start Light Display Manager.
sept. 01 11:14:55 PC336 systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
sept. 01 11:14:55 PC336 systemd[1]: lightdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.

```

Pour info, le contenu du fichier `/etc/X11/default-display-manager` :

```nohighlight
/usr/sbin/lightdm

```

J’ai donc continué en lançant la commande à la main (`/usr/sbin/lightdm`), mais n’ayant aucun retour, j’ai ajouté du débug (`/usr/sbin/lightdm -d`) :

```nohighlight
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=1929
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.00s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+0.00s] DEBUG: Using VT 7
[+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.00s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.00s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.00s] DEBUG: XServer 0: Launching X Server
[+0.00s] DEBUG: Launching process 1934: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.00s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.00s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.01s] DEBUG: Process 1934 exited with return value 1
[+0.01s] DEBUG: XServer 0: X server stopped
[+0.01s] DEBUG: Releasing VT 7
[+0.01s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.01s] DEBUG: Seat seat0: Display server stopped
[+0.01s] DEBUG: Seat seat0: Stopping session
[+0.01s] DEBUG: Seat seat0: Session stopped
[+0.01s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.01s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.01s] DEBUG: Seat seat0: Stopping
[+0.01s] DEBUG: Seat seat0: Stopped
[+0.01s] DEBUG: Required seat has stopped
[+0.01s] DEBUG: Stopping display manager
[+0.01s] DEBUG: Display manager stopped
[+0.01s] DEBUG: Stopping daemon
[+0.02s] DEBUG: Exiting with return value 1

```

J’ai donc compris que c’était le lancement de X qui posait soucis, j’ai donc continué en lançant X à la main pour voir (`/usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch`) :

```nohighlight

X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
Current Operating System: Linux PC336 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64 root=UUID=cb78b371-c5f0-4d34-b78f-82aa057fb6f8 ro quiet nomodeset
Build Date: 05 March 2019 08:11:12PM
xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
Current version of pixman: 0.36.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 1 11:20:36 2020
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.

```

Voici le fichier `/var/log/Xorg.0.log` :

```nohighlight
[1147.529] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[1147.529] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[1147.529] Current Operating System: Linux PC336 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64
[1147.529] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64 root=UUID=cb78b371-c5f0-4d34-b78f-82aa057fb6f8 ro quiet nomodeset
[1147.529] Build Date: 05 March 2019 08:11:12PM
[1147.529] xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
[1147.529] Current version of pixman: 0.36.0
[1147.529] Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[1147.529] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[1147.529] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 1 11:20:36 2020
[1147.529] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[1147.530] (==) No Layout section. Using the first Screen section.
[1147.530] (==) No screen section available. Using defaults.
[1147.530] (**) |-->Screen "Default Screen Section" (0)
[1147.530] (**) | |-->Monitor "<default monitor>"
[1147.530] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[1147.530] (==) Automatically adding devices
[1147.530] (==) Automatically enabling devices
[1147.530] (==) Automatically adding GPU devices
[1147.530] (==) Max clients allowed: 256, resource mask: 0x1fffff
[1147.530] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[1147.530] Entry deleted from font path.
[1147.530] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/75dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        /usr/share/fonts/X11/75dpi,
        built-ins
[1147.530] (==) ModulePath set to "/usr/lib/xorg/modules"
[1147.530] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[1147.530] (II) Loader magic: 0x5557bc5bbe20
[1147.530] (II) Module ABI versions:
[1147.530] X.Org ANSI C Emulation: 0.4
[1147.530] X.Org Video Driver: 24.0
[1147.530] X.Org XInput driver : 24.1
[1147.530] X.Org Server Extension : 10.0
[1147.531] (++) using VT number 7

[1147.531] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[1147.533] (--) PCI:*(0@0:2:0) 8086:9b41:1558:8686 rev 2, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
[1147.533] (II) LoadModule: "glx"
[1147.533] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[1147.534] (II) Module glx: vendor="X.Org Foundation"
[1147.534] compiled for 1.20.4, module version = 1.0.0
[1147.534] ABI class: X.Org Server Extension, version 10.0
[1147.534] (==) Matched modesetting as autoconfigured driver 0
[1147.534] (==) Matched fbdev as autoconfigured driver 1
[1147.534] (==) Matched vesa as autoconfigured driver 2
[1147.534] (==) Assigned the driver to the xf86ConfigLayout
[1147.534] (II) LoadModule: "modesetting"
[1147.534] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[1147.534] (II) Module modesetting: vendor="X.Org Foundation"
[1147.534] compiled for 1.20.4, module version = 1.20.4
[1147.534] Module class: X.Org Video Driver
[1147.534] ABI class: X.Org Video Driver, version 24.0
[1147.534] (II) LoadModule: "fbdev"
[1147.534] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[1147.535] (II) Module fbdev: vendor="X.Org Foundation"
[1147.535] compiled for 1.20.0, module version = 0.5.0
[1147.535] Module class: X.Org Video Driver
[1147.535] ABI class: X.Org Video Driver, version 24.0
[1147.535] (II) LoadModule: "vesa"
[1147.535] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[1147.535] (II) Module vesa: vendor="X.Org Foundation"
[1147.535] compiled for 1.20.1, module version = 2.4.0
[1147.535] Module class: X.Org Video Driver
[1147.535] ABI class: X.Org Video Driver, version 24.0
[1147.535] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[1147.535] (II) FBDEV: driver for framebuffer: fbdev
[1147.535] (II) VESA: driver for VESA chipsets: vesa
[1147.535] (EE) open /dev/dri/card0: No such file or directory
[1147.535] (WW) Falling back to old probe method for modesetting
[1147.535] (EE) open /dev/dri/card0: No such file or directory
[1147.535] (II) Loading sub module "fbdevhw"
[1147.535] (II) LoadModule: "fbdevhw"
[1147.535] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[1147.535] (II) Module fbdevhw: vendor="X.Org Foundation"
[1147.535] compiled for 1.20.4, module version = 0.0.2
[1147.535] ABI class: X.Org Video Driver, version 24.0
[1147.535] (EE) Unable to find a valid framebuffer device
[1147.535] (WW) Falling back to old probe method for fbdev
[1147.535] (II) Loading sub module "fbdevhw"
[1147.535] (II) LoadModule: "fbdevhw"
[1147.535] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[1147.535] (II) Module fbdevhw: vendor="X.Org Foundation"
[1147.535] compiled for 1.20.4, module version = 0.0.2
[1147.535] ABI class: X.Org Video Driver, version 24.0
[1147.535] (II) FBDEV(2): using default device
[1147.535] (EE) Screen 0 deleted because of no matching config section.
[1147.535] (II) UnloadModule: "modesetting"
[1147.535] (EE) Screen 0 deleted because of no matching config section.
[1147.535] (II) UnloadModule: "fbdev"
[1147.535] (II) UnloadSubModule: "fbdevhw"
[1147.535] (EE) 
Fatal server error:
[1147.536] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[1147.536] (EE) 
[1147.536] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[1147.536] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[1147.536] (EE) 
[1147.541] (EE) Server terminated with error (1). Closing log file.

```

Voici le retour de la commande `lspci` :

```nohighlight
00:00.0 Host bridge: Intel Corporation Device 9b71 (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02)
00:12.0 Signal processing controller: Intel Corporation Device 02f9
00:14.0 USB controller: Intel Corporation Device 02ed
00:14.2 RAM memory: Intel Corporation Device 02ef
00:14.3 Network controller: Intel Corporation Device 02f0
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 02e9
00:16.0 Communication controller: Intel Corporation Device 02e0
00:17.0 SATA controller: Intel Corporation Device 02d3
00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0)
00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device 0284
00:1f.3 Audio device: Intel Corporation Device 02c8
00:1f.4 SMBus: Intel Corporation Device 02a3
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 02a4
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01)
01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

```

Une idée ?

---

<div class="post-metadata">

**Author:** ![littlejohn75](https://www.debian-fr.org/user_avatar/www.debian-fr.org/littlejohn75/32/3840_2.png) [@littlejohn75](https://www.debian-fr.org/u/littlejohn75)\
**Post date:** [Septembre 1, 2020, 2:13 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742/2 "2020-09-01T14:13:53Z")

</div>

> [@Almtesh](#):
>
> j’ai donc continué en lançant X à la main pour voir ( `/usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch` ) :

Wahou !  
Comme vous avez semble-t-il recopié la commande qui lance `X` dans et depuis un environnement complet de bureau `lightdm`+ `dbus`+ …, vous avez donné une foule d’informations pertinentes dans le cadre de cet environnement.  
Vous n’avez pas précisé depuis quelle console vous lancez cette super commande. Si c’est bien `tty1` je vous conseillerais de faire défiler les consoles en utilisant AltFlecheDroite  
Vous choisissez une console, par exemple `tty2` vous vous identifiez si besoin est et vous tapez

```auto
startx

```

Autrement dit, vous revenez aux temps anciens où Linux n’était pas prêt pour le desktop et où on se débrouillait à la mano. De toutes façons, dans la solution toute prête (`lightdm` + `udev` + `dbus` + … ) cela ne fonctionne pas.  
Une fois que vous avez trouvé ce qui cloche, la méthode conseillée pour basculer entre les environnement graphiques et consoles uniquement c’est d’utiliser

```auto
systemctl isolate graphical.target
systemctl isolate multi-user.target

```

C’est nettement plus explicite que les niveaux `rc` de `inittab` et si vous êtes le seul utilisateur vous n’avez même pas besoin d’utiliser `sudo` ou `su`.

Quel modèle de carte graphique dans votre machine ?

Cordialement,  
Regards,  
Mit freundlichen Grüßen,  
مع تحياتي الخالصة

* * *

F. Petitjean  
Ingénieur civil du Génie Maritime.

« On ne perd pas son temps en aiguisant ses outils. »  
Proverbe français

« Moi, lorsque je n’ai rien à dire, je veux qu’on le sache. » (R. Devos)

---

<div class="post-metadata">

**Author:** ![Almtesh](https://www.debian-fr.org/user_avatar/www.debian-fr.org/almtesh/32/10312_2.png) [@Almtesh](https://www.debian-fr.org/u/Almtesh)\
**Post date:** [Septembre 1, 2020, 2:23 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742/3 "2020-09-01T14:23:03Z")

</div>

> [@littlejohn75](#):
>
> Vous n’avez pas précisé depuis quelle console vous lancez cette super commande.

Ah, oui effectivement, j’ai tout fait depuis un accès distant par SSH. C’est plus pratique pour faire des copier-coller.

> [@littlejohn75](#):
>
> Vous choisissez une console, par exemple `tty2` vous vous identifiez si besoin est et vous tapez
> 
> ```auto
> startx
> 
> ```

J’ai la même erreur quand je lance cette commande, que ce soit depuis tty1 ou tty2.

> [@littlejohn75](#):
>
> Une fois que vous avez trouvé ce qui cloche

Heu, mais je n’ai pas trouvé ce qui cloche.

> [@littlejohn75](#):
>
> Quel modèle de carte graphique dans votre machine ?

> [@Almtesh](#):
>
> `00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02)`

Je n’y connais rien, je ne peux pas te dire si c’est bien ça.

---

<div class="post-metadata">

**Author:** ![littlejohn75](https://www.debian-fr.org/user_avatar/www.debian-fr.org/littlejohn75/32/3840_2.png) [@littlejohn75](https://www.debian-fr.org/u/littlejohn75)\
**Post date:** [Septembre 2, 2020, 8:26 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742/4 "2020-09-02T20:26:49Z")

</div>

> [@Almtesh](#):
>
> Ah, oui effectivement, j’ai tout fait depuis un accès distant par SSH. C’est plus pratique pour faire des copier-coller.

Vous nous aviez caché cette information essentielle. Je suppose que lorsque vous parlez de copier-coller, entre différentes fenêtres de votre poste vous manipulez surtout la sélection PRIMARY (atom XA\_PRIMARY) et le CLIPBOARD offert par un serveur X local (X11 Xorg ou XWayland).  
Dans cet environnement X, vous utilisez un émulateur de terminal (`xterm`, `xfce4-terminal` , ..) et vous vous connectez à la machine distante par SSH en précisant l’option `-X` qui fait transiter ( `X11 forwarding` ) les informations relatives aux événements X par le tunnel SSH.  
Comme l’ordinateur distant est

> [@Almtesh](#):
>
> un nouveau PC portable

je suppose qu’il n’y a pas de problème de bande passante ou de latence.

> [@Almtesh](#):
>
> ```auto
> [1147.531] (++) using VT number 7
> 
> [1147.531] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
> [1147.533] (--) PCI:*(0@0:2:0) 8086:9b41:1558:8686 rev 2, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
> [1147.533] (II) LoadModule: "glx"
> [1147.533] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
> [1147.534] (II) Module glx: vendor="X.Org Foundation"
> [1147.534] compiled for 1.20.4, module version = 1.0.0
> [1147.534] ABI class: X.Org Server Extension, version 10.0
> [1147.534] (==) Matched modesetting as autoconfigured driver 0
> [1147.534] (==) Matched fbdev as autoconfigured driver 1
> [1147.534] (==) Matched vesa as autoconfigured driver 2
> [1147.534] (==) Assigned the driver to the xf86ConfigLayout
> [1147.534] (II) LoadModule: "modesetting"
> [1147.534] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> [1147.534] (II) Module modesetting: vendor="X.Org Foundation"
> [1147.534] compiled for 1.20.4, module version = 1.20.4
> [1147.534] Module class: X.Org Video Driver
> [1147.534] ABI class: X.Org Video Driver, version 24.0
> [1147.534] (II) LoadModule: "fbdev"
> [1147.534] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
> [1147.535] (II) Module fbdev: vendor="X.Org Foundation"
> [1147.535] compiled for 1.20.0, module version = 0.5.0
> [1147.535] Module class: X.Org Video Driver
> [1147.535] ABI class: X.Org Video Driver, version 24.0
> [1147.535] (II) LoadModule: "vesa"
> [1147.535] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
> [1147.535] (II) Module vesa: vendor="X.Org Foundation"
> [1147.535] compiled for 1.20.1, module version = 2.4.0
> [1147.535] Module class: X.Org Video Driver
> [1147.535] ABI class: X.Org Video Driver, version 24.0
> [1147.535] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [1147.535] (II) FBDEV: driver for framebuffer: fbdev
> [1147.535] (II) VESA: driver for VESA chipsets: vesa
> [1147.535] (EE) open /dev/dri/card0: No such file or directory
> [1147.535] (WW) Falling back to old probe method for modesetting
> [1147.535] (EE) open /dev/dri/card0: No such file or directory
> [1147.535] (II) Loading sub module "fbdevhw"
> [1147.535] (II) LoadModule: "fbdevhw"
> [1147.535] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
> [1147.535] (II) Module fbdevhw: vendor="X.Org Foundation"
> [1147.535] compiled for 1.20.4, module version = 0.0.2
> [1147.535] ABI class: X.Org Video Driver, version 24.0
> [1147.535] (EE) Unable to find a valid framebuffer device
> [1147.535] (WW) Falling back to old probe method for fbdev
> [1147.535] (II) Loading sub module "fbdevhw"
> [1147.535] (II) LoadModule: "fbdevhw"
> [1147.535] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
> [1147.535] (II) Module fbdevhw: vendor="X.Org Foundation"
> [1147.535] compiled for 1.20.4, module version = 0.0.2
> [1147.535] ABI class: X.Org Video Driver, version 24.0
> [1147.535] (II) FBDEV(2): using default device
> [1147.535] (EE) Screen 0 deleted because of no matching config section.
> [1147.535] (II) UnloadModule: "modesetting"
> 
> ```

Voyez l’avant dernière ligne : c’est un problème de configuration du serveur X.  
Mais comme sur mon PC un «&nbsp;locate xorg.conf&nbsp;» ne me renvoie que un truc relatif à `xpra` (que je n’ai jamais vraiment utilisé) et donc tout est automatique (pilotes automatiquement chargés et configurés dans des sections de configuration qui se trouvent on ne sait où ), que j’ai

```auto
fp2@debpacha:~$ aptitude search Xserver | grep '^i' | wc                     
     19 196 1485
fp2@debpacha:~$

```

pas moins de 19 paquets `xserver-truc` installés  
j’avoue que conseiller la commande

```auto
sudo dpkg-reconfigure xserver-xorg-video-fbdev

```

c’est vraiment au petit bonheur la chance 🙂 et sans garantie aucune.

Cordialement,  
Regards,  
Mit freundlichen Grüßen,  
مع تحياتي الخالصة

* * *

F. Petitjean  
Ingénieur civil du Génie Maritime.

« Je préfère le vin d’ici à l’au-delà »  
Pierre Dac

---

<div class="post-metadata">

**Author:** ![Almtesh](https://www.debian-fr.org/user_avatar/www.debian-fr.org/almtesh/32/10312_2.png) [@Almtesh](https://www.debian-fr.org/u/Almtesh)\
**Post date:** [Septembre 3, 2020, 6:44 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742/5 "2020-09-03T06:44:08Z")

</div>

> [@littlejohn75](#):
>
> Je suppose que lorsque vous parlez de copier-coller, entre différentes fenêtres de votre poste vous manipulez surtout la sélection PRIMARY (atom XA\_PRIMARY) et le CLIPBOARD offert par un serveur X local (X11 Xorg ou XWayland).

Hein ?

> [@littlejohn75](#):
>
> Dans cet environnement X, vous utilisez un émulateur de terminal ( `xterm` , `xfce4-terminal` , …) et vous vous connectez à la machine distante par SSH en précisant l’option `-X` qui fait transiter ( `X11 forwarding` ) les informations relatives aux événements X par le tunnel SSH.

Non, je ne fais pas de forwarding du serveur X, j’accède à un interpréteur de commande à distance à partir d’un PC qui fonctionne pour faire les manipulations et pouvoir faire des copier-coller des retours de commandes et autres.

> [@littlejohn75](#):
>
> Voyez l’avant dernière ligne : c’est un problème de configuration du serveur X.

Effectivement, j’ai pensé à la configuration du serveur X, mais j’ai deux problèmes avec ça :

- je n’ai jamais rien compris à la configuration du serveur X dans son fichier de configuration
- je n’ai pas de fichier `/etc/X11/xorg.conf`

---

<div class="post-metadata">

**Author:** ![DarkGagan](https://www.debian-fr.org/user_avatar/www.debian-fr.org/darkgagan/32/4093_2.png) [@DarkGagan](https://www.debian-fr.org/u/DarkGagan)\
**Post date:** [Septembre 4, 2020, 10:19 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742/6 "2020-09-04T22:19:15Z")

</div>

Hello,

> [@Almtesh](#):
>
> 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02)

Cela correspond à un Intel UHD Graphics ([CometLake-U GT2 [UHD Graphics] — PCI 8086:9B41 — DeviceHunt](https://devicehunt.com/view/type/pci/vendor/8086/device/9B41)) donc chip graphique intégré au cpu. Les firmwares intel-microcode sont installés?

---

<div class="post-metadata">

**Author:** ![Almtesh](https://www.debian-fr.org/user_avatar/www.debian-fr.org/almtesh/32/10312_2.png) [@Almtesh](https://www.debian-fr.org/u/Almtesh)\
**Post date:** [Septembre 5, 2020, 5:06 UTC](https://www.debian-fr.org/t/lightdm-ne-se-lance-pas/82742/7 "2020-09-05T05:06:11Z")

</div>

Bon, j’ai trouvé un moyen de faire fonctionner cet ordinateur. Attention, c’est un peu moche.  
J’ai installé Debian 9 pour constater que lightdm se lance bien sous cette version, mais je n’avais pas la carte wifi fonctionnelle. Donc, pour que tout fonctionne, j’ai installé Debian 9 avec le noyau du backport de Debian 10 (celui de Debian 11, en fait), et là, tout fonctionne.  
Il faudrait ouvrir un bug pour signaler la régression, mais mes rapports de bug n’ont jamais abouti à rien du tout, quand on y répondait. Alors, je laisse tomber.

Merci pour vos réponse.