Your message dated Mon, 17 Mar 2025 19:33:43 -0400
with message-id
<CAD+GYvxBKjQnSBDF5xL0+9da06naeyK6k+BO2t1y1Z=my4m...@mail.gmail.com>
and subject line Re: Bug#1099884: mutter: Failed upgrade from gnome 47 to 48:
crash at gdm3 startup: white screen
has caused the Debian Bug report #1099884,
regarding mutter: Failed upgrade from gnome 47 to 48: crash at gdm3 startup:
white screen
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1099884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099884
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutter-common
Version: 48~beta-7
Severity: important
File: mutter
Dear Maintainer,
I experienced a bad upgrade on my HP Elitebook 8440p with Intel Core i5 M540
CPU (Intel Iron Lake graphics). As I switched to gdm3_48~beta-1 via apt and
rebooted I ended up in a white screen with a sad computer-monitor saying
something like: "Startup failed, couldn't fix it, get an administrator…"
journalctl spits out these lines:
Mär 09 00:08:35 [device] gnome-session[4694]:
gnome-session-binary[4694]: WARNING: Could not check if unit
[email protected] is active: Fehler beim Aufruf von
StartServiceB>
Mär 09 00:08:35 [device] gnome-session-binary[4694]: WARNING: Could not
check if unit [email protected] is active: Fehler
beim Aufruf von StartServiceByName für org.freedes>
Mär 09 00:08:35 [device] gnome-shell[4719]: Running GNOME Shell (using
mutter 48.beta) as a X11 window and compositing manager
Mär 09 00:08:36 [device] /usr/libexec/gdm-x-session[4678]: (II)
modeset(0): EDID vendor "CMO", prod id 5219
Mär 09 00:08:36 [device] /usr/libexec/gdm-x-session[4678]: (II)
modeset(0): Printing DDC gathered Modelines:
Mär 09 00:08:36 [device] /usr/libexec/gdm-x-session[4678]: (II)
modeset(0): Modeline "1366x768"x0.0 69.30 1366 1382 1416 1480 768 770
776 780 +hsync -vsync (46.8 kHz eP)
Mär 09 00:08:36 [device] /usr/libexec/gdm-x-session[4678]: (II)
modeset(0): Modeline "1366x768"x0.0 46.27 1366 1382 1416 1480 768 770
776 780 +hsync -vsync (31.3 kHz e)
Mär 09 00:08:36 [device] org.gnome.Shell.desktop[4719]: Failed to setup:
Unable to create suitable GL context
Mär 09 00:08:36 [device] gnome-session[4694]:
gnome-session-binary[4694]: WARNING: App 'org.gnome.Shell.desktop'
exited with code 1
Mär 09 00:08:36 [device] gnome-session-binary[4694]: WARNING: App
'org.gnome.Shell.desktop' exited with code 1
Mär 09 00:08:36 [device] gnome-shell[4735]: Running GNOME Shell (using
mutter 48.beta) as a X11 window and compositing manager
(Always thought, gdm3 starts up using wayland but here we go…
I guess, the point is:
"Unable to create suitable GL context")
So I pulled back the following packages to a version below 48~beta-1…
gdm3_47.0-4
libgdm1_47.0-4
gir1.2-gdm-1.0_47.0-4
gnome-shell_47.3-1
gir1.2-mutter-15_47.4-1
libmutter-15-0_47.4-1
xdg-desktop-portal-gnome_47.2-2
mutter-common_47.4-1
mutter-common-bin_47.4-1
…and I got a working gnome-desktop, again!
Didn't know, which package to report (gdm3 and gnome-shell may be a wiser
choice)… Hope this is okay…!
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mutter-common depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-5
mutter-common recommends no packages.
mutter-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 48~rc-4
--- End Message ---
