i said "how debian 10 has become stable with this bug?" . i did not
know meaning of the term stability about debian releases. now, i know
that stable means that debian has stable apis between different
programs, ie they do not change with updates, and so, custom systems
built by users also has
Hello
I have been struggling with the problems indicated in #870641 for some
time in relation to desktop machines - after locking the screen refuses
to wake up again. I believe I have discovered the solution, through
chance as much as anything else, and I expect it will also work with the
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.
>
this bug leads user to use ctrl+alt+f1 . seems using ctrl+alt+f1 is
dangerous, according to
https://security-tracker.debian.org/tracker/CVE-2018-20839 . is it
enough to put security tag to this bug?
buster, light-locker 1.8.0-3
how to reproduce:
1 under xfce, lock the screen;
2 the display turned off
3 when I need to use it, pressing keyboard or moving mouse will not turn
the screen back on.
I have this problem on both my laptop(which has a single integrated
intel card and my desktop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2020-06-09 at 12:43 +0800, Guus Ellenkamp wrote:
> I have been struggling for a long time with a laptop sometimes not
> waking up after sleep. I read some stuff here and indeed strange this
> bug is still there. I just installed LightDM
I have been struggling for a long time with a laptop sometimes not
waking up after sleep. I read some stuff here and indeed strange this
bug is still there. I just installed LightDM 1.30, but as I don't fully
understand the problem I am not sure if that would solve the problem.
Pressing keys
-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
i said "i could not find kde data, tried kde-full, kde-standard,
kde-plasma-desktop". seems it is plasma-desktop, and it has 10%
installs, 6% uses.
how debian 10 has become stable with this bug? (wikipedia: "Debian 10
(Buster) was released on 6 July 2019". this bug is reported at Thu, 03
Aug 2017). how many users this bug affect? does not it affect all
users? i think it only affects xfce or lightdm users. how many are
they?
i said "i use ctrl+alt+f6 then ctrl+alt+f7" . edit : i use ctrl+alt+f7
then ctrl+alt+f8 .
i said that i searched for "wake black" , but now i have found out
that mere ("mere" meanining "only") locking screen with ctrl+alt+L
also causes same black/turn off screen. (it stays black for some
little
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-12-14 at 21:34 +0300, dinar qurbanov wrote:
> > Do you still have the issue? Which kernel are you running? Are you on
> > stable
> > or testing/unstable?
>
> (this letter got to spam, so i answer a bit later). yes, still have.
> stable
>Do you still have the issue? Which kernel are you running? Are you on stable
>or testing/unstable?
(this letter got to spam, so i answer a bit later). yes, still have.
stable debian 10, 32bit.
Kernel version (/proc/version):
---
Linux version 4.19.0-6-686-pae
Package: light-locker
Version: 1.8.0-3
Followup-For: Bug #870641
More clues to my bug report immediately above:
Unable to resume after blanking xfce4 as follows:
- on ac power, no resume after blanking from light-locker
- on ac power, resumes properly from sleep
- on battery, resumes properly
Package: light-locker
Version: 1.8.0-3
Followup-For: Bug #870641
Dear Maintainer,
* What led up to the situation?
New install from Debian xfce4 iso image; on normal screen blank,
unable to resume with keyboard or mouse action
* What exactly did you do (or not do) that was effective
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-12-11 at 12:38 +0300, dinar qurbanov wrote:
> possible solutions/wokarounds:
> 1) https://bbs.archlinux.org/viewtopic.php?pid=1671675#p1671675
> 2)
> https://github.com/the-cavalry/light-locker/issues/108#issuecomment-502404552
> (i
possible solutions/wokarounds:
1) https://bbs.archlinux.org/viewtopic.php?pid=1671675#p1671675
2) https://github.com/the-cavalry/light-locker/issues/108#issuecomment-502404552
(i have not tried these).
(i use ctrl+alt+f6 then ctrl+alt+f7 as a workaround for now. )
i have found, with " site:https://bugs.debian.org/ wake black " and "
site:https://lists.debian.org/debian-user/ wake black " in google,
some other bugs that may be related: 680586, 773913, 882027, 886302.
and also some mailing list discussions:
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
40 matches
Mail list logo
