![升级到 19.04 后 gnome-session 启动失败](https://linux22.com/image/911815/%E5%8D%87%E7%BA%A7%E5%88%B0%2019.04%20%E5%90%8E%20gnome-session%20%E5%90%AF%E5%8A%A8%E5%A4%B1%E8%B4%A5.png)
从 18.10 升级到 19.04。启动时 GDM 正常启动,输入密码后无法启动 GNOME。它返回到 GDM
这是一台 Nvidia Optimus 笔记本电脑。我从 USB 运行 Dingo 并将其安装到测试分区中。它识别所有内容(使用 nouveau 而不是 Nvidia blob)。
日志显示:
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Unrecoverable failure in required component org.gnome.Shell.desktop
WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
CRITICAL: We failed, but the fail whale is dead. Sorry...
使用 Xorg 和 Wayland 的两个 mutter 会话都以同样的方式失败。旧的 metacity“GNOME Flashback”启动正常(但 indicator-datetime-service 会占用所有 CPU 和内存,而且如果我将其关闭,它也不会停止重生)。
尝试使用 lightdm 代替 GDM。同样失败。
尝试重新安装 gnome-session 包。没有任何变化。
通过 journalct -xe 获取的所有日志。
欢迎任何有关如何调试此东西的建议。
后来,我意识到我无意中启用了“建议的”存储库(在我的 cosmic 安装中)。将 gnome-shell(“3.32.1-1ubuntu1~19.04.1”降级为“3.32.0+git20190410-1ubuntu1”)、mutter 和其他软件包(使用固定优先级),但问题仍然完全相同。
这是日志的较长摘录(现在使用 Budgie):
may 27 02:04:56 hostname gnome-shell[3334]: JS ERROR: TypeError: b.location.get_timezone(...) is null
_clocksChanged/<@resource:///org/gnome/shell/ui/dateMenu.js:127:20
_clocksChanged@resource:///org/gnome/shell/ui/dateMenu.js:125:9
_connectHandler@resource:///org/gnome/shell/misc/util.js:472:9
watchSetting@resource:///org/gnome/shell/misc/util.js:463:9
WorldClocksSection@resource:///org/gnome/shell/ui/dateMenu.js:102:9
_init@resource:///org/gnome/shell/ui/dateMenu.js:530:28
_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1116:25
_updateBox@resource:///org/gnome/shell/ui/panel.js:1127:29
_updatePanel@resource:///org/gnome/shell/ui/panel.js:1072:9
_init@resource:///org/gnome/shell/ui/panel.js:873:9
_initializeUI@resource:///org/gnome/shell/ui/main.js:178:13
start@resource:///org/gnome/shell/ui/main.js:127:5
@<main>:1:31
may 27 02:04:56 hostname gnome-shell[3334]: Execution of main.js threw exception: Script <main> threw an exception
may 27 02:04:56 hostname gnome-shell[3334]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroyin
may 27 02:04:56 hostname org.gnome.Shell.desktop[3334]: == Stack trace for context 0x55852aa8a230 ==
may 27 02:04:56 hostname gnome-shell[3334]: The offending signal was destroy on Gjs_DateMenuButton 0x55852bdbd810.
may 27 02:04:56 hostname gnome-session[3131]: gnome-session-binary[3131]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
may 27 02:04:56 hostname gnome-session[3131]: gnome-session-binary[3131]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
may 27 02:04:56 hostname gnome-session-binary[3131]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
may 27 02:04:56 hostname gnome-session-binary[3131]: Unrecoverable failure in required component org.gnome.Shell.desktop
may 27 02:04:56 hostname gnome-session[3131]: gnome-session-binary[3131]: CRITICAL: We failed, but the fail whale is dead. Sorry....
may 27 02:04:56 hostname gnome-session-binary[3131]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
may 27 02:04:56 hostname gnome-session-binary[3131]: CRITICAL: We failed, but the fail whale is dead. Sorry....
may 27 02:04:56 hostname gdm-x-session[3117]: session exited with status 1
may 27 02:04:56 hostname at-spi-bus-launcher[3250]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
may 27 02:04:56 hostname at-spi-bus-launcher[3250]: after 21 requests (21 known processed) with 0 events remaining.
may 27 02:04:56 hostname ibus-daemon[3309]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the d
may 27 02:04:56 hostname /usr/lib/gdm3/gdm-x-session[3117]: (**) Option "fd" "26"
--纳乔克布
答案1
现在已修复!
我尝试禁用所有扩展,包括用户扩展,但无济于事。问题出在显示世界时钟的内置扩展上。我不得不从 CLI [1] 重置我的世界时钟位置。
据称该问题已经修复(相同的 GitLab 问题)因此将来不会再发生这种情况。
—— 伊卡雷拉