Bug#870641: light-locker: screen stays black after closing and opening laptop lid

2020-07-14 Thread David Farrier



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 mixed results. I added 
"buster-proposed-updates main" to sources.list, and installed 
linux-image-4.19.0-10-amd64. Which I think should be the same as Aaron Lu 
retrieved, except I have the signed variant. I installed on a Panasonic 
CF-19 laptop running Debian 10.4 and xfce.


Recovering from screen blanking and locking does work with that version of 
the kernel. So, on my computer, it does work better than the standard 
buster kernel 4.19.0-9. However, suspend and hibernate still don't work. 
I haven't had a chance to try Aaron Lu's suggestion of backported kernel 
5.6.0. However, I have been using 5.4.0 for a while, and blanking, 
locking, suspend, and hibernate all work with that version.


Hope this information is helpful.



Bug#870641: light-locker: screen stays black after closing and opening laptop lid

2020-05-11 Thread David Farrier
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 laptop, this fixed the 
intermittent problem restoring blanked screen. It also seems to have 
introduced a new problem where the computer occasionally does not blank 
or lock when it should, but that is far better than occasionally losing 
work-in-progress due to inability to restore the screen.


However, this does not seem to simply be a case of buster's default 4.19.0 
kernel being buggy. I say this, because I tried the backport version of 
4.19.0 in stretch. On my laptop, screen blanking and locking work just 
fine in stretch, regardless whether it is the default 4.9.0 or the 
backported 4.19.0 kernel. Apparently, something besides the kernel 
changed between stretch and buster.


Some background info: I have been testing with the xfce desktop on a 
Panasonic CF-19 laptop. Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller (rev 06)




Buster upgrade introduces power manager DBus errors

2019-08-17 Thread David Farrier
Please help me interpret some error messages in the xfce4-power-manager 
daemon log. I collected these logs because, when I upgraded from Debian 9 
stretch to Debian 10 buster, the screen backlight adjustment on my 
Panasonic CF-19 laptop no longer works, and the various sleep modes have 
become erratic.


Among other things, I tried collecting the logs when the power manager 
daemon restarts:

# xfce4-power-manager -q
# xfce4-power-manager --nodaemon --debug
The logs in stretch and buster look very similar, however there are three 
new warning and one critical message in the log under buster.


The three new warnings are at the very beginning of the log:
** (xfce4-power-manager:1643): WARNING **: 01:14:35.473: Failed to get 
name owner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could 
not get owner of name 'org.freedesktop.PowerManagement': no such name
** (xfce4-power-manager:1643): WARNING **: 01:14:35.473: Failed to get 
name owner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could 
not get owner of name 'org.xfce.PowerManager': no such name
(xfce4-power-manager:1643): GLib-GObject-WARNING **: 01:14:35.489: 
../../../gobject/gsignal.c:2523: signal 'Changed' is invalid for instance 
'0x558c1e1d2220' of type 'GDBusProxy'

TRACE[xfpm-main.c:205] xfpm_start(): Starting the power manager
...

The critical message is in the middle of the startup messages:
...
(xfce4-power-manager:1643): GLib-CRITICAL **: 01:14:35.512: g_error_free: 
assertion 'error != NULL' failed

...

Please tell me what these messages mean and what I should try next to fix 
this.



Some additional information:

By the screen backlight adjustment no longer working, I mean, after 
upgrading to buster, neither the laptop's brightness buttons nor the power 
manager applet in the xfce tray are able to change the brightness. The 
laptop buttons still do work during an early part of the boot process.


By sleep modes being erratic, I mean the laptop going to sleep and 
recovering usually works, but occasionally goes to a mode (screen lock 
versus suspend versus hibernate versus powerdown) other than intended. Of 
course, powering down when you still have applications open is most 
frustrating. So far, I haven't been able to figure out how to make this 
problem reproducible. Have been focusing on the brightness problem since 
it is reproducible.


I should mention the warnings that occur under both stretch and buster:
...
(xfce4-power-manager:1643): xfce4-power-manager-WARNING **: 01:14:35.506: 
could not map keysym 1008ffa8 to keycode
** (xfce4-power-manager:1643): WARNING **: 01:14:35.512: No outputs have 
backlight property
xfce4-power-manager-Message: 01:14:35.543: Set kernel brightness switch to 
0
(xfce4-power-manager:1643): xfce4-power-manager-WARNING **: 01:14:35.547: 
Failed to get keyboard max brightness level : 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
“org.freedesktop.UPower.KbdBacklight” on object at path 
/org/freedesktop/UPower/KbdBacklight

...

Which I interpret the first message to mean Xfce's notion of the laptop's 
key map is not quite right.


The others I think mean power manager first tries to control the backlight 
via an X server property. When that fails, it tries UPower. When that 
fails, it falls back to a method that provides no feedback whether it 
works or not. Whatever that method is, it works under stretch but not 
buster. Does this interpretation sound reasonable? Anyhow, it works fine 
under stretch despite these warnings. Would like to understand them, but 
if you can help me understand the warnings from buster, or for that 
matter, getting backlight and sleep working without understanding the 
warnings, that would be most appreciated. I can send the full logs, if 
that would be helpful.