Skip to content
This repository has been archived by the owner on Jan 26, 2024. It is now read-only.

TTY display failure #67

Closed
GregCM opened this issue Dec 5, 2020 · 5 comments
Closed

TTY display failure #67

GregCM opened this issue Dec 5, 2020 · 5 comments
Labels
A: bug Something isn't working B: not applicable Resolution: not a valid issue

Comments

@GregCM
Copy link

GregCM commented Dec 5, 2020

My setup --
5.9.10-artix1-1 : dwl : st

My problem --
Running dwl from an existing wayland comp session works just fine (in my case sway). But running from TTY throws the very unhelpful wlroots error can'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 with st...

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?

@guidocella
Copy link
Contributor

guidocella commented Dec 6, 2020

Uncomment CFLAGS += -DXWAYLAND in config.mk and run make clean; make.

@GregCM
Copy link
Author

GregCM commented Dec 6, 2020

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 dwl on my machine:

glamor: No eglstream capable devices found
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.

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 OpenGL version string: 2.1 Mesa 20.2.3

@guidocella
Copy link
Contributor

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.

@Ordoviz
Copy link

Ordoviz commented Dec 7, 2020

@GregCM I get the same error every time I start river. Don’t worry about it.

@guidocella
Copy link
Contributor

I just noticed that I actually get those same glamor and xkbcomp errors myself when I start Xwayland in dwl. They can be ignored.

@djpohly djpohly added A: bug Something isn't working B: not applicable Resolution: not a valid issue labels Mar 6, 2021
@djpohly djpohly closed this as completed Mar 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A: bug Something isn't working B: not applicable Resolution: not a valid issue
Projects
None yet
Development

No branches or pull requests

4 participants