Bug#922095: light-locker: requires manually switching virtual terminals to unlock

2019-02-14 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2019-02-12 at 08:06 -0500, Dan Robinson wrote: > I was able to actually log in so I didn't realize that was an exact > duplicate. Yes sorry, this is a bit of a mess (which doesn't help user reporting bugs either). If you look at the end of

Bug#922095: light-locker: requires manually switching virtual terminals to unlock

2019-02-12 Thread Dan Robinson
I was able to actually log in so I didn't realize that was an exact duplicate. I have an Optimus laptop, it happens either using just the Intel card or with Optimus enabled (but that's still the Intel card driving the display). On Tue, Feb 12, 2019, 02:06 Yves-Alexis Perez -BEGIN PGP SIGNED

Bug#922095: light-locker: requires manually switching virtual terminals to unlock

2019-02-11 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forcemerge 846278 -1 On Mon, 2019-02-11 at 18:28 -0500, Dan Robinson wrote: > Off a fresh install with no changes to the system, light-locker doesn't > respond after locking the screen without manually switching VTs. Mouse or > key > input

Bug#922095: light-locker: requires manually switching virtual terminals to unlock

2019-02-11 Thread Dan Robinson
Package: light-locker Version: 1.8.0-3 Severity: normal Dear Maintainer, Off a fresh install with no changes to the system, light-locker doesn't respond after locking the screen without manually switching VTs. Mouse or key input just leaves the screen blanked (and backlight off). Manually