Not sure if this is the righ forum to report this kind of problems, but after this morning's `pacman -Syu`, I began to observe that Sway crashes each time DPMS is forced off, for example after `swaymsg "output * dpms off"`. Downgrading wlroots0.19 (0.19.1-2 => 0.19.0-5) and libdisplay-info (0.3.0-1 => 0.2.0-2) (and mpv) "fixes" the problem. Small excerpt from the system journal: wrz 24 10:07:01 ganges sway[1030]: sway: backend/drm/drm.c:1453: realloc_crtcs: Assertion `conn->crtc != NULL' failed. wrz 24 10:07:01 ganges systemd-coredump[1262]: Process 1030 (sway) of user 1000 terminated abnormally with signal 6/ABRT, proc> wrz 24 10:07:01 ganges systemd[1]: Created slice Slice /system/systemd-coredump. wrz 24 10:07:01 ganges systemd[1]: Started Process Core Dump (PID 1262/UID 0). wrz 24 10:07:01 ganges systemd-coredump[1263]: [🡕] Process 1030 (sway) of user 1000 dumped core. Best, R
On Wed, 24 Sept 2025 at 10:24, Radosław Kintzi <radek@k4i.pl> wrote:
Not sure if this is the righ forum to report this kind of problems, but after this morning's `pacman -Syu`, I began to observe that Sway crashes
with millions of possible configurations, it's all but impossible to debug your issue without more :-P
On 9/24/25 11:23 AM, Radosław Kintzi wrote:
Not sure if this is the righ forum to report this kind of problems, but after this morning's `pacman -Syu`, I began to observe that Sway crashes each time DPMS is forced off, for example after `swaymsg "output * dpms off"`.
Downgrading wlroots0.19 (0.19.1-2 => 0.19.0-5) and libdisplay-info (0.3.0-1 => 0.2.0-2) (and mpv) "fixes" the problem.
Small excerpt from the system journal:
wrz 24 10:07:01 ganges sway[1030]: sway: backend/drm/drm.c:1453: realloc_crtcs: Assertion `conn->crtc != NULL' failed. wrz 24 10:07:01 ganges systemd-coredump[1262]: Process 1030 (sway) of user 1000 terminated abnormally with signal 6/ABRT, proc> wrz 24 10:07:01 ganges systemd[1]: Created slice Slice /system/systemd-coredump. wrz 24 10:07:01 ganges systemd[1]: Started Process Core Dump (PID 1262/UID 0). wrz 24 10:07:01 ganges systemd-coredump[1263]: [🡕] Process 1030 (sway) of user 1000 dumped core.
Best, R
wlroots0.19 0.19.1-2 should have fixed that [1]. Did you try restarting your sway session / rebooting after the upgrade to it? Might worth a try I guess. [1] https://gitlab.archlinux.org/archlinux/packaging/packages/wlroots0.19/-/comm... -- Regards, Robin Candau / Antiz
On Wed Sep 24, 2025 at 11:56 AM CEST, Robin Candau wrote:
wlroots0.19 0.19.1-2 should have fixed that [1].
It seems that you are correct.
Did you try restarting your sway session / rebooting after the upgrade to it? Might worth a try I guess.
I did — it's hard not to when Sway crashes. I checked the pacman.log, and this morning's system upgrade installed version 0.19.1-1 (I'm not sure why this happened - perhaps it was due to an out-of-sync mirror): [2025-09-24T07:39:54+0200] [ALPM] upgraded wlroots0.19 (0.19.0-5 -> 0.19.1-1) I initially downgraded the kernel: [2025-09-24T10:06:02+0200] [ALPM] downgraded linux-lts (6.12.48-1 -> 6.12.47-1) [2025-09-24T10:06:04+0200] [ALPM] downgraded linux-lts-headers (6.12.48-1 -> 6.12.47-1) and a few moments later (after reboot), wlroots: [2025-09-24T10:11:11+0200] [ALPM] downgraded wlroots0.19 (0.19.1-1 -> 0.19.0-5) I am not sure what made me believe that the problem was with version 0.19.1-2. Regardless, I am now using wlroots 0.19.1-2, and the system is stable.
[1] https://gitlab.archlinux.org/archlinux/packaging/packages/wlroots0.19/-/comm...
Thank you for directing me to this patch and encouraging me to perform one more check. R.
On 9/24/25 1:21 PM, Radosław Kintzi wrote:
On Wed Sep 24, 2025 at 11:56 AM CEST, Robin Candau wrote:
wlroots0.19 0.19.1-2 should have fixed that [1].
It seems that you are correct.
Did you try restarting your sway session / rebooting after the upgrade to it? Might worth a try I guess.
I did — it's hard not to when Sway crashes.
I checked the pacman.log, and this morning's system upgrade installed version 0.19.1-1 (I'm not sure why this happened - perhaps it was due to an out-of-sync mirror):
[2025-09-24T07:39:54+0200] [ALPM] upgraded wlroots0.19 (0.19.0-5 -> 0.19.1-1)
I initially downgraded the kernel:
[2025-09-24T10:06:02+0200] [ALPM] downgraded linux-lts (6.12.48-1 -> 6.12.47-1) [2025-09-24T10:06:04+0200] [ALPM] downgraded linux-lts-headers (6.12.48-1 -> 6.12.47-1)
and a few moments later (after reboot), wlroots:
[2025-09-24T10:11:11+0200] [ALPM] downgraded wlroots0.19 (0.19.1-1 -> 0.19.0-5)
I am not sure what made me believe that the problem was with version 0.19.1-2. Regardless, I am now using wlroots 0.19.1-2, and the system is stable.
Alright, good to know! Thanks for the confirmation :)
[1] https://gitlab.archlinux.org/archlinux/packaging/packages/wlroots0.19/-/comm...
Thank you for directing me to this patch and encouraging me to perform one more check.
No problem, thanks for actually performing the double check and glad to know that wlroots0.19 0.19.1-2 indeed fixes the issue (like it supposed to)!
R.
-- Regards, Robin Candau / Antiz
participants (3)
-
Andy Pieters
-
Radosław Kintzi
-
Robin Candau