Your message dated Thu, 26 Mar 2026 22:27:10 +0100
with message-id <[email protected]>
and subject line Re: Bug#1121493: crash: sway crashes on screen changes via
kanshi
has caused the Debian Bug report #1121493,
regarding crash: sway crashes on screen changes via kanshi
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1121493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121493
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libwlroots-0.19
Version: 0.19.1-1+b1
Severity: normal
Dear Maintainer,
when running kanshi on my setup. My triple monitor setup crashes as
follows:
```
00:00:00.846 [INFO] [sway/commands.c:261] Handling command 'exec
"~/.sway/scripts/swayidle-cmd"'
00:00:00.849 [INFO] [sway/commands.c:261] Handling command 'exec systemctl
--user start mako.service'
00:00:00.853 [INFO] [sway/server.c:550] Running compositor on wayland display
'wayland-1'
2025-11-27 09:55:36 - [main.c:282] Found config * for output HDMI-A-1 (Dell
Inc. DELL U2724DE J7NQD34)
2025-11-27 09:55:36 - [main.c:282] Found config * for output DP-2 (Dell Inc.
DELL U2724DE 57PQD34)
2025-11-27 09:55:36 - [main.c:282] Found config * for output DP-1 (Dell Inc.
DELL U2724DE 27NQD34)
00:00:03.559 [INFO] [sway/commands.c:261] Handling command 'exec alacritty'
00:00:03.742 [INFO] [sway/commands.c:261] Handling command 'title_format
"%title"'
sway: backend/drm/drm.c:1453: realloc_crtcs: Assertion `conn->crtc != NULL'
failed.
Io error: Connection reset by peer (os error 104)
Io error: Connection reset by peer (os error 104)
warning: queue 0x7f8870000c90 destroyed while proxies still attached:
zwp_primary_selection_device_v1#32 still attached
zwp_primary_selection_device_manager_v1#28 still attached
wl_data_device#31 still attached
wl_seat#30 still attached
wl_data_device_manager#29 still attached
wl_registry#27 still attached
Error: ExitFailure(1)
```
Configuring my screens via wdisplays does not lead to a chrash but does
not work as well, when applying chnages wdisplays crashes. Maybe
dependencies have to be updated so a rebuild of the tools is triggered.
Hope there is a solution to this.
Cheers
Jan
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.17.9+deb14-amd64 (SMP w/48 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libwlroots-0.19 depends on:
ii libc6 2.41-12
ii libdisplay-info3 0.3.0-1
ii libdrm2 2.4.127-1
ii libegl1 1.7.0-1+b2
ii libgbm1 25.2.7-1
ii libgles2 1.7.0-1+b2
ii libinput10 1.30.0-1
ii liblcms2-2 2.17-1
ii libliftoff0 0.5.0-1.1
ii libpixman-1-0 0.46.4-1
ii libseat1 0.9.1-1
ii libudev1 259~rc2-1
ii libvulkan1 1.4.328.1-1
ii libwayland-client0 1.24.0-2+b1
ii libwayland-server0 1.24.0-2+b1
ii libxcb-composite0 1.17.0-2+b1
ii libxcb-dri3-0 1.17.0-2+b1
ii libxcb-errors0 1.0.1-4
ii libxcb-ewmh2 0.4.2-1
ii libxcb-icccm4 0.4.2-1
ii libxcb-present0 1.17.0-2+b1
ii libxcb-render-util0 0.3.10-1
ii libxcb-render0 1.17.0-2+b1
ii libxcb-res0 1.17.0-2+b1
ii libxcb-shm0 1.17.0-2+b1
ii libxcb-xfixes0 1.17.0-2+b1
ii libxcb-xinput0 1.17.0-2+b1
ii libxcb1 1.17.0-2+b1
ii libxkbcommon0 1.12.3-1
libwlroots-0.19 recommends no packages.
libwlroots-0.19 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.19.3-1
On Thu Mar 26, 2026 at 10:14 PM CET, Jan Christoph Uhde wrote:
> On 2026-03-26 9:46 PM, Diederik de Haas wrote:
>> Can you test/confirm whether this bug is indeed fixed?
>
> The problem is resolved with the latest version. I installed the
> package and restarted sway before testing. Both kanshi and swayidle
> (using `swaymsg 'output * power off'` and `on`) work as expected.
Excellent. As you seem to be running Unstable, I'm closing the bug with
the version from Unstable.
Thanks for reporting back :-)
PS: (for next time) always keep the bug in To/Cc when replying
signature.asc
Description: PGP signature
--- End Message ---
