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)

Processed: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

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

> forcemerge 961132 961124
Bug #961132 [light-locker] light-locker: with the nvidia driver, light-locker 
suspends the system when locking
Bug #961124 [light-locker] systemd: suspend for no apparent reasons when using 
light-locker and the screensaver becomes inactive
Severity set to 'important' from 'minor'
Marked as found in versions light-locker/1.8.0-3.
Merged 961124 961132
> reassign 961132 lightdm 1.26.0-7
Bug #961132 [light-locker] light-locker: with the nvidia driver, light-locker 
suspends the system when locking
Bug #961124 [light-locker] systemd: suspend for no apparent reasons when using 
light-locker and the screensaver becomes inactive
Bug reassigned from package 'light-locker' to 'lightdm'.
Bug reassigned from package 'light-locker' to 'lightdm'.
No longer marked as found in versions light-locker/1.8.0-3.
No longer marked as found in versions light-locker/1.8.0-3.
Ignoring request to alter fixed versions of bug #961132 to the same values 
previously set
Ignoring request to alter fixed versions of bug #961124 to the same values 
previously set
Bug #961132 [lightdm] light-locker: with the nvidia driver, light-locker 
suspends the system when locking
Bug #961124 [lightdm] systemd: suspend for no apparent reasons when using 
light-locker and the screensaver becomes inactive
Marked as found in versions lightdm/1.26.0-7.
Marked as found in versions lightdm/1.26.0-7.
> retitle -1 lightdm: with the nvidia driver, lightdm suspends the system when 
> locking or logging out
Bug #961132 [lightdm] light-locker: with the nvidia driver, light-locker 
suspends the system when locking
Bug #961124 [lightdm] systemd: suspend for no apparent reasons when using 
light-locker and the screensaver becomes inactive
Changed Bug title to 'lightdm: with the nvidia driver, lightdm suspends the 
system when locking or logging out' from 'light-locker: with the nvidia driver, 
light-locker suspends the system when locking'.
Changed Bug title to 'lightdm: with the nvidia driver, lightdm suspends the 
system when locking or logging out' from 'systemd: suspend for no apparent 
reasons when using light-locker and the screensaver becomes inactive'.

-- 
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

Processed: reassign 961124 to light-locker

2020-05-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 961124 light-locker
Bug #961124 [systemd] systemd: suspend for no apparent reasons when using 
light-locker and the screensaver becomes inactive
Bug reassigned from package 'systemd' to 'light-locker'.
No longer marked as found in versions systemd/245.5-2.
Ignoring request to alter fixed versions of bug #961124 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
961124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#961132: light-locker: with the nvidia driver, light-locker suspends the system when locking

2020-05-20 Thread Vincent Lefevre 
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.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  libc62.30-8
ii  libcairo21.16.0-4
ii  libdbus-1-3  1.12.16-2
ii  libdbus-glib-1-2 0.110-5
ii  libglib2.0-0 2.64.2-1
ii  libgtk-3-0   3.24.20-1
ii  libpango-1.0-0   1.44.7-4
ii  libpangocairo-1.0-0  1.44.7-4
ii  libsystemd0  245.5-2
ii  libx11-6 2:1.6.9-2+b1
ii  libxext6 2:1.3.3-1+b2
ii  libxss1  1:1.2.3-1
ii  lightdm  1.26.0-7

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

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