On 2026-03-07 17:17:20 +0100, Vincent Lefevre wrote: > On 2026-03-07 07:53:31 +0100, Andreas Metzler wrote: > > Plus possibly XDG_SESSION_TYPE. The heuristics are a little bit strange > > If I unset XDG_SESSION_TYPE (which is "x11" here), the problem > disappears in the case where DISPLAY is unset, i.e. [...]
FYI, it is pam_systemd that sets the XDG_SESSION_TYPE environment variable (assuming something else does not set it, but that would be undocumented, and "grep -r XDG_SESSION_TYPE /etc" outputs nothing): the pam_systemd(8) man page says: The following environment variables are read by the module and may be used by the PAM service to pass metadata to the module. If these variables are not set when the PAM module is invoked but can be determined otherwise they are set by the module, so that these variables are initialized for the session and applications if known at all. $XDG_SESSION_TYPE [...] I'm wondering why you did not get an abort like me. But after ssh with X11 forwarding, $XDG_SESSION_TYPE is set to "tty" instead of "x11"[*], so that this changes the behavior. [*] I've just reported https://github.com/systemd/systemd/issues/40992 -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
