Faliure to find GLFW profile

[Ferrum115]

Operating System

Linux

Version of Prism Launcher

Prism Launcher 9.4 (Freesm Seqoia 1.4.4)

Version of Qt

Qt 6.8.3

Description of bug

Minecraft 1.21.1 (Neoforge latest) isn't launching (yes, I've tried making new instances and no-mod launch) because of faliure to find "suitable GLFW profile"

Steps to reproduce

1. Install CachyOS (latest) with Hyprland (also latest) [if its relevant to launching Freesm on linux]
2. Install Freesm Launcher from github flatpak (x86_64)
3. Add instance -> mc ver: 1.21.1, neoforge ver: 21.1.216 (latest)
4. run that instance
5. look at the error message
   error message:
   Failure details:
   Failed to find a valid GLFW profile.
   _We tried 4.6, 4.5, 4.4, 4.3, 4.2, 4.1, 4.0, 3.3, 3.2 but none of them worked.
   Trying 4.6: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 4.5: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 4.4: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 4.3: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 4.2: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 4.1: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 4.0: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 3.3: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig
   Trying 3.2: GLFW error: [0x10009]GLX: Failed to find a suitable GLXFBConfig

If you click yes, we will try and open https://links.neoforged.net/early-display-errors in your default browser_

Suspected cause

suspects:

1. GLFW location isn't constant
2. Hyprland's shaders break configs (very unlikely, this error disappears after launcher reinstallation, but it appears again after updates/reboots)
3. GLFW configs are being saved in temporary folders (or cache), so they are being deleted after reboots/updates

This issue is unique

• I have searched the issue tracker and did not find an issue describing my bug.

[notwindstone]

The only solution I know is not to use flatpak.

For some reason, flatpak users of Prism Launcher face this issue occasionally. They reported the problem to Prism devs several times, yet they did not get any response. You might open the same issue in Prism Launcher repository to see if the devs will respond this time though