Modrinth self-terminates when trying to export a Modpack

1

I tried launching it through wine so I could get debug info, and got this:

(Z:\nix\store\jxp9kyzxb4w6rsvk505f98s7qah4p2kf-modrinth-app-0.9.5\bin\ModrinthApp:13595): GLib-GIO-ERROR **: 17:14:11.626: No GSettings schemas are installed on the system

I have installed the package by putting whatever this is in my environment.systemPackages:

 (pkgs.modrinth-app.overrideAttrs (oldAttrs: {
  buildCommand =
    ''
      gappsWrapperArgs+=(
         --set GDK_BACKEND x11
         --set WEBKIT_DISABLE_DMABUF_RENDERER 0
      )
    ''
    + oldAttrs.buildCommand;
}))

(This is basically required to make it render properly)

I also found something on StackOverflow
(https://stackoverflow.com/questions/28953925/glib-gio-error-no-gsettings-schemas-are-installed-on-the-system)
about some unrelated programs having this issue but I’m not quite sure how to fix it in this context.

I’m using NixOS Warbler 25.05.804391.b2485d569675 on KDE Plasma 6.

Any ideas? AMA! :3

1 Like
2

I’ve tried installing glib to run glib-compile-schemas but it just says

“glib-compile-schemas” is not in your PATH. You can make it available in an ephemeral shell by typing: nix-shell -p glib

even though I’ve added glib to my pkgs?

anyway I did

nix-shell -p glib

and then

glib-compile-schemas .

but then it just says

No schema files found: doing nothing.

??? Help pls ;-;

3

Update: It works fine on GNOME Apparently?

A friend of mine temporarily switched over to test it and yeah, it just works on there.

Is there a way to find what exactly makes Modrinth work in one desktop environment instead of another? I’m not really interested in switching over to GNOME for this single program lol.

Maybe some way to track what Modrinth is “touching”?

4

huh. not really a fan of unfree stuff, which modrinth is, but my best guess would be the fact that a gnome environment, services.desktopManager.gnome.enable, enables programs.dconf.enable, which controls GSettings. it also does some other stuff related to xdg.portal.*… what is your non-gnome desktop environment? i can see that it’s an X11 one?

also, mind if i ask, why modrinth?

5

I am currently running KDE Plasma 6 Wayland, and as for “why Modrinth”

  1. I’m not aware of a FOSS alternative that fits what I want (which is basically Modrinth but FOSS lol).

  2. I want to develop a modpack, and the people I’m making it for are all on Modrinth, not to mention they’re not exactly tech-savvy. So while I wouldn’t mind switching to a different program, they would lol. (Notably they’re also on Windows 10, 11, and MacOS, not sure if that means anything)

  3. In order to upload a modpack to Modrinth, you need Modrinth to make the modpack file. Currently that is one of the only things that are actually broken with the program, and the other things report the same error.

6

damn. well, ive never created a public modpack for minecraft, buuut i thought the way it works is: you get a client, e.g. pkgs.prismlauncher, you Add Instance with a Modrinth Modpack, which you have created previously on the Modrinth website, and that would be it. can you please elaborate on why do you need to Export it? like, did i get that right, not Import, but Export? as in, you want to share this modpack as an archive? :crazy_face: is it not possible to do that manually? sorry, i thought this wasnt this confusing!

also, yeah, modrinth is open source, its just that its license is not very cool…

7

Yes I want to export it.

What this does (If it’s anything like the ThunderStore mod manager on Overwolf I used when I was on Windows 10 ~2 months ago) is it creates a unique code that somehow encapsulates:

  1. What mods/texture packs/datapacks the modpack contains.

and

  1. The config files for each of those mods.

This code is put in essentially a text file (I think) but I don’t know how it’s made so I need Modrinth itself to generate it.

Why do I need this code? Because it’s required to upload a modpack to Modrinth -_-

I want to upload it so when I push an update to it, I don’t have to send a zip to everyone that’s using it because that’s a pain!

The only thing holding me back at this point is this one button that for whatever reason wants a GSettings schema lol

8

Another thing I like about Modrinth is that it is also a launcher, and a fast one at that, HUGE improvement over the official one, and you can build your modpacks on it!

Just overall my fav :3

Also: It appears simply enabling dconf doesn’t do anything unfortunately ;-;

9

oh.

(pkgs.modrinth-app.overrideAttrs (oldAttrs: {
  buildCommand =
    ''
      gappsWrapperArgs+=(
         --set GDK_BACKEND x11
         --set WEBKIT_DISABLE_DMABUF_RENDERER 0
      )
    ''
    + oldAttrs.buildCommand;
}))

plasma on wayland, you say? what’s that then? you’re building it for x11. you’re probably launching it via xwayland, mate. or am i wrong? :crazy_face:

actually, where did you get this piece of code? what’s “not rendering” properly? :nerd_face:

10

Modrinth reeeeealy doesn’t like Wayland, so I have to do that.

Also adding this:

–prefix XDG_DATA_DIRS : “${gtk3}/share/gsettings-schemas/${gtk3.name}”

to here:

 (modrinth-app.overrideAttrs (oldAttrs: {
  buildCommand =
    ''
      gappsWrapperArgs+=(
         --set GDK_BACKEND x11
         --set WEBKIT_DISABLE_DMABUF_RENDERER 0
         --prefix XDG_DATA_DIRS : "${gtk3}/share/gsettings-schemas/${gtk3.name}"
      )
    ''
    + oldAttrs.buildCommand;
}))

Fixes everything :3

1 Like