Web12. apr 2024. · Hi, I'm having trouble getting hikari and sway running. I'm not using x11. I have installed drm-kmod. What could I have done wrong? I've been "using" FreeBSD for … WebThis fixed the problem and it can still start after a reboot. I've written a patch which addresses this issue. You can see swaywm/wlroots#1895 or build from master if you'd like to test it, but you must apply the referenced systemd patch as well for it to actually fix the described issue. Great, thank you!
postmarketOS // Sway, SWMO: missing seat group
WebAlternatively, if you're strictly on embedded intel graphics, your backend DRM device driver should be accessible through mesa-dri. I actually just did this setup again myself … Web03. feb 2024. · To use seatd service, builtin and server USE flags are required. In addition, to have access to seatd, it is required to be part of the video and seat groups: root # gpasswd -a larry video. root # gpasswd -a larry seat. Add the seatd daemon to the default runlevel so that seat management is provided on system startup: root # rc-update add … fit rizskása
"[libseat/backend/seatd.c:70] Could not connect to socket …
Web11. mar 2024. · Running Sway on Void Linux (without SystemD) elogind is the part of SystemD logind that can run as standalone. So we need it to run Sway without SystemD. To do that we need to build wlroots with elogind option. Then we can install and use Sway as normal from the current repo. There are other ways to achieve this without elogind here. Web15. sep 2024. · The text was updated successfully, but these errors were encountered: Web04. mar 2024. · No backend was able to open a seat [ERROR] [wlr] [libseat] [libseat/libseat.c:78] No backend was able to open a seat It is looking for a seat management daemon such as sys-auth/seatd or sys-auth/elogind. Also check whether setting XDG_RUNTIME_DIR is required. fit reggeli rizskása