View Issue Details

IDProjectCategoryView StatusLast Update
0009060Kali LinuxGeneral Bugpublic2025-01-21 21:30
Reporterkpd Assigned Todaniruiz  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0009060: Lock screen activated despite settings set to not lock screen in Kali 2024.4
Description

Since Kali 2024.4, several users have reported that the lock screen is activated after a short period of inactivity, despite settings changed to prevent. Configuring power and display options to prevent screen lock does not stop the screen from locking automatically. I was running 2024.3 in a VM and had no problems. Performed an upgrade and first noticed the issue. Downloaded a new base install of 2024.4, and noticed the issue is also present with no additional changes.

To replicate issue, download new ISO image of 2024.4 in a VM and the screen logout will occur, even if the setting is disabled.

Several users affected, see this report and messages in OffSec Discord server for further examples.

Activities

kali-bugreport

kali-bugreport

2025-01-08 16:47

reporter   ~0020226

Needs to be reported to the Desktop Environment (e.g. XFCE) developers?

fiktion5

fiktion5

2025-01-17 17:08

reporter   ~0020262

Per a discussion with XFCE developers in https://gitlab.xfce.org/xfce/xfce4-power-manager/-/issues/260, xfce-power-manager (Version 4.20) no longer controls any applications that use the screensaver/screen lock.

light-locker is one of those screensaver/screen lock applications that is installed automatically in Kali. Killing this process and disabling it at startup seems to be the only way to stop the automatic lock-out at 10 minutes.

With xfce-power-manager version 4.20 no longer controlling applications like light-locker, should this be removed from automatic install?

I've attempted to use xfce-screensaver instead, but it appears it has issues with PAM as I'm not able to login after the screen locks (separate issue, I know).

kali-bugreport

kali-bugreport

2025-01-17 23:25

reporter   ~0020263

Just noticed this there:

Per Kali Bug Tracker, https://bugs.kali.org/view.php?id=9060, they suggested contacting the Desktop Environment developer.

As you can see i'm having "Reporter" permissions like you and obviously not part of the Kali team ;-)

fiktion5

fiktion5

2025-01-18 06:20

reporter   ~0020264

That may be a tad confusing with a name like"kali-bugreport", no?

kali-bugreport

kali-bugreport

2025-01-18 07:46

reporter   ~0020265

Last edited: 2025-01-18 09:19

Names are irrelevant, eg. the existing user "kali-rick" is unlikely a kali member. Only the the status matters, "Developer", "Manager" or "Administrator" are Kali team members :-)

Above text of me is also ending with "(e.g. XFCE) developers?" so a question not a suggestion :-)

kali-bugreport

kali-bugreport

2025-01-21 17:52

reporter   ~0020272

Relevant to this?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092854

https://forums.debian.net/viewtopic.php?t=161513

kpd

kpd

2025-01-21 18:13

reporter   ~0020273

Links are more symptoms of the underlying cause. Consumers of the xfce4-power-manager packages (such as Kali) need to update their code, as XFCE Devs have removed the link to control the power saver feature. Anyone using xfce4-power-manager will have this issue, e.g. Kali, Debian, etc. In terms of Kali, xfce4-power-manager controlled this, but when XFCE removed this component, it no longer works in Kali.

kali-bugreport

kali-bugreport

2025-01-21 20:52

reporter   ~0020274

IIUC Debian (would arrive in Kali afterwards) would only need to make sure that if xfce4-power-managrr is installed the light-locker is getting deinstalled and xfce4-screensaver is installed as https://xfce.org/about/tour mentions:


Lock screen management was massively simplified and "Light Locker" was dropped. "lock-on-sleep" is now synchronized with xfce4-session and xfce4-screensaver.

Screen locking settings are now only handled by xfce4-screensaver to avoid conflicts. A button to open xfce4-screensaver-preferences was added.

fiktion5

fiktion5

2025-01-21 21:00

reporter   ~0020275

Last edited: 2025-01-21 21:00

Then xfce4-screensaver should be the standard automatic install from Kali packages, and not "Light Locker", right?

Also, xfce4-screensaver has it's own login screen after locking (not lightdm), which for some reason has issues authenticating:

Jan 17 12:24:31 kali xfce4-screensaver-dialog[2979]: pam_unix(xfce4-screensaver:auth): authentication failure; logname=kali uid=1000 euid=1000 tty=:0.0 ruser= rhost=  user=kali          
Jan 17 12:24:31 kali xfce4-screensaver-dialog[2979]: pam_winbind(xfce4-screensaver:auth): getting password (0x00000388)                                                                   
Jan 17 12:24:31 kali xfce4-screensaver-dialog[2979]: pam_winbind(xfce4-screensaver:auth): pam_get_item returned a password                                                                
Jan 17 12:24:31 kali xfce4-screensaver-dialog[2979]: pam_winbind(xfce4-screensaver:auth): request wbcLogonUser failed: WBC_ERR_WINBIND_NOT_AVAILABLE, PAM error: PAM_AUTHINFO_UNAVAIL (9)!
Jan 17 12:24:31 kali xfce4-screensaver-dialog[2979]: pam_winbind(xfce4-screensaver:auth): internal module error (retval = PAM_AUTHINFO_UNAVAIL(9), user = 'kali')                         
kali-bugreport

kali-bugreport

2025-01-21 21:23

reporter   ~0020276

Last edited: 2025-01-21 21:30

Then xfce4-screensaver should be the standard automatic install from Kali packages, and not "Light Locker", right?

IIUC yes, but from Debian packages which Kali is then inheriting from (Don't think that Kali is maintaining this package on their own).

which for some reason has issues authenticating

Another issue for the XFCE or Debian bug tracker?

Issue History

Date Modified Username Field Change
2025-01-07 17:27 kpd New Issue
2025-01-08 16:47 kali-bugreport Note Added: 0020226
2025-01-08 18:41 dudah16x Issue cloned: 0009061
2025-01-17 17:08 fiktion5 Note Added: 0020262
2025-01-17 23:25 kali-bugreport Note Added: 0020263
2025-01-18 06:20 fiktion5 Note Added: 0020264
2025-01-18 07:46 kali-bugreport Note Added: 0020265
2025-01-18 09:19 kali-bugreport Note Edited: 0020265
2025-01-21 12:45 daniruiz Assigned To => daniruiz
2025-01-21 12:45 daniruiz Status new => assigned
2025-01-21 17:52 kali-bugreport Note Added: 0020272
2025-01-21 18:13 kpd Note Added: 0020273
2025-01-21 20:52 kali-bugreport Note Added: 0020274
2025-01-21 21:00 fiktion5 Note Added: 0020275
2025-01-21 21:00 fiktion5 Note Edited: 0020275
2025-01-21 21:23 kali-bugreport Note Added: 0020276
2025-01-21 21:30 kali-bugreport Note Edited: 0020276