Flatpak doesn't start on arch

Frill7742 commented 2 months ago

Please confirm the following.

[X] I checked the existing issues for duplicate problems
[X] I have tried resolving the issue using the support portal
[X] I have ensured my Modrinth App installation is up to date

What version of the Modrinth App are you using?

Branch: stable | Version: 0.8.2

What operating systems are you seeing the problem on?

Linux

Describe the bug

If I install modrinth on arch via a flatpak image it doesn't start. It just fails and give without the -v flag no error. The “Error” with the -v-flag:


[alex@Arschy ~]$ flatpak run -v com.modrinth.ModrinthApp
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/alex/.local/share/flatpak
F: Opening user flatpak installation at path /home/alex/.local/share/flatpak
F: Opening user flatpak installation at path /home/alex/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: /var/lib/flatpak/runtime/org.gnome.Platform/x86_64/46/9137a2d4c8f90d206bd02adc971886c29429e8cef83394b2317c02a9263f9acd/files/lib32 does not exist
F: Cleaning up unused container id 934891929
F: Cleaning up per-app-ID state for com.github.tchx84.Flatseal
F: Allocated instance id 743705312
F: Add defaults in dir /com/modrinth/ModrinthApp/
F: Add locks in dir /com/modrinth/ModrinthApp/
F: Allowing wayland access
F: Allowing x11 access
F: Allowing pulseaudio access
F: Pulseaudio user configuration file '/home/alex/.config/pulse/client.conf': Error opening file /home/alex/.config/pulse/client.conf: No such file or directory
F: Running 'bwrap --args 42 -- xdg-dbus-proxy --args=45'
F: Running 'bwrap --args 42 -- modrinth-app'
``

### Steps to reproduce

1. Install arch Linux
2. Try to download and install modrinth
3. Try to launch modrinth

### Expected behavior

It should start normaly.

### Additional context

_No response_

ThatKid1351 commented 2 months ago

Same issue on Fedora 40

ThatKid1351 commented 2 months ago

Similar information mentioned in #2289

Eaterminer commented 3 weeks ago

Can you try again and check dmesg for segfaults? Theres a related issue in flathub/com.modrinth.ModrinthApp (Flathub repo) that breaks NVIDIA drivers

modrinth / code