Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
I've just updated all packages from unstable, including glibc and the problem is solved. So, it might have been the one you've described. Thanks for your help and your work! Cheers, Bastian Am 08.07.23 um 11:32 schrieb Simon McVittie: On Thu, 06 Jul 2023 at 09:50:57 +0100, Simon McVittie wrote: On Wed, 05 Jul 2023 at 22:44:40 +0200, Bastian Venthur wrote: #5 0x7f134cbe97ce g_utf8_collate_key (libglib-2.0.so.0 + 0x8a7ce) #6 0x7f134ccee180 e_source_set_display_name (libedataserver-1.2.so.27 + 0x57180) Well, this is messed up - something is setting the display name of an ESource (a calendar or address book or something similar) to a value that is, apparently, so long that allocating memory for its collation key (a version that has been modified to sort in the correct locale-sensitive order) will fail. I wonder whether this is the same root cause as #1040452: glibc (>= 2.37-2) sometimes generating corrupted locale archives? That might explain why g_utf8_collate_key() would get nonsense results. Please try with glibc (>= 2.37-5) which fixes that bug, and maybe this one too. smcv -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
On Thu, 06 Jul 2023 at 09:50:57 +0100, Simon McVittie wrote: > On Wed, 05 Jul 2023 at 22:44:40 +0200, Bastian Venthur wrote: > > #5 0x7f134cbe97ce g_utf8_collate_key (libglib-2.0.so.0 > > + 0x8a7ce) > > #6 0x7f134ccee180 e_source_set_display_name > > (libedataserver-1.2.so.27 + 0x57180) > > Well, this is messed up - something is setting the display name of an > ESource (a calendar or address book or something similar) to a value that > is, apparently, so long that allocating memory for its collation key (a > version that has been modified to sort in the correct locale-sensitive > order) will fail. I wonder whether this is the same root cause as #1040452: glibc (>= 2.37-2) sometimes generating corrupted locale archives? That might explain why g_utf8_collate_key() would get nonsense results. Please try with glibc (>= 2.37-5) which fixes that bug, and maybe this one too. smcv
Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
On Wed, 05 Jul 2023 at 22:44:40 +0200, Bastian Venthur wrote: > Start-Date: 2023-07-03 09:06:13 Unfortunately this upgrade was sufficiently large that it's hard to spot which package might have triggered this. Nothing jumps out at me as a particularly likely trigger. Maaaybe glibc, or the evolution family of packages? > Here are also two outputs of coredumpctl that appeared after a crash: > Stack trace of thread 3960: ... > #3 0x7f134cbbb0ff g_log (libglib-2.0.so.0 + 0x5c0ff) > #4 0x7f134cbb96a2 g_malloc (libglib-2.0.so.0 + 0x5a6a2) > #5 0x7f134cbe97ce g_utf8_collate_key (libglib-2.0.so.0 > + 0x8a7ce) > #6 0x7f134ccee180 e_source_set_display_name > (libedataserver-1.2.so.27 + 0x57180) Well, this is messed up - something is setting the display name of an ESource (a calendar or address book or something similar) to a value that is, apparently, so long that allocating memory for its collation key (a version that has been modified to sort in the correct locale-sensitive order) will fail. A display name that large is clearly absurd, so all I can think of is that the `result_len` or `xfrm_len` in g_utf8_collate_key() (depending which code path we're in) might have been calculated incorrectly? > Stack trace of thread 3710: ... > #7 0x7f539ead20ff g_log (libglib-2.0.so.0 + 0x5c0ff) > #8 0x7f539ead06a2 g_malloc (libglib-2.0.so.0 + 0x5a6a2) > #9 0x7f539eb007ce g_utf8_collate_key (libglib-2.0.so.0 > + 0x8a7ce) > #10 0x7f539ee22d65 _shell_app_set_app_info > (libgnome-shell.so + 0x22d65) Similarly this one is setting up a collation key for the name of an app (a fairly short string like "LibreOffice Writer", and again reaching OOM as a result of that is clearly absurd. Please could you try retracing these with debug symbols installed? You can either install appropriate -dbgsym packages manually, or export DEBUGINFOD_URLS=https://debuginfod.debian.net coredumpctl gdb $PID to download appropriate symbols automatically and cache them in ~/.cache/debuginfod_client. See https://wiki.debian.org/HowToGetABacktrace for more details. If you're setting this up manually, we would want to see debug symbols for at least GLib (libglib2.0-0-dbgsym) and glibc (libc6-dbg), preferably also gnome-shell-dbgsym and libedataserver-1.2-27-dbgsym. Thanks, smcv
Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
[Apologies for sending this twice, my original mail did not make it to the bug tracker.] Hi Simon, here's the additional info you've asked for. The excerpt from history.log for the software I've installed on the day the system broke, and two outputs of coredumlpctl: Start-Date: 2023-07-03 09:06:13 Requested-By: venthur (1000) Install: libavtp0:amd64 (0.2.0-1+b1, automatic), libheif-plugin-libde265:amd64 (1.16.2-1, automatic), libheif-plugin-aomdec:amd64 (1.16.2-1, automatic), libheif-plugin-x265:amd64 (1.16.2-1, automatic), libheif-plugin-aomenc:amd64 (1.16.2-1, automatic), libsframe1:amd64 (2.40.50.20230630-1, automatic), libheif-plugin-dav1d:amd64 (1.16.2-1, automatic) Upgrade: libsynctex2:amd64 (2022.20220321.62855-6, 2022.20220321.62855-7), openjdk-11-jre:amd64 (11.0.19+7-1, 11.0.20~7-1), libedata-book-1.2-27:amd64 (3.48.3-1, 3.48.4-1), libebook-1.2-21:amd64 (3.48.3-1, 3.48.4-1), libyajl2:amd64 (2.1.0-3, 2.1.0-3.1), libgomp1:amd64 (13.1.0-6, 13.1.0-7), libecal-2.0-2:amd64 (3.48.3-1, 3.48.4-1), libedataserver-1.2-27:amd64 (3.48.3-1, 3.48.4-1), udev:amd64 (253-4, 253.5-1), evolution-data-server:amd64 (3.48.3-1, 3.48.4-1), openjdk-11-jre-headless:amd64 (11.0.19+7-1, 11.0.20~7-1), g++-12:amd64 (12.3.0-4, 12.3.0-5), gstreamer1.0-plugins-ugly:amd64 (1.22.3-2, 1.22.4-1), gcc-12:amd64 (12.3.0-4, 12.3.0-5), libctf-nobfd0:amd64 (2.40.50.20230625-1, 2.40.50.20230630-1), libtsan2:amd64 (13.1.0-6, 13.1.0-7), libnss-myhostname:amd64 (253-4, 253.5-1), libtexluajit2:amd64 (2022.20220321.62855-6, 2022.20220321.62855-7), libtexlua53-5:amd64 (2022.20220321.62855-6, 2022.20220321.62855-7), evolution-data-server-common:amd64 (3.48.3-1, 3.48.4-1), texlive-binaries:amd64 (2022.20220321.62855-6, 2022.20220321.62855-7), systemd-timesyncd:amd64 (253-4, 253.5-1), libtinfo6:amd64 (6.4-4, 6.4+20230625-1), libtinfo6:i386 (6.4-4, 6.4+20230625-1), libtasn1-6:amd64 (4.19.0-2, 4.19.0-3), gir1.2-gstreamer-1.0:amd64 (1.22.3-2, 1.22.4-1), libsrt1.5-gnutls:amd64 (1.5.1-1, 1.5.2-1), libpam-systemd:amd64 (253-4, 253.5-1), libdebuginfod-common:amd64 (0.188-2.1, 0.189-3), openjdk-17-jre:amd64 (17.0.8~6-2, 17.0.8~6-3), libheif1:amd64 (1.15.1-1, 1.16.2-1), locate:amd64 (4.9.0-4, 4.9.0-5), libkpathsea6:amd64 (2022.20220321.62855-6, 2022.20220321.62855-7), libbinutils:amd64 (2.40.50.20230625-1, 2.40.50.20230630-1), i2c-tools:amd64 (4.3-2+b3, 4.3-3), libgfortran5:amd64 (13.1.0-6, 13.1.0-7), libsystemd0:amd64 (253-4, 253.5-1), libi2c0:amd64 (4.3-2+b3, 4.3-3), binutils-x86-64-linux-gnu:amd64 (2.40.50.20230625-1, 2.40.50.20230630-1), libnss-systemd:amd64 (253-4, 253.5-1), evolution-plugins:amd64 (3.48.3-1, 3.48.4-1), debianutils:amd64 (5.7-0.4, 5.7-0.5), libjsoncpp25:amd64 (1.9.5-4, 1.9.5-5), libevolution:amd64 (3.48.3-1, 3.48.4-1), libgegl-common:amd64 (1:0.4.44-3, 1:0.4.46-1), libdebuginfod1:amd64 (0.188-2.1, 0.189-3), libcc1-0:amd64 (13.1.0-6, 13.1.0-7), python3-pyparsing:amd64 (3.0.9-1, 3.1.0-1), libgegl-0.4-0:amd64 (1:0.4.44-3, 1:0.4.46-1), libcamel-1.2-64:amd64 (3.48.3-1, 3.48.4-1), libedataserverui4-1.0-0:amd64 (3.48.3-1, 3.48.4-1), gcc-9-base:amd64 (9.5.0-3, 9.5.0-3+b1), systemd:amd64 (253-4, 253.5-1), libudev1:amd64 (253-4, 253.5-1), libudev1:i386 (253-4, 253.5-1), systemd-dev:amd64 (253-4, 253.5-1), libptexenc1:amd64 (2022.20220321.62855-6, 2022.20220321.62855-7), libebook-contacts-1.2-4:amd64 (3.48.3-1, 3.48.4-1), libc6:amd64 (2.36-9, 2.37-3), libc6:i386 (2.36-9, 2.37-3), locales:amd64 (2.36-9, 2.37-3), libasan8:amd64 (13.1.0-6, 13.1.0-7), libedataserverui-1.2-4:amd64 (3.48.3-1, 3.48.4-1), libgstreamer-plugins-bad1.0-0:amd64 (1.22.3-2, 1.22.4-1), evolution-plugin-pstimport:amd64 (3.48.3-1, 3.48.4-1), libctf0:amd64 (2.40.50.20230625-1, 2.40.50.20230630-1), ncurses-base:amd64 (6.4-4, 6.4+20230625-1), evolution-plugin-bogofilter:amd64 (3.48.3-1, 3.48.4-1), findutils:amd64 (4.9.0-4, 4.9.0-5), evolution:amd64 (3.48.3-1, 3.48.4-1), libgstreamer1.0-0:amd64 (1.22.3-2, 1.22.4-1), cpp-12:amd64 (12.3.0-4, 12.3.0-5), binutils-common:amd64 (2.40.50.20230625-1, 2.40.50.20230630-1), python3-dotenv-cli:amd64 (3.1.1-1, 3.2.0-1), libitm1:amd64 (13.1.0-6, 13.1.0-7), python3-protobuf:amd64 (3.21.12-3, 3.21.12-5), gnome-pkg-tools:amd64 (0.22.7, 0.22.9), libc-dev-bin:amd64 (2.36-9, 2.37-3), python3-exceptiongroup:amd64 (1.1.0-1, 1.1.1-1), postgresql-client-common:amd64 (248, 252), libc-l10n:amd64 (2.36-9, 2.37-3), gir1.2-gst-plugins-bad-1.0:amd64 (1.22.3-2, 1.22.4-1), libc-bin:amd64 (2.36-9, 2.37-3), libsystemd-shared:amd64 (253-4, 253.5-1), libopenmpt0:amd64 (0.7.1-1, 0.7.2-1), libc-devtools:amd64 (2.36-9, 2.37-3), libedata-cal-2.0-2:amd64 (3.48.3-1, 3.48.4-1), libgprofng0:amd64 (2.40.50.20230625-1, 2.40.50.20230630-1), postgresql-client:amd64 (15+248, 15+252), libc6-dbg:amd64 (2.36-9, 2.37-3), libc6-dev:amd64 (2.36-9, 2.37-3), libksba8:amd64 (1.6.3-2, 1.6.4-2), libquadmath0:amd64 (13.1.0-6, 13.1.0-7), libprotobuf32:amd64 (3.21.12-3, 3.21.12-5), systemd-sysv:amd64 (253-4, 253.5-1),
Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
Hi Simon, thank you for the fast reply! Am 04.07.23 um 16:21 schrieb Simon McVittie: On Tue, 04 Jul 2023 at 08:55:38 +0200, Bastian Venthur wrote: Jul 03 16:48:14 fiona gnome-shell[2112]: ../../../glib/gmem.c:136: failed to allocate 51540049304 bytes Jul 03 16:48:14 fiona kernel: __vm_enough_memory: pid: 2112, comm: gnome-shell, not enough memory for the allocation I think this is the key thing here: some upgraded package has caused gnome-shell to try (and fail) to allocate 51G of RAM at once. The rest of what you quoted is just fallout from this. Agreed. Since there was no upgrade in Gnome recently, I suspect that one of the dependencies got an upgrade. I do vaguely remember evolution, systemd and libc6 being the biggest updates today. Please check /var/log/apt for recent upgrades. Mesa is another possibility, and if you have any GNOME Shell extensions installed/enabled, so are those. I don´t have any shell extensions enabled. It would be useful to know whether a different user account on the same system shows the same issue (create a new one with adduser from a text-mode login if necessary) - that would narrow down whether this is triggered by some user-specific setting or whether it's a system-wide issue. gnome-shell is clearly not *completely* unusable on your system, because you say gdm3 is working, and the gdm3 UI is just gnome-shell in a special mode - but that special mode turns off a lot of code paths, including the whole application chooser, which seems to be involved in the crash. Done. I've created a new user and tried to login, with the same results. If you can get a core dump/backtrace from the crash (the syslog entries that you quoted include a Javascript-level backtrace, but not a C-level one) then that would probably also be useful information. Installing system-coredump and using `coredumpctl gdb` is usually the easiest way to get that, especially for components larger than a single application. I can try that, do you have a link with some tutorial on how to do that? Cheers, Bastian -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
Control: reassign -1 gnome-shell 43.6-1 Control: retitle -1 gnome-shell: fails to start on login: failed to allocate 51540049304 bytes Control: tags -1 + trixie sid moreinfo On Tue, 04 Jul 2023 at 08:55:38 +0200, Bastian Venthur wrote: > Jul 03 16:48:14 fiona gnome-shell[2112]: ../../../glib/gmem.c:136: failed to > allocate 51540049304 bytes > Jul 03 16:48:14 fiona kernel: __vm_enough_memory: pid: 2112, comm: > gnome-shell, not enough memory for the allocation I think this is the key thing here: some upgraded package has caused gnome-shell to try (and fail) to allocate 51G of RAM at once. The rest of what you quoted is just fallout from this. > Since there was no upgrade in Gnome recently, I suspect that one of the > dependencies got an upgrade. I do vaguely remember evolution, systemd and > libc6 > being the biggest updates today. Please check /var/log/apt for recent upgrades. Mesa is another possibility, and if you have any GNOME Shell extensions installed/enabled, so are those. It would be useful to know whether a different user account on the same system shows the same issue (create a new one with adduser from a text-mode login if necessary) - that would narrow down whether this is triggered by some user-specific setting or whether it's a system-wide issue. gnome-shell is clearly not *completely* unusable on your system, because you say gdm3 is working, and the gdm3 UI is just gnome-shell in a special mode - but that special mode turns off a lot of code paths, including the whole application chooser, which seems to be involved in the crash. If you can get a core dump/backtrace from the crash (the syslog entries that you quoted include a Javascript-level backtrace, but not a C-level one) then that would probably also be useful information. Installing system-coredump and using `coredumpctl gdb` is usually the easiest way to get that, especially for components larger than a single application. smcv
Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
Package: gnome Version: 1:43+1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: vent...@debian.org Dear Maintainer, since yesterday, Gnome fails to start and falls back to GDM3 when I try to login. I cannot start gnome on wayland nor xorg anymore. Gnome classic fails as well. Falling back to the terminal and trying `startx` does also not start gnome either. Installing something else (MATE) helps. Since there was no upgrade in Gnome recently, I suspect that one of the dependencies got an upgrade. I do vaguely remember evolution, systemd and libc6 being the biggest updates today. Here's some output of journalctl that looks suspicious. Maybe it helps you: Jul 03 16:48:14 fiona dbus-daemon[1894]: [session uid=1000 pid=1894] Activating service name='org.gnome.ScreenSaver' requested by ':1.63' (uid=1000 pid=2485 comm="/usr/libexec/gsd-usb-pr> Jul 03 16:48:14 fiona dbus-daemon[1894]: [session uid=1000 pid=1894] Successfully activated service 'org.freedesktop.portal.IBus' Jul 03 16:48:14 fiona gnome-software-service.desktop[2490]: Unable to acquire bus name 'org.gnome.Software' Jul 03 16:48:14 fiona gnome-shell[2112]: ../../../glib/gmem.c:136: failed to allocate 51540049304 bytes Jul 03 16:48:14 fiona gnome-shell[2112]: == Stack trace for context 0x557fe8d747b0 == Jul 03 16:48:14 fiona gnome-shell[2112]: #0 557fe9756f10 i resource:///org/gnome/shell/ui/appDisplay.js:2124 (20b9b5e92b50 @ 110) Jul 03 16:48:14 fiona gnome-shell[2112]: #1 7ffd1218ef90 I self-hosted:164 (3bea9db8c380 @ 272) Jul 03 16:48:14 fiona gnome-shell[2112]: #2 557fe9756e78 i resource:///org/gnome/shell/ui/appDisplay.js:2138 (20b9b5e92b00 @ 147) Jul 03 16:48:14 fiona gnome-shell[2112]: #3 557fe9756de8 i resource:///org/gnome/shell/ui/appDisplay.js:2229 (20b9b5e92dd0 @ 21) Jul 03 16:48:14 fiona gnome-shell[2112]: #4 557fe9756d38 i resource:///org/gnome/shell/ui/appDisplay.js:2106 (20b9b5e92a60 @ 325) Jul 03 16:48:14 fiona gnome-shell[2112]: #5 557fe9756c98 i resource:///org/gnome/shell/ui/appDisplay.js:490 (20b9b5e90ba0 @ 27) Jul 03 16:48:14 fiona gnome-shell[2112]: #6 557fe9756bf8 i resource:///org/gnome/shell/ui/appDisplay.js:2081 (20b9b5e92fb0 @ 27) Jul 03 16:48:14 fiona gnome-shell[2112]: #7 557fe9756b40 i resource:///org/gnome/shell/ui/appDisplay.js:2329 (20b9b5e93060 @ 336) Jul 03 16:48:14 fiona gnome-shell[2112]: #8 557fe9756aa0 i resource:///org/gnome/shell/ui/appDisplay.js:1844 (20b9b5e92970 @ 27) Jul 03 16:48:14 fiona gnome-shell[2112]: #9 557fe9756a00 i resource:///org/gnome/shell/ui/appDisplay.js:2305 (20b9b5e93600 @ 27) Jul 03 16:48:14 fiona gnome-shell[2112]: #10 557fe9756958 i resource:///org/gnome/shell/ui/appDisplay.js:1504 (20b9b5e915b0 @ 115) Jul 03 16:48:14 fiona gnome-shell[2112]: #11 7ffd12191b10 I self-hosted:164 (3bea9db8c380 @ 272) Jul 03 16:48:14 fiona gnome-shell[2112]: #12 557fe97568b8 i resource:///org/gnome/shell/ui/appDisplay.js:1500 (20b9b5e914c0 @ 226) Jul 03 16:48:14 fiona gnome-shell[2112]: #13 557fe9756808 i resource:///org/gnome/shell/ui/appDisplay.js:1067 (20b9b5e904c0 @ 88) Jul 03 16:48:14 fiona gnome-shell[2112]: #14 557fe9756778 i resource:///org/gnome/shell/ui/appDisplay.js:1374 (20b9b5e91100 @ 44) Jul 03 16:48:14 fiona gnome-shell[2112]: #15 557fe97566f8 i resource:///org/gnome/shell/ui/appDisplay.js:638 (20b9b5e8f920 @ 12) Jul 03 16:48:14 fiona gnome-shell[2112]: #16 7ffd12192880 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (3bea9dba0790 @ 433) Jul 03 16:48:14 fiona gnome-shell[2112]: #17 557fe9756670 i resource:///org/gnome/shell/ui/appFavorites.js:75 (20b9b5e94d80 @ 35) Jul 03 16:48:14 fiona gnome-shell[2112]: #18 557fe97565c0 i resource:///org/gnome/shell/misc/parentalControlsManager.js:95 (20b9b5e95510 @ 590) Jul 03 16:48:14 fiona gnome-shell[2112]: #19 557fe9756528 i self-hosted:1429 (1caa8ee391f0 @ 30) Jul 03 16:48:14 fiona gnome-shell[2112]: #20 7ffd12193f70 b self-hosted:632 (1caa8eeb2e70 @ 15) Jul 03 16:48:14 fiona kernel: __vm_enough_memory: pid: 2112, comm: gnome-shell, not enough memory for the allocation Jul 03 16:48:14 fiona kernel: __vm_enough_memory: pid: 2112, comm: gnome-shell, not enough memory for the allocation Jul 03 16:48:14 fiona kernel: __vm_enough_memory: pid: 2112, comm: gnome-shell, not enough memory for the allocation Jul 03 16:48:14 fiona kernel: __vm_enough_memory: pid: 2112, comm: gnome-shell, not enough memory for the allocation Jul 03 16:48:14 fiona gsd-keyboard[2442]: Cannot open display: Jul 03 16:48:14 fiona gsd-power[2452]: Cannot open display: Jul 03 16:48:14 fiona gnome-software[2477]: cannot open display: :0 Jul 03 16:48:14 fiona gsd-media-keys[2445]: Cannot open display: Jul 03 16:48:14 fiona gsd-color[2433]: Cannot open display: Jul 03 16:48:14 fiona gsd-wacom[2491]: Cannot open display: Jul 03 16:48:14 fiona systemd[1854]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=5/TRAP Jul
