Hey,

since a recent system update (approx. 2 days ago) on Debian Sid, the
GNOME desktop environment fails to start. The screen remains black, but
switching to a virtual terminal (e.g., TTY2) works normally.

When attempting to restart the display manager, GDM3 fails immediately.

Here are the relevant details from `systemctl status gdm3` and the
system journal:
--- Logs & Error Output ---
gdm3[1621]: GdmDisplay: Session never registered, failing
gdm3[1621]: Child process -2395 was already dead.
gdm-launch-environment[2494]: pam_unix(gdm-launch-environment:session):
session opened for us...
gdm-launch-environment[2494]: gkr-pam: couldn't unlock the login keyring.
gdm3[1621]: GdmDisplay: Session never registered, failing
gdm-local-display-factory: maximum number of display failures reached.
Giving up.
-------------------------

System Information:
- Distribution: Debian Sid (unstable)
- Graphics Hardware: AMD Radeon / Ryzen Graphics (amdgpu driver)
- Latest packages

Is this something on my system or are you noticing this to? My concern
is this moving into testing with this bug.

Greetings

Have you installed updates from your virtual terminal? There was a
critical bug that landed Tuesday and was fixed Wednesday where the apt
package gweather-locations was not installed but should have been.

Thank you,
Jeremy Bícha

Hey,

yes sir, i did. The system is on the latest version available. I have
multiple mirrors included on my system, all of them are up to date.

The issue still exists. There is the message, that the gnome-shell and
gnome-shell-common package are hold back, maybe this is related? But i
am not doing anything special with my packages here, no special pinning,
nothing. Just tested it in a clean VM without any motifications, gdm3
currenrly does not start.

Greetings

sudo apt dist-upgrade

Pay attention to what it suggests removing. Do you have GNOME Shell
extension packages installed? If so, some of the packaged extensions
might not be compatible with this version of GNOME Shell yet.

Thank you,
Jeremy Bícha

Hey,

yeah, i already did that. Also in the fresh installation i did to
reproduce this.

There is no shell extension that i can see that would cause this.

But i am starting to think that this is related to another issue that i
am tracking down that just causes this as a side effect. I just talked
to another debian user who does not have this issue. So i asume its on
my end.

You can close this for now, i report back if i find anything else.
Thanks for your input!

You could try to explicitly install gnome-shell:
sudo apt install gnome-shell

Thank you,
Jeremy Bícha