Confirming fixed in Debian 10.5 point release:
Bug is reproducible with kernel 4.19.0-9 running, not reproducible with
4.19.0-10 running. Tested via xdg-screensaver lock.
Another weird thing: on 4.19.0-9, if I leave the screen/display off long
enough, like:
1 lock the screen
2 see the display off
3 go out for lunch
4 when return, typing or moving mouse can bring the display back on.
As comparison, if I leave the screen/display off not long enough, like
going to
On Tue, Jul 14, 2020 at 07:38:21PM -0400, David Farrier wrote:
>
> On Tue, 14 Jul 2020, Aaron Lu wrote:
> >
> > Anyway, I downloaded this package directly from the mirror's pool:
> > linux-image-4.19.0-10-amd64-unsigned_4.19.131-2_amd64.deb
> > Is the above package correct?
> >
> > And the good
On Tue, 14 Jul 2020, Aaron Lu wrote:
Anyway, I downloaded this package directly from the mirror's pool:
linux-image-4.19.0-10-amd64-unsigned_4.19.131-2_amd64.deb
Is the above package correct?
And the good news is, this kernel also works fine :-)
I tried something similar, but am having
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2020-07-14 at 10:47 +0800, Aaron Lu wrote:
> On Mon, Jul 13, 2020 at 08:26:14PM +0200, Yves-Alexis Perez wrote:
> > Could you try linux-image-4.19.0-10-amd64 from testing-proposed-updates
> > and
> > report back? It should include the fix.
>
On Mon, Jul 13, 2020 at 08:26:14PM +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2020-07-13 at 10:33 +0800, Aaron Lu wrote:
> > On Tue, May 12, 2020 at 11:13:52AM +0200, Yves-Alexis Perez wrote:
> > > I've also re-pinged upstream Linux and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-07-13 at 10:33 +0800, Aaron Lu wrote:
> On Tue, May 12, 2020 at 11:13:52AM +0200, Yves-Alexis Perez wrote:
> > I've also re-pinged upstream Linux and the patch should be included in the
> > next Linux point release (hopefully 4.19.123),
On Tue, May 12, 2020 at 11:13:52AM +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2020-05-11 at 19:34 -0400, David Farrier wrote:
> > I see I am coming to this thread a bit late, but for what it is worth,
> > here is some additional information.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-05-11 at 19:34 -0400, David Farrier wrote:
> I see I am coming to this thread a bit late, but for what it is worth,
> here is some additional information.
>
> But first, thanks to Udo Richter for suggesting the workaround of
>
I see I am coming to this thread a bit late, but for what it is worth,
here is some additional information.
But first, thanks to Udo Richter for suggesting the workaround of
installing linux-image-5.4.0-0.bpo.2-amd64, in other words backporting the
testing/bullseye kernel into buster. On my
On 24.03.19 19:35, Udo Richter wrote:
I experience this behavior in most cases when light-locker kicks in as
screen saver. Closing the lid or suspending never triggers this. i965
driver on Sandybridge CPU. Ctrl-Alt-F6-F7 brings me to a
screen-is-locked display, and after some seconds, to the
Package: light-locker
Version: 1.8.0-3
Followup-For: Bug #870641
Dear Maintainer,
Another user here with the same issue, using Jeremiah Mahler's workaround
fixed the problem for me as well. I can confirm I see the same thing in the
xorg logs, which is fbdev is being loaded. Afer the work
One more for the mix:
I experience this behavior in most cases when light-locker kicks in as
screen saver. Closing the lid or suspending never triggers this. i965
driver on Sandybridge CPU. Ctrl-Alt-F6-F7 brings me to a
screen-is-locked display, and after some seconds, to the actual login
Re: Yves-Alexis,
On Tue, Oct 23, 2018 at 05:29:02PM +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Tue, 2018-10-23 at 08:07 -0700, Jeremiah Mahler wrote:
> > Re: Yves-Alexis,
> >
> > On Tue, Oct 23, 2018 at 11:01:21AM +0200, Yves-Alexis Perez wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2018-10-23 at 08:07 -0700, Jeremiah Mahler wrote:
> Re: Yves-Alexis,
>
> On Tue, Oct 23, 2018 at 11:01:21AM +0200, Yves-Alexis Perez wrote:
> [...]
> > On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote:
> > > I am experiencing this
Re: Yves-Alexis,
On Tue, Oct 23, 2018 at 11:01:21AM +0200, Yves-Alexis Perez wrote:
[...]
>
> On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote:
> > I am experiencing this problem and I found a workaround ...
>
> Did you try the other workarounds (vt-switch back and forth)? Was it not
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote:
> I am experiencing this problem and I found a workaround ...
Did you try the other workarounds (vt-switch back and forth)? Was it not
working?
> If I create an Xorg config file that says
Package: light-locker
Version: 1.8.0-2
Followup-For: Bug #870641
Hi,
I am experiencing this problem and I found a workaround ...
If I lock the screen it goes black and won't unlock from the
keyboard. If I ssh to the machine I can restart lightdm and
get a login prompt.
$ light-locker-command
I think I am experiencing the same issue as Thomas Maaß, though I am
not convinced that it is the same behavior as the initial report.
Namely, sometimes the display does not turn on when light-locker should be
prompting for a password (I think I have seen this both when returning from
hibernation
I have a similar Problem. But not only when hibernating. I have set up
to lock when the screensaver gets activated. I have no screensaver
installed, but configured a black screen. But this issue is not always.
Sometimes, the unlock screen appears as it should. Sometimes i can enter
my pw blind to
Package: light-locker
Version: 1.8.0-1
Followup-For: Bug #870641
Here the same with intel igpu.
After staying black, ctrl+alt+f1 and killing light-locker makes you able to go
back to desktop and resume work.
Regards
-- System Information:
Debian Release: buster/sid
APT prefers unstable
On 3.08.17, Yves-Alexis Perez wrote:
> On Thu, 2017-08-03 at 19:36 +0200, G. Milde wrote:
> > I use xfce on an eeepc laptop. It's configured to hibernate (Bereitschaft)
> > when the lid closes using xfce4-power-manager.
> Which graphic card and driver do you use?
lspci says:
Intel Corporation
On Thu, 2017-08-03 at 19:36 +0200, G. Milde wrote:
> I use xfce on an eeepc laptop. It's configured to hibernate (Bereitschaft)
> when the lid closes using xfce4-power-manager.
Which graphic card and driver do you use?
Regards,
--
Yves-Alexis
signature.asc
Description: This is a digitally
Package: light-locker
Version: 1.7.0-3
Severity: important
Dear Maintainer,
I use xfce on an eeepc laptop. It's configured to hibernate (Bereitschaft)
when the lid closes using xfce4-power-manager.
After updating to Debian stretch, the wakeup fails, the screen stays black
after opening (with
24 matches
Mail list logo
