GL_INVALID_FRAMEBUFFER_OPERATION
just have built stardust and it shows the error right after run:
what do i wrong?
22 Replies
you didn't
does this appear to actually affect anything or is it just an annoyance?
i just see monado's black empty window
monado's empty is generally gray
try running a stardust client
the black window probably is not what should i see, so i guess it affected
so, seeing black window is ok until i run something more? Right?
no you would see a black window
yea
ah, ok. sorry, i thought empty screen is a bug 😄
no problem haha
I've tried to launch some wayland clients like nautilus by passing the env var
WAYLAND_DISPLAY=wayland-1
. Also, I've tried to launch Flatland. None of these shows anything. Just a black Monado's window and huge amount of errors in the log of stardust. Looks like errors generated on every frame. In the same time, I can stop stardust and run xrgears. It works.
startup log messages
Could libEGL warning be related?you need to launch flatland and the wayland app at the same time
though yes, libegl warning is probably the issue :p
Just have tried. Nothing.
yep that's libegl
this is a graphics driver issue
not stardust
I've found the magical commands that help to run something.
I can run flatland with these env vars:
I guess, as a result, smithay changes its rendering backeng from gles to egl. Though it still spits another bunch of errors, at least it allows showing a window.
Then I can run Flatland with
cargo run
that doesn't show anything.
Next any wayland client renders its window inside stardust if run with
WAYLAND_DISPLAY=wayland-1
I'm glad to see that small step, but where is mouse input? Is it implemented?
The mouse input only works in flatscreen mode.yes
you need to use the
non-spatial-input
repo
read its READMEok, thanks, i'll look into it
@Skull
This thread
As always, nvidia being fun