#1077277 xfce4-settings: screen locked but lockscreen invisible after suspend

Package:
xfce4-settings
Source:
xfce4-settings
Description:
graphical application for managing Xfce settings
Submitter:
Rodrigo Campos
Date:
2024-08-01 14:18:05 UTC
Severity:
normal
#1077277#5
Date:
2024-07-27 19:02:16 UTC
From:
To:
Dear Maintainer,

The lockscreen after suspend is not reliable. Sometimes it is shown,
sometimes it isn't, but the screen is always locked. Sometimes my apps
are showing, no indication of the lockscreen, but mouse clicks, etc.
don't work. The screen is, and it really acts as if, the screen is locked.

If I type my passowrd and hit "enter", the screen is usable again. This
behavior of it not showing has caused me to write my passowrd and send
it in places I'd rather not to :(.

This problem seems to be caused because xfce4-settings is compiled with
upower-glib support[1]. The linked answer explains the problem, but this
other answer explains just how to recompile the debian package disabling
upower-glib support[2]. Please note the third answer too, as some
reported to disable it in another way[3] to do the trick (maybe it was
using versions that didn't disable it by default yet?).

The bug is also reported upstream[4] and upstream disabled compiling
with upower-glib by default 3 years ago[5].

Can you please disable upower-glib support in the debian package?



Best,
Rodrigo


[1]: https://askubuntu.com/a/1446916
[2]: https://askubuntu.com/a/1424719
[3]: https://askubuntu.com/a/1439372
[4]: https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/222
[5]: https://gitlab.xfce.org/xfce/xfce4-settings/-/merge_requests/20

#1077277#10
Date:
2024-07-28 08:46:25 UTC
From:
To:
Hi Rodrigo,

I guess we can try to disable it at least for a try, but I think if we do that
we lose the lid events, preventing I think to disable the laptop screen when
the lid is closed.

It'd be best to fix the detection code there, but we can see what happens at
least.

Regards,

#1077277#15
Date:
2024-07-28 09:04:42 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
xfce4-settings, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1077277@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez <corsac@debian.org> (supplier of updated xfce4-settings package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 28 Jul 2024 10:49:47 +0200
Source: xfce4-settings
Architecture: source
Version: 4.18.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers <debian-xfce@lists.debian.org>
Changed-By: Yves-Alexis Perez <corsac@debian.org>
Closes: 1077277
Changes:
 xfce4-settings (4.18.6-2) unstable; urgency=medium
 .
   * disable upower-glib support (Closes: #1077277)
Checksums-Sha1:
 10c1f1ada25037d349a8423fd993f1f063dbf760 1979 xfce4-settings_4.18.6-2.dsc
 fe0cbb73dce7d0fd65d31dd9922e5ed5167f259a 9324 xfce4-settings_4.18.6-2.debian.tar.xz
 d1548a5a6cd8503d760c9d9664712d70f0212ea9 16868 xfce4-settings_4.18.6-2_amd64.buildinfo
Checksums-Sha256:
 44b1f8bd169c28d98aa334bd35d43ff64e4d1c5f731463655250c4bcda760a77 1979 xfce4-settings_4.18.6-2.dsc
 ce542555b97777646e765118cebcc37dee34ed0f40293c4111907c84066250a8 9324 xfce4-settings_4.18.6-2.debian.tar.xz
 6cd09369fedbc15c81aff19bb961008b071c1e91d0dd7b731caa9ca64aa86c39 16868 xfce4-settings_4.18.6-2_amd64.buildinfo
Files:
 8ffc395010884a01d612bf17f5941ffa 1979 xfce optional xfce4-settings_4.18.6-2.dsc
 b9178c5c8ef4d5363d7e568d2d8a9eda 9324 xfce optional xfce4-settings_4.18.6-2.debian.tar.xz
 192a406cd50939fe728b752772c56d1e 16868 xfce optional xfce4-settings_4.18.6-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmamBysACgkQ3rYcyPpX
RFtuzgf/ceBwgr4TdmRjUX3X93+pfrZO90Emtv/EHd1osKSYtzxYFZc0JwQhpHva
ZHCikt2rtQIcqh9+i8PT8hMaZVm2bAVAEnso/810TKlevV5SpzKidNZxXH1XFicg
f1p+ozIFDa7kSjM6jOzT+ltZRkKdWb0JW0wFZGZP0B+0sI2vbTgMqRlzEYYe4CUY
Om+DSVoXJtNmmcj56vWTI+K2JLsOqQxEJLJtPqYojJOBWMXNSFq4TfrcJ5Yq4QU5
b4AqrZ1mUcB7fKS5VqtWeEeYCAlwDs370n+tvXLQtC0GDWqV6DbN1ZWyFl0kjw6E
Sf4SEwWY2lKmZDSa+52VX1W1se+XaQ==
=/Fcb
-----END PGP SIGNATURE-----

#1077277#20
Date:
2024-07-29 14:10:25 UTC
From:
To:
Thanks! I've been trying it in the last couple of days and it seems to
fix the problem reliably for me.

I've tried after sleep, after sleep and a new screen connected, sleeping
when the screensaver is active, etc.

Is there something else you want me to try?



Best,
Rodrigo

#1077277#25
Date:
2024-08-01 11:23:01 UTC
From:
To:
I wasn't really worried about not fixing the problem, but more about having
side effects of losing the LID closure detection.

#1077277#30
Date:
2024-08-01 14:11:22 UTC
From:
To:
Is there anything I can try to help you understand that?



Best,
Rodrigo

#1077277#35
Date:
2024-08-01 14:14:27 UTC
From:
To:
Well if you notice any new, undesirable behavior, please share it here. And I
guess we'll see once the new version gains exposure if there are any side
effect reported.

Regards,