Bug#961132: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

2020-05-21 Thread Vincent Lefevre
Hi,

On 2020-05-21 14:01:04 +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> control: tag -1 unreproducible

Not sure the conditions to reproduce the bug, but to be sure, with
a laptop:

1. Set up a systemd-inhibit lock for handle-lid-switch.

2. Close the lid.

3. Lock the screen with light-locker or log out.

Just guessing, because the systemd log does not mention lid closing
at all for the reason of suspend.

Note that this was in my bug report against systemd:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961124

(merged with this bug).

> On Wed, 2020-05-20 at 19:35 +0200, Vincent Lefevre wrote:
> > 
> > Both locking and logging out trigger the lightdm login prompt,
> > so that I suppose that this is the same issue, and it was not
> > light-locker that was suspending the system, but lightdm.
> 
> Hi,
> 
> this is weird indeed, but I'm not going to investigate an nvidia
> binary issue. For what it's worth, I do have a system with an nvidia
> card and the binary driver, running lightdm, light-locker and Xfce,
> and I don't have that behavior at all (running Buster).

Well, Michael Biebl says that's light-locker / lightdm that suspends
the system:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961124#22

(note: I don't use XFCE, just lightdm + light-locker at that time).
There is no reason to do that under any condition, and the code that
does that needs to be removed.

Now, if there isn't any such code, I would tend to think that
Michael Biebl is wrong, because I also get a suspend issue
without lightdm / light-locker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961146

and it seems to be related to systemd-inhibit lock vs which
login session is associated with the display, in particular
when switching from X to a VT:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961146#15

Since the use of lightdm does something similar, this could explain
the bug.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#961132: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

2020-05-21 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

control: tag -1 unreproducible

On Wed, 2020-05-20 at 19:35 +0200, Vincent Lefevre wrote:
> 
> Both locking and logging out trigger the lightdm login prompt,
> so that I suppose that this is the same issue, and it was not
> light-locker that was suspending the system, but lightdm.

Hi,

this is weird indeed, but I'm not going to investigate an nvidia binary issue.
For what it's worth, I do have a system with an nvidia card and the binary
driver, running lightdm, light-locker and Xfce, and I don't have that behavior
at all (running Buster).

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl7GbYAACgkQ3rYcyPpX
RFtKhwgAn7axFp/6uKnAgAMrpB7Z7IV33zp4l8KZXiR/AB6yc3WJbvzPNp+rmzVC
3jUfnKiG5iNSLmKu+AewnA9/jKV5MM60Fo+ZMm52DLocZ2lfUS5YghJ9BJM2ucgJ
CMagLBeMe9Q22W2q7g42CAmmmKfiDtkl6J+6xOKWDO1JZ2EkWE15TiavbPtEuZSs
pdKKauqZhAI/FjwfWSFhBN10rlReucN+MFFoYDWZ4X7j3MM1cKRR3LFGQOORrl+E
SDZ8BMz2LIbYthUSqYwNIW+8gCdIH1TjT8uqV9zZh0HTHQeeJjW8iRlpwC9MWWTr
Gd7NOmx90Ziuj53Xbpcyayk5AmEX0g==
=Sq/d
-END PGP SIGNATURE-



Processed: Re: Bug#961132: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

2020-05-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 unreproducible
Bug #961132 [lightdm] lightdm: with the nvidia driver, lightdm suspends the 
system when locking or logging out
Bug #961124 [lightdm] lightdm: with the nvidia driver, lightdm suspends the 
system when locking or logging out
Added tag(s) unreproducible.
Added tag(s) unreproducible.

-- 
961124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961124
961132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#961132: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

2020-05-20 Thread Vincent Lefevre
Control: forcemerge 961132 961124
Control: reassign 961132 lightdm 1.26.0-7
Control: retitle -1 lightdm: with the nvidia driver, lightdm suspends the 
system when locking or logging out

On 2020-05-20 15:58:11 +0200, Vincent Lefevre wrote:
> Package: light-locker
> Version: 1.8.0-3
> Severity: important
> 
> With the nvidia driver, light-locker suspends the system when locking.
> In the journalctl logs, I get a line like
> 
> May 20 09:16:43 zira systemd-logind[785]: Suspending...
> 
> and according to the systemd maintainer, this is light-locker's fault.
> 
> This happens at lock time, thus immediately with --no-late-locking,
> and at the time of screensaver deactivation with --late-locking.
> 
> Note: Until yesterday, IIRC, using --no-late-locking (at least) did
> not trigger a suspend, but the screen was unblanked after a few seconds
> (it remained black, but the DPMS state was no longer off, which defeats
> the purpose of the screensaver nowadays). So this may be related to
> some conditions.
> 
> Moreover, after the resume, this puts the system in a bad state, and
> the X server (thus lightdm) no longer works (apparently, according to
> the lightdm Xorg logs, no screens found). I can switch to a VT, but
> the login prompt is shown only for a fraction of second, after which
> I just get a blinking cursor over a black screen.
> 
> In case this matters, my xrandr configuration is
> 
>   xrandr --output DP-3 --off \
>  --output DP-4 --auto --primary \
>  --output DP-5 --auto --right-of DP-4
> 
> where DP-3 corresponds to the laptop screen. But this is no longer
> honored after the resume.

I eventually got rid of light-locker, so that there is no longer
any issue with the screensaver. But logging out also suspends the
system!

Both locking and logging out trigger the lightdm login prompt,
so that I suppose that this is the same issue, and it was not
light-locker that was suspending the system, but lightdm.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)