Hi everyone and a happy new year!
Today I decided to test the sway window manager, installed and configured it following the documentation step-by-step (sway wiki (https://github.com/swaywm/sway/wiki)). However, when I finish logging into the system the sway doesn't load, it's as if it crashed.
Make a sway debug log and then post it. It should tell you why it crashed.
@Dudemanguy 00:00:00.001 [INFO] [sway/main.c:347] Sway version 1.6.1
00:00:00.001 [INFO] [sway/main.c:348] wlroots version 0.14.1
00:00:00.011 [INFO] [sway/main.c:155] Linux artix 5.10.84-1-lts #1 SMP Wed, 08 Dec 2021 16:07:43 +0:43 +0000 x86_64 GNU/Linux
00:00:00.011 [INFO] [sway/main.c:171] Contents of /etc/os-release:
00:00:00.027 [INFO] [sway/main.c:155] NAME="Artix Linux"
00:00:00.027 [INFO] [sway/main.c:155] PRETTY_NAME="Artix Linux"
00:00:00.027 [INFO] [sway/main.c:155] ID=artix
00:00:00.027 [INFO] [sway/main.c:155] BUILD_ID=rolling
00:00:00.027 [INFO] [sway/main.c:155] ANSI_COLOR="0;36"
00:00:00.027 [INFO] [sway/main.c:155] HOME_URL="https://www.artixlinux.org/"
00:00:00.027 [INFO] [sway/main.c:155] DOCUMENTATION_URL="https://wiki.artixlinux.org/"
00:00:00.027 [INFO] [sway/main.c:155] SUPPORT_URL="https://forum.artixlinux.org/"
00:00:00.027 [INFO] [sway/main.c:155] BUG_REPORT_URL="https://bugs.artixlinux.org/"
00:00:00.027 [INFO] [sway/main.c:155] LOGO=artixlinux
00:00:00.028 [INFO] [sway/main.c:143] LD_LIBRARY_PATH=
00:00:00.028 [INFO] [sway/main.c:143] LD_PRELOAD=
00:00:00.028 [INFO] [sway/main.c:143] PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
00:00:00.028 [INFO] [sway/main.c:143] SWAYSOCK=
00:00:00.028 [DEBUG] [sway/server.c:47] Preparing Wayland server initialization
00:00:00.030 [INFO] [wlr] [libseat] [libseat/backend/seatd.c:80] Could not connect to socket /run/seatd.sock: No such file or directory
00:00:00.030 [INFO] [wlr] [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
00:00:00.055 [INFO] [wlr] [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind'
00:00:00.055 [INFO] [wlr] [backend/session/session.c:110] Successfully loaded libseat session
00:00:00.062 [INFO] [wlr] [backend/backend.c:233] Found 1 GPUs
00:00:00.062 [INFO] [wlr] [backend/drm/backend.c:182] Initializing DRM backend for /dev/dri/card0 (vmwgfx)
00:00:00.062 [DEBUG] [wlr] [backend/drm/drm.c:84] Using atomic DRM interface
00:00:00.062 [DEBUG] [wlr] [backend/drm/drm.c:97] ADDFB2 modifiers unsupported
00:00:00.062 [INFO] [wlr] [backend/drm/drm.c:259] Found 8 DRM CRTCs
00:00:00.062 [INFO] [wlr] [backend/drm/drm.c:186] Found 16 DRM planes
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
00:00:02.353 [ERROR] [wlr] [render/egl.c:281] Software rendering detected, please use the WLR_RENDERER_ALLOW_SOFTWARE environment variable to proceed
00:00:02.353 [ERROR] [wlr] [EGL] command: eglMakeCurrent, error: EGL_BAD_DISPLAY (0x3008), message: "Invalid display (nil)"
00:00:02.353 [ERROR] [wlr] [render/gles2/renderer.c:742] Could not initialize EGL
00:00:02.353 [DEBUG] [wlr] [render/wrl_renderer.c:281] Failed to create GLES2 renderer
00:00:02.354 [INFO] [wlr] [render/pixman/renderer.c:550] Creating pixman renderer
00:00:02.354 [DEBUG] [wlr] [render/allocator.c:49] Trying to create drm dumb allocator
00:00:02.354 [DEBUG] [wlr] [render/drm_dumb_allocator.c:245] Created DRM dumb allocator with node /dev/dri/card0
00:00:02.354 [ERROR] [wlr] [sway/main.c:202] Unable to drop root (we shouldn't be able to restore it after setuid), refusing to start
The log indicates that you are using the vmwgfx driver which is for vmware (should have mentioned this earlier). I don't think this supports EGL at all so naturally sway (and the majority of wayland compositors by extension) won't work. You could try to use the WLR_RENDERER_ALLOW_SOFTWARE variable as mentioned in the log instead which may work.
Hi, sorry for the delay! I was just testing others window managers.
Well, I followed your advice but the sway remains crashing during autostart.
It would be helpful to post a log. It's entirely possible that wayland just doesn't work on vmware though.