Process crash upon DPMS on

[a-priestley]

This doesn't seem to happen every time, but the longer my displays are off, the more likely it is that this will happen when they turn back on. I'm using two displays with different resolutions and refresh rates.

Trace:

``` Process 3844226 (swaylock) of user 1000 dumped core. Stack trace of thread 3844226: #0 0x00007fc7462e4ab3 wl_proxy_marshal_flags (libwayland-client.so.0 + 0xaab3) #1 0x000055b52eade71c n/a (swaylock + 0xa71c) #2 0x00007fc7459bd4f6 n/a (libffi.so.8 + 0x74f6) #3 0x00007fc7459b9f5e n/a (libffi.so.8 + 0x3f5e) #4 0x00007fc7459bcb73 ffi_call (libffi.so.8 + 0x6b73) #5 0x00007fc7462e1645 n/a (libwayland-client.so.0 + 0x7645) #6 0x00007fc7462e1e03 n/a (libwayland-client.so.0 + 0x7e03) #7 0x00007fc7462e1ffc wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x7ffc) #8 0x000055b52eade4a5 n/a (swaylock + 0xa4a5) #9 0x000055b52eaddd57 n/a (swaylock + 0x9d57) #10 0x000055b52eadb771 n/a (swaylock + 0x7771) #11 0x00007fc74609b290 n/a (libc.so.6 + 0x23290) #12 0x00007fc74609b34a __libc_start_main (libc.so.6 + 0x2334a) #13 0x000055b52eadbdf5 n/a (swaylock + 0x7df5) Stack trace of thread 3844227: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844230: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844229: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844228: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844231: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844233: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844235: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844237: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844241: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844239: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844236: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844234: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844240: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844232: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844238: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844244: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844242: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844245: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) Stack trace of thread 3844243: #0 0x00007fc74629eeee futex_wait (libgomp.so.1 + 0x1feee) #1 0x00007fc74629c450 gomp_simple_barrier_wait (libgomp.so.1 + 0x1d450) #2 0x00007fc7460fe8fd n/a (libc.so.6 + 0x868fd) #3 0x00007fc746180d20 n/a (libc.so.6 + 0x108d20) ELF object binary architecture: AMD x86-64 ░░ Subject: Process 3844226 (swaylock) dumped core ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ Documentation: man:core(5) ░░ ░░ Process 3844226 (swaylock) crashed and dumped core. ░░ ░░ This usually indicates a programming error in the crashing program and ░░ should be reported to its vendor as a bug. ```

It happens with both this fork, and with the upstream swaylock-effects, but not with swaylock.

[a-priestley]

After a system update today, this seems to have been resolved. however effects do not work properly on the secondary display after resume (white background).

[jflanglois]

This has started happening to me... NixOS unstable (currently at 897876e4c484f1e8f92009fd11b7d988a121a4e7, kernel version 6.3.1, swaylock version 1.6.11.

[jflanglois]

I don't have good evidence for this yet, but it might be related to the grace period. I'm trying things out with no grace period and it seems to be working fine so far. It could be that there's a bug in the time calculation? The lock screen does seem to disappear on input when it malfunctions.

[jacobmichels]

Could this be related to the hyprland discussion here? https://github.com/hyprwm/Hyprland/issues/4134