Hi, swaylock only works on wayland compositors that support the layer shell protocol [0], like sway. Do you use such a wayland compositor?
cheers, Birger [0] https://github.com/swaywm/wlr-protocols/blob/master/unstable/wlr-layer-shell-unstable-v1.xml On 7/21/20 12:45 PM, Jonathan Marsaud wrote: > Package: swaylock > Version: 1.5-2 > Severity: normal > X-Debbugs-Cc: jonathanmars...@gmail.com > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > Installing the package "swaylock" from Sid. > > * What was the outcome of this action? > zic@excalibur:~$ swaylock > swaylock: ../main.c:1183: main: Assertion `state.compositor && > state.layer_shell && state.shm' failed. > Abandon > > * What outcome did you expect instead? > Lock the Wayland input without blocking the display (swaylock is > supposed to be a "xtrlock" replacement for Wayland instad of X.org) > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages swaylock depends on: > ii libc6 2.31-1 > ii libcairo2 1.16.0-4 > ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 > ii libglib2.0-0 2.64.4-1 > ii libpam0g 1.3.1-5 > ii libwayland-client0 1.18.0-1 > ii libxkbcommon0 0.10.0-1 > > swaylock recommends no packages. > > swaylock suggests no packages. > > -- no debconf information >
