On 2014-01-17 09:55:22 +0100, Yves-Alexis Perez wrote:
> The greeter doesn't set anything, it gets the menu selection and gives
> it to lightdm.
A problem is that the greeter forces the first menu entry to be
selected by default instead of having a "nothing selected" state.
I reported the
After being idle, the screen was automatically locked.
A bit later, I entered my password to unlock, but I got a black
screen, then after some time, the lightdm prompt again. I tried
two other times. Same problem. I eventually rebooted
I have the following issue with a machine using sysvinit (I don't
think that sysvinit is the culprit, just that it makes the problem
visible). This has occurred for several months now (perhaps after
the upgrade from 1.18.3 to 1.26, but I'm not
On 2019-09-11 20:17:48 -0400, Christopher David Howie wrote:
> I also experience this problem. It is intermittent, making it difficult
> to reproduce, and it may or may not depend on specific hardware.
I think I have never reproduced this problem on any machine
(including the same machine, which
Control: forcemerge 932047 -1
On 2019-09-10 17:55:06 +0100, Mark Hindley wrote:
> I believe this is the same as the bug I submitted #932047.
> You might like to try the pam configuration fix I have there?
Indeed, that's the same issue, and your configuration fix solves
the problem for me.
I have a machine still using sysvinit, and systemd-shim has been
replaced by elogind for such machines. The dependencies have been
updated in lightdm 1.26.0-4. But after the upgrade (which did not
output any warning about a regression),
On 2020-01-25 12:53:58 +0100, Yves-Alexis Perez wrote:
> On Mon, 2020-01-20 at 12:03 +0100, Vincent Lefevre wrote:
> > > In case this might depend on the driver, I was using the nvidia
> > > driver (and I still use it on this machine).
> > My l
On 2020-01-27 19:11:49 +0100, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> On Mon, 2020-01-27 at 10:54 +0100, Vincent Lefevre wrote:
> > It was the kernel from Debian/unstable at the time I reported the
> > bug, and it still occurred
Control: retitle -1 light-locker: screen sometimes black on screensaver
On 2019-09-12 03:46:03 +0200, Vincent Lefevre wrote:
> On 2019-09-11 20:17:48 -0400, Christopher David Howie wrote:
> > I also experience this problem. It is intermittent, making it difficult
On 2020-01-20 12:58:41 +0100, Vincent Lefevre wrote:
> On 2020-01-20 12:03:30 +0100, Vincent Lefevre wrote:
> > I'm going to turn on the debug messages to see whether there is a
> > difference when the problem occurs.
> Unfortunately, light-locker does not output any
On 2020-01-20 12:03:30 +0100, Vincent Lefevre wrote:
> I'm going to turn on the debug messages to see whether there is a
> difference when the problem occurs.
Unfortunately, light-locker does not output any debug message
when the screensaver stops (whether or not the bug has occurred).
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
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: Suspending...
and according to the systemd maintainer, this is light-locker's
ith 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.
Mail list logo