swaywm
swaylock unlocks before password is typed fully when second monitor comes on after sleep
Likely related to #99. Quite often upon waking from sleep, it shows the unlock circle when I start typing but when my second monitor turns on the laptop is unlocked without me entering any password.
I'm using the latest sway version from the AUR sway version 1.5.1 and swaylock swaylock version 1.5-1-g5da2b1d (Jan 23 2020, branch 'master')
I can confirm this behavior and I actually see a crash:
$ coredumpctl info 1198028
PID: 1198028 (swaylock)
UID: 1000 (dave)
GID: 1000 (dave)
Signal: 6 (ABRT)
Timestamp: Wed 2021-01-13 20:37:16 CET (2min 25s ago)
Command Line: swaylock -F -f -e -c 000000
Executable: /usr/bin/swaylock
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (dave)
Boot ID: cdbba8066b4c4f5ea361d35a43ac9e3e
Machine ID: a5640b7a4f7946aa8d2d075962e96526
Hostname: hmbx
Storage: /var/lib/systemd/coredump/core.swaylock.1000.cdbba8066b4c4f5ea361d35a43ac9e3e.1198028.1610566636000000.zst
Message: Process 1198028 (swaylock) of user 1000 dumped core.
Stack trace of thread 1198028:
#0 0x00006cc53c5b4615 raise (libc.so.6 + 0x3d615)
#1 0x00006cc53c59d862 abort (libc.so.6 + 0x26862)
#2 0x00006cc53c5f65e8 __libc_message (libc.so.6 + 0x7f5e8)
#3 0x00006cc53c5fe27a malloc_printerr (libc.so.6 + 0x8727a)
#4 0x00006cc53c5ff324 malloc_consolidate (libc.so.6 + 0x88324)
#5 0x00006cc53c6011d3 _int_malloc (libc.so.6 + 0x8a1d3)
#6 0x00006cc53c602d04 malloc (libc.so.6 + 0x8bd04)
#7 0x00006cc53c8740b3 n/a (libcairo.so.2 + 0x4d0b3)
#8 0x00006cc53c85ecda n/a (libcairo.so.2 + 0x37cda)
#9 0x00006cc53c884177 n/a (libcairo.so.2 + 0x5d177)
#10 0x00006cc53c8840c7 n/a (libcairo.so.2 + 0x5d0c7)
#11 0x00006cc53c8840ac n/a (libcairo.so.2 + 0x5d0ac)
#12 0x00006cc53c8840ac n/a (libcairo.so.2 + 0x5d0ac)
#13 0x00006cc53c8840ac n/a (libcairo.so.2 + 0x5d0ac)
#14 0x00006cc53c88ba20 n/a (libcairo.so.2 + 0x64a20)
#15 0x00006cc53c85f29c n/a (libcairo.so.2 + 0x3829c)
#16 0x00006cc53c86678a n/a (libcairo.so.2 + 0x3f78a)
#17 0x00006cc53c866876 n/a (libcairo.so.2 + 0x3f876)
#18 0x00006cc53c88b52b n/a (libcairo.so.2 + 0x6452b)
#19 0x00006cc53c84488e n/a (libcairo.so.2 + 0x1d88e)
#20 0x00006cc53c854275 n/a (libcairo.so.2 + 0x2d275)
#21 0x00006cc53c8933f6 n/a (libcairo.so.2 + 0x6c3f6)
#22 0x00006cc53c84a995 n/a (libcairo.so.2 + 0x23995)
#23 0x00006cc53c89fe75 cairo_fill_preserve (libcairo.so.2 + 0x78e75)
#24 0x000008d48e6e75fc n/a (swaylock + 0x95fc)
#25 0x000008d48e6e608d n/a (swaylock + 0x808d)
#26 0x00006cc53bd56acd n/a (libffi.so.7 + 0x6acd)
#27 0x00006cc53bd5603a n/a (libffi.so.7 + 0x603a)
#28 0x00006cc53c75de92 n/a (libwayland-client.so.0 + 0x9e92)
#29 0x00006cc53c75a6c1 n/a (libwayland-client.so.0 + 0x66c1)
#30 0x00006cc53c75bccc wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x7ccc)
#31 0x00006cc53c75c160 wl_display_roundtrip_queue (libwayland-client.so.0 + 0x8160)
#32 0x00006cc53bd56acd n/a (libffi.so.7 + 0x6acd)
#33 0x00006cc53bd5603a n/a (libffi.so.7 + 0x603a)
#34 0x00006cc53c75de92 n/a (libwayland-client.so.0 + 0x9e92)
#35 0x00006cc53c75a6c1 n/a (libwayland-client.so.0 + 0x66c1)
#36 0x00006cc53c75bccc wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x7ccc)
#37 0x000008d48e6e51c1 n/a (swaylock + 0x71c1)
#38 0x000008d48e6e4faf n/a (swaylock + 0x6faf)
#39 0x000008d48e6e35ff n/a (swaylock + 0x55ff)
#40 0x00006cc53c59f152 __libc_start_main (libc.so.6 + 0x28152)
#41 0x000008d48e6e3ade n/a (swaylock + 0x5ade)
This is with
- swaylock 1.5
- cairo 1.17.4
- pam 1.5.0
- wayland 1.18.0
- gdk-pixbuf2 2.24.2
on Arch Linux.
Neither my circus nor monkeys, but it looks like https://github.com/swaywm/swaylock/pull/219 solved this? :)
You're probably right! I haven't seen this issue occur in a very long time. 🥳