this post was submitted on 20 Jan 2025
24 points (90.0% liked)

Linux Gaming

15884 readers
126 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 2 years ago
MODERATORS
[email protected]
24
[SOLVED] Bazzite: Steam won't launch games from ext4 secondary drive (lemm.ee)
submitted 6 days ago* (last edited 5 days ago) by [email protected] to c/[email protected]
15 comments fedilink hide all child comments
 

I finally took the time to move my gaming rig to Bazzite because I don't boot it that often, and because I don't want to spend half the little time I have for gaming doing updates and maintenance.

Most of my games are on an ext4-formatted secondary drive. Note: They worked perfectly on Manjaro and Nobara, the previous distros I used on this machine.

They are recognized by Steam, I can install and uninstall games just fine, it's just that... they don't launch. At all. Native or Proton. Like if I was on an exFAT partition. The "Launching" button switches back to "Play" almost instantly. If I move a game to my main home partition, it launches fine.

Has anyone encountered this issue before?

Where/how could I get detailed logs to try and pinpoint the issue?

Thanks!

Edit: Solved! The issue was with fstab configuration, always specify exec AFTER users, despite the doc telling you that order doesn't matter ;)

Wrong fstab entry :

UUID=blah-blah-blah /my/mount/point ext4 defaults,noatime,nofail,auto,exec,users,rw 0 2

Proper fstab entry (it's subtle):

UUID=blah-blah-blah /my/mount/point ext4 defaults,noatime,nofail,auto,users,exec,rw 0 2

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 5 days ago (1 children)

The issue was indeed from the fstab. But it was because exec was specified before users.

[–] kugmo 1 points 2 hours ago* (last edited 45 minutes ago)

Late to reply, but you should just leave it as defaults,noatime,nofail. From the mount man page, defaults already implies rw,suid,dev,exec,auto,nouser,async.

EDIT: change it to rw,suid,dev,nouser,exec,auto,async,noatime,nofail actually, anything after defaults overrides the options specified by that.