[From nobody Fri Oct 23 18:01:04 2026
Received: (at submit) by bugs.debian.org; 23 Oct 2026 13:45:54 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-15.0 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,HAS_PACKAGE,SPF_HELO_PASS,SPF_PASS autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 28; hammy, 118; neutral, 41; spammy,
 4. spammytokens:0.997-1--H*RU:sk:mail1.p,
 0.997-1--Hx-spam-relays-external:sk:mail1.p, 0.997-1--H*r:sk:mail1.p,
 0.940-+--H*r:bugs.debian.org hammytokens:0.000-+--systemctl,
 0.000-+--gdm3, 0.000-+--pam_unix, 0.000-+--tty2, 0.000-+--gnomeshell
Return-path: <leo@unglaub.at>
Received: from mail1.polarlight-labs.com ([37.27.17.14]:24055)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <leo@unglaub.at>) id 1xKFal-00ENst-01
 for submit@bugs.debian.org; Fri, 23 Oct 2026 13:45:54 +0000
Message-ID: <e72352ab-a22c-470f-b9a2-f439dd10fc08@unglaub.at>
Date: Fri, 23 Oct 2026 15:42:32 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB, de-AT
To: submit@bugs.debian.org
From: Leo Unglaub <leo@unglaub.at>
Subject: gnome-shell: GNOME fails to start after Sid update ("Session never
 registered")
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: delayed 424 seconds by postgrey-1.37 at buxtehude;
 Fri, 23 Oct 2026 13:45:54 UTC
Delivered-To: submit@bugs.debian.org

Package: gnome-shell
Severity: important

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
]