no password pass about swaylock HOT 5 CLOSED

There's a chance that it's your PAM stack (/etc/pam.d/swaylock or one of its includes) that is misconfigured, with a module that is letting you pass.

If it's a swaylock bug, try running swaylock like this to collect a log: WAYLAND_DEBUG=1 swaylock 2>swaylock.log. Note that this log will contain all your keypresses, so do not type anything sensitive in this test.

from swaylock.

hi, this repeat a lot of times
[email protected]_id(20)
[2703451.275] [email protected](13373473)
[2703451.289] -> [email protected](new id wl_callback@20)
[2703451.302] -> [email protected]_position(465, 164)
[2703451.314] -> [email protected](nil, 0, 0)
[2703451.325] -> [email protected]()
[2703452.924] -> [email protected]_buffer_scale(1)
[2703452.938] -> [email protected](wl_buffer@22, 0, 0)
[2703452.950] -> [email protected]_buffer(0, 0, 2147483647, 2147483647)
[2703452.961] -> [email protected]()
[2703452.971] -> [email protected]()
[2703454.246] [email protected]()

and

[2703033.263] -> [email protected](new id wl_callback@20)
[2703033.310] [email protected]_id(20)
[2703033.321] [email protected](6869)

not sure what i´m looking for

from swaylock.

Attach the full log.

from swaylock.

swaylock.log

from swaylock.

The lock is not using ext_session_lock, so whatever you are running is either:

1. Older than v1.6 (that is, over a year old). If so, upgrade to the latest release and try again.
2. Not swaylock, but a fork. If so, report the issue to the maintainer of the fork instead of here.

Closing for now. You can reopen if the issue is observed with the latest swaylock release.

from swaylock.