-
Notifications
You must be signed in to change notification settings - Fork 283
TTY display failure #67
Comments
Uncomment |
So simple. Thank you, sorry I didn't thoroughly check the source code first. What I get next however I think is a death sentence for
Namely that xkbcomp reports my device is not eglstream capable, which I believe based on the age of the GPU and the fact my opengl compatibility looks like |
Well, I think that how to enable XWayland should be documented in the README. If your GPU can run sway, I don't see why it shouldn't run dwl. Those glamor and xkbcomp errors don't even seem related. xkbcomp has nothing to do with OpenGL, and if you look up those 2 errors in a search engine you will find them separately in various unrelated issues. Have you tried with other terminals? The sway wiki recommends termite as a Wayland-native terminal, maybe that will work since it's not based on OpenGL. |
I just noticed that I actually get those same glamor and xkbcomp errors myself when I start Xwayland in dwl. They can be ignored. |
My setup --
5.9.10-artix1-1
:dwl
:st
My problem --
Running
dwl
from an existing wayland comp session works just fine (in my casesway
). But running from TTY throws the very unhelpful wlroots errorcan't open display
. At least I assume it's wlroots. In short, from TTY I can get to the dwl gray screen, but no terminal, no dmenu, alt-shift-Q to end my misery.wlroots-nosystemd-minimal-git doesn't seem stable, so I use wlroots-git as directed in #9, but with a similar problem to ntegan's original lack of terminal handling with
alacritty
in my own case withst
...At this point,
wterm
has been all but abandoned (see maintainer's comment in majestrate/wterm#23), which leaves me with very few wayland-only terminal emulators worth pursuing.I've tried a few different iterations of
xwayland
, but that may be unrelated.Is there a reason
st
or other display would be handled fine within a virtual display but not from TTY?The text was updated successfully, but these errors were encountered: