this post was submitted on 06 Dec 2023
41 points (100.0% liked)

Linux Gaming

15388 readers
69 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 1 year ago
MODERATORS
monolalia
41
Most games installed on my main OS drive refuse to launch. Proton issue or something else? (self.linux_gaming)
submitted 1 year ago* (last edited 1 year ago) by revolverunit to c/linux_gaming
11 comments fedilink hide all child comments
 

It seems to mostly happen to 3D games, very rarely for 2D ones.

Normally, this wouldn't be much of an issue for me since I install everything to secondary SSDs anyways, but the one piece of software that is driving me up a wall is Steam VR, since its installation folder can't be moved.

I could find plenty of fixes when it came to the opposite problem (launching games from another drive) but nothing for my situation.

Any solutions or even just point me in the right direction where to start when it comes to troubleshooting something like this?

OS: Endeavour OS

GPU: RTX 2070 (latest Nvidia drivers)

CPU: Ryzen 2700X

Happens on both X11 and Wayland environments and everything is up-to-date

Edit: also this seems to happen with every version of Proton

you are viewing a single comment's thread
view the rest of the comments
[–] revolverunit 5 points 11 months ago (1 children)

Thank you, actually having a log to go through was very useful! Kinda. I managed to suss out that vkBasalt was having a config issue, which I eventually fixed. Now all my OS drive games seem to launch fine, except SteamVR (still).

I was able to do a little more research with info from the log and I found out running SteamVR the usual way was broken. Launching Steam from /usr/lib/steam/ makes it...sorta work.

Yeah, turns out it happened to be a separate issue from my initial problem, but with the same symptoms.

[–] [email protected] 3 points 11 months ago

Thanks for the closure. I was real curious about this one.