On Tue, Aug 11, 2026 at 06:19:20PM +0200, Yves-Alexis Perez wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Tue, 2026-08-11 at 17:56 +0200, Agustin Martin wrote: > > Hey Agustin, thanks for the feedback. > > > > > As a consequence, locking the screen (ctrl-alt-del): > > > > > > Does this mean you're using light-locker? Please migrate to xfce4- > > > screensaver, > > > it's been a while since we transitioned to it. It seems there might be > > > incompatibilities between lightdm 1.33 and light-locker, which is > > > unmaintained > > > so they're unlikely to be fixed. > > > > > > Then check against the switch-to-greeter command? > > > > Using xscreensaver here. > > Sorry, I'm unsure I'm following you and your workflow: you're using > xscreensaver as locker so, for what exactly are you using dm-tool switch-to- > greeter? You mention it in the context of locking the screen, but that's not > really how xscreensaver does it, so I'm confused, could you elaborate?
Franck mentioned that using light-locker failed in a way he associates to this problem. I just added that this does not happen with xscreensaver. I use dm-tool switch-to-greeter to open and have some simultaneous sessions for different users (I usually use it through menu options, not explicitely. Only put it explicitely to show this problem). > > I can lock and unlock screen properly with it > > (also while this switch problem is happening). Anyway, if this can cause > > data loss with light-locker, should not this bug's severity be raised? > > light-locker will be removed from Debian as soon as possible. Even with a package about to be dropped, data loss is not a good thing. > > Also, note that I need to restart lightdm.service (or reboot) after upgrade > > for problem to start appearing (and similar after downgrade for problem to > > disappear). > > Did you do a full reboot at some point after upgrading or are you still on the > same boot? Can you try to do the 1.33 upgrade, reboot and see if that still > happens? Sure, I first noticed the problem after a full reboot with 1.33 installed. Later noticed that restarting ligthdm service also shows it. Done some reboots later in both directions after changes. Regards, -- Agustin
