Closed Simao-pp-C closed 1 year ago
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.
hi, this repeat a lot of times wl_display@1.delete_id(20) [2703451.275] wl_callback@20.done(13373473) [2703451.289] -> wl_surface@16.frame(new id wl_callback@20) [2703451.302] -> wl_subsurface@18.set_position(465, 164) [2703451.314] -> wl_surface@17.attach(nil, 0, 0) [2703451.325] -> wl_surface@17.commit() [2703452.924] -> wl_surface@17.set_buffer_scale(1) [2703452.938] -> wl_surface@17.attach(wl_buffer@22, 0, 0) [2703452.950] -> wl_surface@17.damage_buffer(0, 0, 2147483647, 2147483647) [2703452.961] -> wl_surface@17.commit() [2703452.971] -> wl_surface@16.commit() [2703454.246] wl_buffer@22.release()
and
[2703033.263] -> wl_display@1.sync(new id wl_callback@20) [2703033.310] wl_display@1.delete_id(20) [2703033.321] wl_callback@20.done(6869)
not sure what i´m looking for
Attach the full log.
The lock is not using ext_session_lock, so whatever you are running is either:
Closing for now. You can reopen if the issue is observed with the latest swaylock release.
i´m using archt and when i lock screen it just unlock whit any key the version intaled is 6f67d76 10 jul 2023