Closed aesof01 closed 1 year ago
Are you running dwl from a tty (drm backend), another wayland compositor (wayland backend), or inside an X session (x11 backend)?.
My guess is that you are trying to run dwl in a X session but your wlroots build does not have support for the x11 backend.
I am trying to run it from a tty
Mmmm, what is your distro?
Gentoo
Please apply this diff and send me the stderr.
diff --git a/dwl.c b/dwl.c
index 19bb6ce..bbf282b 100644
--- a/dwl.c
+++ b/dwl.c
@@ -2069,6 +2069,7 @@ setup(void)
/* The Wayland display is managed by libwayland. It handles accepting
* clients from the Unix socket, manging Wayland globals, and so on. */
dpy = wl_display_create();
+ wlr_log_init(WLR_DEBUG, NULL);
/* Set up signal handlers */
#ifdef XWAYLAND
Just to confirm, your wlroots is built with USE='drm libinput', right?
my use flags are USE="libinput -X -drm -tinywl -vulkan -x11-backend" i am compiling with drm right now
Ah, yeah, it's because you don have USE=drm.
Now I get a different error
00:00:10:010 [backend/backend.c:217] Found 0 GPUs, cannot create backend
00:00:10.010 [backend/backend.c:390] Failed to open any DRM device
couldn't create backend
My USE Flags for media-libs/mesa USE="X gles2 wayland" VIDEO_CARDS="nouveau"
What is your VIDEO_CARDS for x11-libs/libdrm?
VIDEO_CARDS="nouveau"
CONFIG_DRM_NOUVEAU is disabled in the kernel maybe that's the problem
Check dmesg for messages of drm or nouveau (dmesg | grep -i -E 'drm|nouveau'
)
CONFIG_DRM_NOUVEAU is disabled in the kernel maybe that's the problem
Yeah, that's it. Please recompile.
ACPI: bus type drm_connector registered
Just enable nouveau in the kernel, recompile and try to run dwl again.
Thanks, that solved the issue
I got the same error message but I am using nvidia-dkms. Any ideas?
distro: Arch Linux backend: DRM dwl version: wlroots-next d4f2c6b wlroots version: master e315068b9848d7fc920eb21340a076bb6587c1ff
00:00:00.000 [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.cockt No euch file or dirtetory
00:00:00.000 [libseat] [libseat/libseat.c:76] Backend seatd' failed to open seat, skipping
00:00:00.004 [libseat] [libseat/libseat.c:73] Seat opened with backend "logind"
00:00:00.004 [backend/session/session.c:109] Successfully loaded libseat session
00:00:00.004 [backend/session/session.c:384] Ignoring "/dev/dri/card0': not a KMS device
00:00:00.005 [backend/backend.c:217] Found 0 GUs, cannot create backend
00:00:00.005 [backend/backend.c:383] Failed to open any DRM device
couldn't create backend
@ST-Saint Enable kernel mode setting for nvidia.
In your bootloader, set the kernel parameter nvidia_drm.modeset=1
Slightly better described here: https://wiki.archlinux.org/title/NVIDIA
Hey, I'm having some issues to initialize it too.
I'm also on Gentoo but I'm compiling by myself.
These are the logs after adding wlr_log_init(WLR_DEBUG, NULL);
as asked
00:00:00.000 [INFO] [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
00:00:00.000 [INFO] [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
00:00:00.000 [ERROR] [libseat] [libseat/libseat.c:79] No backend was able to open a seat
00:00:00.000 [ERROR] [backend/session/session.c:83] Unable to create seat: Function not implemented
00:00:00.000 [ERROR] [backend/session/session.c:248] Failed to load session backend
00:00:00.000 [ERROR] [backend/backend.c:79] Failed to start a session
00:00:00.000 [ERROR] [backend/backend.c:359] Failed to start a DRM session
couldn't create backend
I'm using the official Makefile of the release v0.5
I could not figure out by myself how to fix this
@pandasoli How are you running dwl.
I'm on gentoo with seatd and elogind installed.
Usually you need to launch dwl with dbus:
dbus-run-session dwl
@fictitiousexistence I was just running dwl
in the tty, but running that way gives the same problem.
I'm with elogind and seatd installed too. As it says:
[ebuild R ] sys-auth/seatd-0.8.0:0/1::gentoo USE="-builtin -elogind -server -systemd" 0 KiB
[ebuild R ] sys-auth/elogind-252.9::gentoo USE="acl cgroup-hybrid pam policykit -audit -debug -doc (-selinux) -test" 0 KiB
@pandasoli I have the elogind flag enabled for seatd and also the elogind service enabled at boot.
@fictitiousexistence Done!!
I ran dbus-run-session dwl > .log 2>&1
May you tell if it is normal? btw, there's anything non expected going on
@pandasoli Nothing looks non-expected to me but I don't know enough about dwl to say you should trust me on that. I also don't have any debugging on so your output has extra stuff than mine.
Did dwl work now? It looked like it did...
Yeah it did bro @fictitiousexistence thx very much!
Info
dwl version: 0.4 wlroots version: 0.16.2-r1
Description
I get an error message when I try to run dwl