-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No GUI on Wayland #24
Comments
Please run this command in a console:
Then copy/paste the full output here, and attach a copy of your |
Hmm, I don't see any errors in there. Some questions for you:
|
That's strange. My guess is that this is either a problem in the Winit library or an issue with your graphics drivers. To narrow it down, would you be willing to try the Winit examples? You would just need to install Rust and then run the following (this tests both the latest version and the version used by Ludusavi):
Output should look like this: |
Thanks. I took a look through some Winit tickets, and apparently that's normal since their examples don't draw anything inside of the window, and Wayland doesn't show the window until something inside is drawn. But there aren't any errors in your console output, so that's good at least. The next question would be if there's an issue in Iced. One thing to note is that currently Ludusavi uses Iced with OpenGL, but Iced's next release is dropping OpenGL in favor of WebGPU (plus a software renderer fallback). If we're lucky, maybe those will end up helping here. To test it:
This is how it should look: |
Nice! So there's something going wrong with OpenGL specifically, but it'll be fixed by switching to WebGPU before too long. As soon as the next Iced release comes out, I'll update Ludusavi to use it. I'll leave this ticket open in the meantime. I found some threads talking about the
One comment said that it's fixed in Mesa 18.x drivers, but that doesn't seem to be the case for everyone, and some comments suggested that there may be limitations around older hardware and virtual machines. |
Cetere... ĉu vi parolas Esperanton? Mi demandas al vi pri tio, pro la nomo de via aplikaĵo. 😅 |
I don't speak it (unfortunately), but I do have an interest in linguistics :) The name comes from Latin |
Ha, bone! The Esperanto language has many roots in Latin. That's why I thought about it. Ĝis, kara! |
Do, mi proponas al vi esperantigi la nomon de via aplikaĵo: lud-sav-il-o xD |
Hey, sorry for writing here again, but seems like I have the same issue. |
@BLACK4585 I think it's normal that there's no console output, since that would be if it crashed outright. Could you send me a copy of If you're willing to install Rust, you could try running the examples from Iced to verify how it behaves in isolation and whether the latest development version behaves better:
|
I just tested the iced examples and they also stay black. I got this error in another app, but sadly I don't remember anymore which app it was. |
Hmm, it could be an issue either in your drivers or in Winit, but it's hard to say. You could try opening a ticket in the Winit repo and see if they have some idea. That's beyond my area of expertise 😅 As a workaround, you could try forcing X11 for Ludusavi:
|
Mhh also the workaround doesn't work. |
Looks like Winit checks some environment variables to determine if it should use Wayland. Could you try this?
(It also needs the |
Also doesn't help, I will ask the Nobara Community once more, I really think this is because of NVIDIA somehow.. |
No GUI on Wayland. On X11 works.
The text was updated successfully, but these errors were encountered: