Subject: bug#937: elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory

From: Nathan Schulte <[email-masked]>
Date: Fri, 23 Jan 2026 13:24:02 -0600

Source: elogind
Version: 255.17-4
Severity: normal
X-Debbugs-Cc: [email-masked]

Hello.

Upon upgrading to elogind packages version 255.17-4, SwayWM
fell/"crashed" back to vTTY, and is no longer able to be started,
producing the log attached. The log is produced with the command:

> sway --debug --verbose &> sway-$(date -u -Im).log

elogind service is running with this upgrade, and the system is
practically virgin (a fresh install). However, the only way I've managed
to launch Sway is by downgrading elogind packages to version 255.17-3.
Reboots, both warm and cold, do not resolve the issue, nor does any
amount of waiting.

Thank you for your attention.

-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 7 (freia/ceres)
Release:	7
Codename:	freia ceres
Architecture: x86_64

Kernel: Linux 6.18.5+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

-- no debconf information