Modrinth 0.6.3 will not launch on Wayland, Ubuntu 23.04

[xendyex]

Describe the bug

Modrinth 0.6.3 Launcher does not launch ( appImage or deb ) on Wayland, only Xorg, but 0.6.2 did.

Steps to reproduce

1. Log out of your Ubuntu Machine
2. Switch to Wayland ( the cog in the bottom right when you click your profile, 'Ubuntu' )
3. Launch 0.6.3

Expected behavior

It launches, and shows the home.

System information

Ubuntu 23.04 Theseus 0.6.3 Wayland Gnome 44 Intel Celeron N4120x4

Additional context

Launching from both a .desktop and appImage results in this. I'd prefer not to use Xorg as it gives me less FPS, resulting in even more unplayable ( without 47 mods ) minecraft.

[ZtereoHYPE]

I also am having issues running the version downloaded from modrinth.com, as when I try to launch the AppImage I get the following error:

(modrinth-app:198831): GLib-GIO-ERROR **: 17:33:19.576: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

However, building from the repository (master branch, cd'd in theseus_gui) with npm run tauri build works flawlessly.

Fedora 39, Wayland system.

[xendyex]

I also am having issues running the version downloaded from modrinth.com, as when I try to launch the AppImage I get the following error:

(modrinth-app:198831): GLib-GIO-ERROR **: 17:33:19.576: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

However, building from the repository (master branch, cd'd in theseus_gui) with npm run tauri build works flawlessly.

Fedora 39, Wayland system.

Any good guides for building? I'm not that technical.

[akirapink]

(modrinth-app:198831): GLib-GIO-ERROR **: 17:33:19.576: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

having the same issue here!

[triphora]

As a temporary workaround, you can specify the GDK_BACKEND environment variable to x11. In other words:

$ GDK_BACKEND=x11 ~/path/to/Modrinth-App.AppImage

I will add this to the docs.

[xendyex]

As a temporary workaround, you can specify the GDK_BACKEND environment variable to x11. In other words:

$ GDK_BACKEND=x11 ~/path/to/Modrinth-App.AppImage

I will add this to the docs.

Can I do this without a terminal? Otherwise I can't close the Modrinth launcher when playing to then get more FPS...

[ZtereoHYPE]

As a temporary workaround, you can specify the GDK_BACKEND environment variable to x11. In other words:

$ GDK_BACKEND=x11 ~/path/to/Modrinth-App.AppImage

I will add this to the docs.

Can I do this without a terminal? Otherwise I can't close the Modrinth launcher when playing to then get more FPS...

If you have a .desktop file to launch the program then you can add the flags to that so they automatically apply whenever you launch the app

[Lampe2020]

If you have a .desktop file to launch the program then you can add the flags to that

On my computer it didn't work to just insert that envvar in the beginning of the command in the .desktop file, I had to change the command to bash -c "export GDK_BACKEND=x11; /path/to/Modrinth.AppImage".

[Legion495]

May I also add a potential workaround posted here since I ran into it on Fedora. I think this is Gnome Specific. https://github.com/modrinth/theseus/issues/880#issuecomment-1872568648

GLib-GIO-ERROR **: 16:48:12.495: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

A workaround is to edit (vi/nano/or any editor): sudo micro /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.xsettings.gschema.xml And alter the line where it says deprecated. I simply removed the deprecated... sudo glib-compile-schemas /usr/share/glib-2.0/schemas And now the appimage will work.

I would much more prefer a Flatpak to avoid all of this. I would think Ubuntu has the same issue.

[Lampe2020]

I did that and now I get a different error on launch, modrinth-app: symbol lookup error: /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_proxy_marshal_flags.
Any idea on that?

[DioEgizio]

While searching for this issue online found basically the same issue but from 2021 and related to the bottles appimage here on the appimage discourse, while here from their GitHub issues page, so this probably means it's something with gtk in general. The creator of appimage hates Wayland and has had very weird takes about it so I don't think it'll be fixed upstream anytime soon

[Legion495]

This 100% and Distros and DEs already announced going Wayland by now. We can expect many more will announce it this year.

This guy: https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277 https://github.com/probonopd/wayland-x11-compat-protocols/

And this was KDEs recent post about Wayland: https://pointieststick.com/2023/12/26/does-wayland-really-break-everything/

Either way. The Application should be moved to another packaging format because I am certain more issues will come up.

[JulianVennen]

Tauri also disables Wayland in the AppImage by default in newer versions, causing it to fall back to XWayland: https://github.com/tauri-apps/tauri/issues/8541

Maybe updating Tauri would be a good idea?

[catvin82]

saw this and will try to build from source, but triphora's fix doesn't work without sudo for me I have an issue like this on #981

[leo60228]

Does this issue still occur? It seems like the root cause of this issue is a mismatch between the GTK3 version and running gnome-settings-daemon (which is seemingly unsupported), but the AppImage is now built on Ubuntu 22.04 which includes GTK 3.24.

[Lampe2020]

I tested on Fedora 41 with KDE Plasma 6.2 and it seems to now automatically start with Xwayland by default instead of trying to go Wayland-native, judging by xeyes being able to follow the cursor over Modrinth but not any Wayland-native window.
It fixes the issue of not getting any output for me but is probably not the desired long-term solution.