[(Pretty much) solved] Can’t get LM Studio to work on OpenSUSE Leap 16

2026-04-09 19:23 UTC

Solution: download an earlier version of the LM Studio AppImage. Or 0.4.6-1, which works better for me. I recently bought a new computer, and, after again trying Windows 11 for a bit, I decided I wanted to keep using OpenSUSE. Probably unpopular here: I enjoy screwing around with local LLM models. I used LM Studio on my old computer (on which I had also installed OpenSUSE Leap). I also tested it on my new computer in Windows 11, and it worked very nicely. Now I’m trying on my new computer with OpenSUSE Leap 16, and it doesn’t work at all. Specifically: no runtimes nor engines are present, and my hardware isn’t recognised at all - not my GPU nor my CPU, nothing. I’m thinking it’s a driver issue. I’ve looked around quite a bit, and also looked up (what seems to me) the most important error messages I got when running the AppImage from the console: spoiler [BackendManager] Surveying hardware with backends with options: {“type”:“newAndSelected”} [BackendManager] Surveying new engine ‘llama.cpp-linux-x86_64-avx2@2.12.0’ [ProcessForkingProvider][NodeProcessForker] Spawned process 13407 [ProcessForkingProvider][NodeProcessForker] Exited process 13407 21:17:29.644 › Failed to survey hardware with engine ‘llama.cpp-linux-x86_64-avx2@2.12.0’: LMSCore load lib failed - child process with PID 13407 exited with code 127 [BackendManager] Survey for engine ‘llama.cpp-linux-x86_64-avx2@2.12.0’ took 9.47ms [BackendManager] Surveying new engine ‘llama.cpp-linux-x86_64-nvidia-cuda-avx2@2.12.0’ [ProcessForkingProvider][NodeProcessForker] Spawned process 13408 [ProcessForkingProvider][NodeProcessForker] Exited process 13408 21:17:29.648 › Failed to survey hardware with engine ‘llama.cpp-linux-x86_64-nvidia-cuda-avx2@2.12.0’: LMSCore load lib failed - child process with PID 13408 exited with code 127 [BackendManager] Survey for engine ‘llama.cpp-linux-x86_64-nvidia-cuda-avx2@2.12.0’ took 3.70ms [BackendManager] Surveying new engine ‘llama.cpp-linux-x86_64-vulkan-avx2@2.12.0’ [ProcessForkingProvider][NodeProcessForker] Spawned process 13409 [ProcessForkingProvider][NodeProcessForker] Exited process 13409 21:17:29.651 › Failed to survey hardware with engine ‘llama.cpp-linux-x86_64-vulkan-avx2@2.12.0’: LMSCore load lib failed - child process with PID 13409 exited with code 127 [BackendManager] Survey for engine ‘llama.cpp-linux-x86_64-vulkan-avx2@2.12.0’ took 3.57ms This is my system with installed drivers: I did get Ollama to work… Any thoughts?

Replies (4)

@moonpiedumplings@programming.dev 2026-04-13 07:26

Okay, I hath returned. So I used to play a game called krunker.io. It was browser game, but I would use a native, electron based client. I spent a lot of time tinkering to figure out what options would maximize performance, and because I had a laptop with an Nvidia gpu, a few special flags were needed. Here was the full command that I would run to run the client: gamemoderun prime-run ./crankshaft-portable-linux-x86_64.AppImage -no-sandbox --ignore-gpu-blocklist --enable-gpu-rasterization --enable-native-gpu-memory-buffers --enable-zero-copy --disable-gpu-vsync --disable-frame-rate-limit --ozone-platform-hint=wayland > /dev/null 2>&1 You probably don’t want gamemoderun. But you can play with the rest of the flags there. I don’t remember what was needed and what was there for performance. I’m pretty sure that the first two arguments there were needed though.

Open ##1122061
@m33@lemmy.zip 2026-04-09 19:42

I use lmstudio too, from the official appimage. Never managed to get the nvidia working, probably because the nvidia drivers are a pain to install properly (secure boot, drivers, kernel, display … everything must be perfect or it doesn’t work). But the CPU is just enough for local models if you are a bit patient and have plenty RAM. It is very unusual for lmstudio failing to detect your CPU and your system memory. I would start looking for excessive restriction affecting lmstudio itself (appimage ? Native ? Something with selinux or system hardening ?)

Open ##1178760
@moonpiedumplings@programming.dev 2026-04-10 03:31

I know this issue, I had a similer issue trying to get the client for krunker.io working with my nvidia gpu. I might have the solution saved somewhere, this comment is so I can remind myself to check.

Open ##1178761
@just_another_person@lemmy.world 2026-04-09 20:48

This looks like a sandboxing issue. Using the "no-sandbox" flag has never worked on AppImage from what I remember, except for very light runtimes. Running with sudo will throw that error because the root user has no display manager running. Just try running the installer if you don't want to mess around with debugging the AppImage. Check the GitHub Issues for related keywords and see if others are running into the same issue, maybe it's just a specific release, or SELinux causing the problem.

Open ##1178762