-
Notifications
You must be signed in to change notification settings - Fork 11
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
Wayland support or documentation addition? #41
Comments
I seen you were in the Discord, but, essentially it's most likely a bug with Tauri, which is the library we use (similar to Electron). Not sure what can be done about it for now unfortunately, other than that flag. |
I'm having an issue that may or may not be related. When I launch YARC Launcher from SteamOS's Game Mode (which is using the Gamescope Wayland compositor) on my Steam Deck it shows up as a blank white window and I can't seem to do anything. It launches fine in Desktop Mode (KDE Plasma, and according to |
I'm not sure exactly how Steam Deck handles applications, but if it launches fine in Desktop Mode then it's probably a separate issue, unfortunately.
With how the launcher works, the majority of the updater is written in TypeScript, so the launcher would have to load properly in order for that to work, sadly. |
I also forgot to mention, as you have just reminded me: @ajrichins, can you test whether or not the newest launcher version fixes this issue? According to a Tauri issue (tauri-apps/tauri#8541), it should be fixed with a rebuild. Sorry, I don't have a Linux machine anymore to test. |
@EliteAsian123 sorry it took so long, but it works now! thank you |
using ubuntu 22.04, gnome 42.9 with Wayland.
when running the yarc-launcher, I get this error
(yarc-launcher:574632): GLib-GIO-ERROR **: 22:41:20.783: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
Trace/breakpoint trap (core dumped)
seems like it might be a wayland support thing from a brief search, but I was wondering if y'all were already aware and had a fix other than using xorg or using the GDK_BACKEND=x11 flag solution found in said issue (both of which work btw).
Would be very sad if this is just another wayland/xorg compatibility bug, but if it is so, I'll add it to documentation
The text was updated successfully, but these errors were encountered: