Open seagoj opened 10 months ago
@seagoj Are you able to run dwl without GDM?
Have you set any particular bindings in your config.h file?
the black black screen is alright as dwl does not ship a background by default. Have you checked if you are using the correct keybindings? By default, dwl uses the alt key instead of the super key.
Yes, none of the bindings I've added work and alt+p doesn't launch bemenu and shift+alt+q doesn't kill it.
Something is happening though, because the screen does change from totally black to a slightly lighter black.
I can launch dwl from the TTL just fine. It only fails via GDM
@seagoj Modify the .desktop file used for launching dwl from GDM to redirect stderr (like /path/to/dwl 2>/tmp/dwl.log
) and see if dwl is even starting.
@fauxmight
amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
00:00:00.043 [ERROR] [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use
00:00:00.043 [ERROR] [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X1: Address already in use
00:00:00.072 [ERROR] [backend/x11/backend.c:695] X11 error: op ChangeProperty (no minor), code Atom (no extension), sequence 62, value 0
00:00:00.072 [ERROR] [backend/x11/backend.c:695] X11 error: op ChangeProperty (no minor), code Atom (no extension), sequence 63, value 0
00:00:00.072 [ERROR] [backend/x11/backend.c:695] X11 error: op ChangeProperty (no minor), code Atom (no extension), sequence 64, value 0
Compared to launching from the TTY:
amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
00:00:00.062 [ERROR] [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use
Info
dwl version: 0.4 wlroots version: 0.16.2
Description
I understand this is likely not at all, or at least not entirely, DWL's problem, but when I launch the DWL session from GDM, I just get a black screen that does not respond to any keyboard commands. This GDM instance is also running wayland, so my first thought was an issue launching the compositor.
Thanks for your time!