Debian 10 (buster) - gdm3只有在"systemctl重新启动gdm3“之后才会启动。

Question

我目前已经设置了Debian拉伸的新安装。我跟着关于如何更新到Debian测试(buster)的说明，一切都很顺利。我重启了系统，一切都很顺利。

接下来，我在这个系统上为我的系统编译了一个4.19.5内核：

$ git clone -b kernel_4.19.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
$ cd linux
$ cp /boot/config-`uname -r` .config
$ yes "" | make oldconfig
$ make -j64 bzImage modules
$ sudo make modules_install install
$ sudo update-grub
$ sudo reboot

编译内核完美无缺，内核启动，一切都很好。除了gdm3：它不会在启动内核之后启动。

因此，我再次启动了Debian 4.18.y内核，但仍然只有一个黑屏幕。再次启动4.19.5，我从这台机器上的另一台机器启动，并发布了systemctl restart gdm3。2-4秒后，我的显示器上会弹出登录屏幕，一切正常工作。

再一次重启系统。没有登录屏幕，只有黑色。再次，ssh在机器上，重新启动gdm3，一切都会弹出。

当gdm3无法启动时，我一直在钻研它的日志。

Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) config/udev: removing GPU device /sys/devices/pci0000:40/0000:40:03.1/0000:43:00.0/drm/card0 /dev/dri/card0
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: xf86: remove device 0 /sys/devices/pci0000:40/0000:40:03.1/0000:43:00.0/drm/card0
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: failed to find screen to remove
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: dbus-daemon[1264]: [session uid=103 pid=1264] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=103 pid=1176 comm="/usr/lib/gdm3/gdm-x-session gnome-session --autost")
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: dbus-daemon[1264]: [session uid=103 pid=1264] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Nov 28 12:11:46 bamdevsrv gdm3[1102]: GdmManager: trying to register new display
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: Unable to register display with display manager
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (**) Option "fd" "25"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) event1  - Power Button: device removed
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (**) Option "fd" "28"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) event0  - Power Button: device removed
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (**) Option "fd" "29"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) event16 - Cherry USB keyboard: device removed
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (**) Option "fd" "30"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) event18 - Cherry USB keyboard System Control: device removed
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (**) Option "fd" "31"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) event19 - Cherry USB keyboard Consumer Control: device removed
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (**) Option "fd" "32"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) event20 - PixArt Cherry USB Optical Mouse: device removed
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) UnloadModule: "libinput"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) systemd-logind: releasing fd for 13:84
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) UnloadModule: "libinput"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) systemd-logind: releasing fd for 13:83
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) UnloadModule: "libinput"
Nov 28 12:11:46 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) systemd-logind: releasing fd for 13:82
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) UnloadModule: "libinput"
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) systemd-logind: releasing fd for 13:80
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) UnloadModule: "libinput"
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) systemd-logind: releasing fd for 13:64
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) UnloadModule: "libinput"
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) systemd-logind: releasing fd for 13:65
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) RADEON(0): RADEONCloseScreen
Nov 28 12:11:47 bamdevsrv /usr/lib/gdm3/gdm-x-session[1176]: (II) Server terminated successfully (0). Closing log file.
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSession: Emitting 'session-exited' signal with exit code '70'
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSession: stopping conversation gdm-launch-environment
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSessionWorkerJob: Stopping job pid:1170
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmCommon: sending signal 15 to process 1170
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmDisplay: Greeter exited: 70
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmLocalDisplayFactory: display status changed: 4
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmDisplay: finish display
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmDisplayStore: Unreffing display: 0x55da450b4350
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmDisplay: Disposing display
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmCommon: sending signal 15 to process -1176
Nov 28 12:11:47 bamdevsrv gdm3[1102]: Child process -1176 was already dead.
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSession: Closing session
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSession: Stopping all conversations
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSessionWorkerJob: Stopping job pid:1170
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmCommon: sending signal 15 to process 1170
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSessionWorkerJob: Waiting on process 1170
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmCommon: process (pid:1170) done (status:0)
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSessionWorkerJob: SessionWorkerJob died
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSession: Disposing session
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSession: Closing session
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmSession: Stopping all conversations
Nov 28 12:11:47 bamdevsrv gdm3[1102]: GdmDisplay: Finalizing display: /org/gnome/DisplayManager/Displays/94395949597520

最后，它被困在了Finalizing display。在我发出重新启动后，日志看起来几乎相同，但它在Finalizing display之后继续进行，还有很多其他输出。

Nov 28 13:59:16 bamdevsrv gdm3[1129]: GdmSession: Disposing session
Nov 28 13:59:16 bamdevsrv gdm3[1129]: GdmSession: Closing session
Nov 28 13:59:16 bamdevsrv gdm3[1129]: GdmSession: Stopping all conversations
Nov 28 13:59:16 bamdevsrv gdm3[1129]: GdmDisplay: Finalizing display: /org/gnome/DisplayManager/Displays/93976516326224
Nov 28 14:02:49 bamdevsrv gdm3[1129]: GDM finished, cleaning up...
Nov 28 14:02:49 bamdevsrv gdm3[1129]: GdmDisplayStore: Clearing display store
Nov 28 14:02:49 bamdevsrv gdm3[2448]: Enabling debugging
Nov 28 14:02:49 bamdevsrv gdm3[2448]: Changing user:group to Debian-gdm:Debian-gdm
Nov 28 14:02:49 bamdevsrv gdm3[2448]: Successfully connected to D-Bus
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmManager: GDM starting to manage displays
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GLib: posix_spawn avoided (fd close requested)
Nov 28 14:02:49 bamdevsrv gdm3[2448]: Could not ping plymouth: Failed to execute child process “/bin/plymouth” (No such file or directory)
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmLocalDisplayFactory: enumerating seats from logind
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmLocalDisplayFactory: wayland login display for seat seat0 requested
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmLocalDisplayFactory: Adding display on seat seat0
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: id: (null)
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: seat id: (null)
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: session class: greeter
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: initial: no
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: allow timed login: yes
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: local: yes
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: session type: wayland
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: seat id: seat0
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: initial: yes
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplayStore: Adding display /org/gnome/DisplayManager/Displays/94188358636112 to store
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: Managing display: /org/gnome/DisplayManager/Displays/94188358636112
Nov 28 14:02:49 bamdevsrv gdm3[2448]: GdmDisplay: Preparing display: /org/gnome/DisplayManager/Displays/94188358636112

gdm3在引导时是如何损坏的，但在我重新启动它之后就不会了？

编辑：目前我正在运行一个解决方案。但这不过是一次丑陋的黑客攻击，即新系统服务：

[Unit]
After=gdm3.service

[Service]
ExecStartPre=/bin/sleep 15
ExecStart=/bin/systemctl restart gdm3

[Install]
WantedBy=multi-user.target

Answer 1

wiki.debian.org DebianTesting有关于gdm的具体说明。

apt-get --reinstall install gdm3
apt-get --reinstall install gnome
apt-get --reinstall install gnome-shell

dpkg-reconfigure gdm3

Answer 2

经历了一个类似的问题，而gnome在启动时就开始了。

dmesg (对我而言)在侏儒壳中显示了一个节段断层，这是由于weyland造成的。

使用"WaylandEnable=false“更新/etc/gdm3 3/中的gnome消除了分段错误，并导致gnome启动(启动时)，而无需再发出任何问题。

https://askubuntu.com/questions/1059091/gnome-shell-error-showing-in-dmesg