Please confirm the following.
What version of the Modrinth App are you using?
Modrinth App 0.14.6
What operating systems are you seeing the problem on?
Linux
Describe the bug
Overview of the problem
Everyone on linux seems to be having thix exact issue. Whether you download Modrinth using the AppImage, the AUR or through flatpak, when you download a modpack and try clicking on it afterwards the app instantly crashes.
my system specs if needed (but it doesn't not appear to be relevant as I specify below)
OS: 7.0.11-arch1-1
Hyprland (Wayland Compositor)
GPU: Nvidia
NVIDIA-SMI 610.43.02
Driver Version: 610.43.02
CUDA UMD Version: 13.3
How to avoid it as of now :] (exact steps)
I think I pinned down the issue. I don't know if it's a bug but you can avoid it by running these steps.
Let's say that we have 2 profiles, the downloaded one which for me is 'Fabulously Optimized' and a profile I created called 'Test Instance'. Modrinth crashes when I click on Fabulously Optimized but works perfectly fine when I click on Test Instance.
Weirdly, when I copy over the files inside Fabulously Optimized (like mods, configs, resourcepacks etc...) inside 'Test Instance' and start said profile, the app launches the game perfectly fine, so the problem isn't related to the files inside of the downloaded profiles rather the metadata that they need.
So I installed sqlite3 and inspected app.db inside of ~/.local/share/ModrinthApp running "sqlite3 app.db" inside my terminal emulator. I wanted to inspect "profiles" so I ran:
> SELECT *
> FROM profiles
> WHERE name IN ('Fabulously Optimized', 'Test Instance');
and noticed that the only difference between these 2 profiles (apart from the icon path) is this:
'Fabulously Optimized'
linked_project_id = 1KVo5zza
linked_version_id = g5RAIwpP
icon_path = /home/user/.local/share/ModrinthApp/caches/icons/...
install_stage = installed
'Test Instance'
linked_project_id = NULL
linked_version_id = NULL
icon_path = NULL
install_stage = installed
The only logical try was then to set the value of "linked_project_id = 1KVo5zza" and "linked_version_id = g5RAIwpP" of 'Fabulously Optimized' both to "NULL" by running:
> UPDATE profiles
> SET linked_project_id = NULL,
> linked_version_id = NULL
> WHERE name = 'Fabulously Optimized';
Now both profiles work perfectly fine, so the problem is somehow linked to these 2 properties that downloaded profiles have
linked_project_id = 1KVo5zza
linked_version_id = g5RAIwpP
Steps to reproduce
No response
Expected behavior
No response
Additional context
No response
Please confirm the following.
What version of the Modrinth App are you using?
Modrinth App 0.14.6
What operating systems are you seeing the problem on?
Linux
Describe the bug
Overview of the problem
Everyone on linux seems to be having thix exact issue. Whether you download Modrinth using the AppImage, the AUR or through flatpak, when you download a modpack and try clicking on it afterwards the app instantly crashes.
my system specs if needed (but it doesn't not appear to be relevant as I specify below)
OS: 7.0.11-arch1-1
Hyprland (Wayland Compositor)
GPU: Nvidia
NVIDIA-SMI 610.43.02
Driver Version: 610.43.02
CUDA UMD Version: 13.3
How to avoid it as of now :] (exact steps)
I think I pinned down the issue. I don't know if it's a bug but you can avoid it by running these steps.
Let's say that we have 2 profiles, the downloaded one which for me is 'Fabulously Optimized' and a profile I created called 'Test Instance'. Modrinth crashes when I click on Fabulously Optimized but works perfectly fine when I click on Test Instance.
Weirdly, when I copy over the files inside Fabulously Optimized (like mods, configs, resourcepacks etc...) inside 'Test Instance' and start said profile, the app launches the game perfectly fine, so the problem isn't related to the files inside of the downloaded profiles rather the metadata that they need.
So I installed sqlite3 and inspected app.db inside of ~/.local/share/ModrinthApp running "sqlite3 app.db" inside my terminal emulator. I wanted to inspect "profiles" so I ran:
and noticed that the only difference between these 2 profiles (apart from the icon path) is this:
'Fabulously Optimized'
'Test Instance'
The only logical try was then to set the value of "linked_project_id = 1KVo5zza" and "linked_version_id = g5RAIwpP" of 'Fabulously Optimized' both to "NULL" by running:
Now both profiles work perfectly fine, so the problem is somehow linked to these 2 properties that downloaded profiles have
Steps to reproduce
No response
Expected behavior
No response
Additional context
No response