Bug#735251: [Pkg-xfce-devel] Bug#735251: lightdm: user locale tweaks are clobbered by non-default locale

2018-07-24 Thread Vincent Lefevre
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

Bug#913062: light-locker: impossible to unlock: black screen, then the lightdm prompt again (not reproducible)

2018-11-06 Thread Vincent Lefevre
Package: light-locker Version: 1.8.0-2 Severity: important 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

Bug#928034: lightdm: acknowledge of shutdown is not visible immediately

2019-04-26 Thread Vincent Lefevre
Package: lightdm Version: 1.26.0-4 Severity: minor 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

Bug#913062: light-locker: impossible to unlock: black screen, then the lightdm prompt again

2019-09-11 Thread Vincent Lefevre
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

Bug#939970: lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out with elogind

2019-09-12 Thread Vincent Lefevre
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.

Bug#939970: lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out with elogind

2019-09-10 Thread Vincent Lefevre
Package: lightdm Version: 1.26.0-5 Severity: important 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),

Bug#913062: light-locker: impossible to unlock: black screen, then the lightdm prompt again

2020-01-27 Thread Vincent Lefevre
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

Bug#913062: light-locker: impossible to unlock: black screen, then the lightdm prompt again

2020-01-27 Thread Vincent Lefevre
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

Bug#913062: light-locker: impossible to unlock: black screen, then the lightdm prompt again

2020-01-20 Thread Vincent Lefevre
Control: retitle -1 light-locker: screen sometimes black on screensaver deactivation 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 > &g

Bug#913062: light-locker: impossible to unlock: black screen, then the lightdm prompt again

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

Bug#913062: light-locker: impossible to unlock: black screen, then the lightdm prompt again

2020-01-20 Thread Vincent Lefevre
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). The

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 >

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

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

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