this post was submitted on 11 Aug 2025
40 points (82.3% liked)

Linux Gaming

20623 readers
329 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.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
 

I have been able to run games whether it was Steam, GOG, or itch and now I can't get shit to run. I don't have the worst rig. I was playing Fo4, and now suddenly I can't. I switched from a shitty Windows to Garuda. That was working wonderful, until I suddenly couldn't get it to work no matter what Proton version. Then I switched to Ubuntu, same issue. Then Cachy, then back to Ubuntu, and now back at it again with Garuda. Still. The. Same. Fucking. Problem. I have scoured the net for answers and fixes to no avail and I feel like driving into traffic. I cannot get any Proton version to run ANY GAME at this point, not just the more intensive ones. What the fuck do I do? Here are some specs:

  • Processor: 8 x Intel Core i7-2600 CPU @ 3.40Ghz
  • Mem: 32 GiB RAM
  • Graphics Processor: Quadro K620
  • Dell Optiplex 990 (7010 housing)
  • 245GB SSD, with additional 500GB HDD and 4TB external drive

I have been able to seamlessly play all kinds of games for months, and then it just up and doesn't let me anymore. I haven't done anything to tweak shit out of whack. No matter how many clean installs and following instructions otherwise, this shit feels BROKEN and I'm LOSING IT. Someone help me please.

-Little extra info, I always skip the Vulkan shaders bullshit and it was fine before. Sometimes it'd load with the "Downloading Windows (somethingsomething), but I don't get that anymore, and as soon as I skip the thing crashes before any launchers of sorts can load so I can mess with configuration with the little GUI bullshit before total launch.

  • UPDATE:

I have switched to Bazzite and have set my external drive to ext4. Shit seems to work seamlessly now. Thank you all very much.

you are viewing a single comment's thread
view the rest of the comments
[–] FauxLiving@lemmy.world 24 points 4 days ago* (last edited 4 days ago) (2 children)

Don't worry dude, we'll get you sorted.

I could ask you a bunch of questions about your system, but it's easier if you just use inxi:

inxi -Fz

You may have to install it first with your package manager. It'll output your full system information (-F) with personal data removed (-z).

Also, close steam, open a terminal emulator and run:

steam -d

Steam will launch and output debugging info into that terminal window. If you close the window it will exit steam.

When you run a game and it fails, look at the log and see if you see any errors or crashes being reported.

Note which version of Proton that you're using (if not default).

[–] fleebleneeble@reddthat.com 12 points 4 days ago* (last edited 4 days ago) (2 children)

Here's what I got:

System:
Kernel: 6.15.9-zen1-1.1-zen arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.4.4 Distro: Garuda Linux
Machine:
Type: Desktop System: Dell product: OptiPlex 990 v: 01
serial: <superuser required>
Mobo: Dell model: 06D7TR v: A02 serial: <superuser required> BIOS: Dell
v: A24 date: 07/02/2018
CPU:
Info: quad core model: Intel Core i7-2600 bits: 64 type: MT MCP cache:
L2: 1024 KiB
Speed (MHz): avg: 2072 min/max: 1600/3800 cores: 1: 2072 2: 2072 3: 2072
4: 2072 5: 2072 6: 2072 7: 2072 8: 2072
Graphics:
Device-1: NVIDIA GM107GL [Quadro K620] driver: nvidia v: 575.64.05
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64.05
renderer: Quadro K620/PCIe/SSE2
API: Vulkan v: 1.4.321 drivers: nvidia,llvmpipe surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX]
driver: snd_hda_intel
API: ALSA v: k6.15.9-zen1-1.1-zen status: kernel-api
Server-1: PipeWire v: 1.4.7 status: active
Network:
Device-1: Intel 82579LM Gigabit Network driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: wlp0s29u1u2i2 state: down mac: <filter>
IF-ID-2: wlp0s29u1u6i2 state: down mac: <filter>
Bluetooth:
Device-1: Realtek 802.11ac NIC driver: btusb,rtw_8821cu type: USB
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: N/A
Report: btmgmt ID: hci1 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: N/A
Device-2: Realtek 802.11ac NIC driver: btusb,rtw_8821cu type: USB
Drives:
Local Storage: total: 4.33 TiB used: 2.31 TiB (53.4%)
ID-1: /dev/sda vendor: SK Hynix model: SH920 2.5 7MM 256GB
size: 238.47 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD5000AZLX-75K2TA1
size: 465.76 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD40NDZW-11BCVS0
size: 3.64 TiB type: USB
Partition:
ID-1: / size: 238.47 GiB used: 46.71 GiB (19.6%) fs: btrfs dev: /dev/sda1
ID-2: /home size: 238.47 GiB used: 46.71 GiB (19.6%) fs: btrfs
dev: /dev/sda1
ID-3: /var/log size: 238.47 GiB used: 46.71 GiB (19.6%) fs: btrfs
dev: /dev/sda1
ID-4: /var/tmp size: 238.47 GiB used: 46.71 GiB (19.6%) fs: btrfs
dev: /dev/sda1
Swap:
ID-1: swap-1 type: zram size: 31.29 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 36.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.29 GiB used: 3.69 GiB (11.8%)
Processes: 316 Uptime: 46m Shell: fish inxi: 3.3.38
[–] FauxLiving@lemmy.world 16 points 4 days ago

Nothing stands out as being wrong here.

It's detecting your graphics card, you're using the latest versions of the graphics driver, wayland and vulkan and your GPU architecture is supported.

That's good because these kinds of problems are much more annoying to deal with.

[–] tal@lemmy.today 5 points 4 days ago

Not disk space exhaustion.

[–] fleebleneeble@reddthat.com 9 points 4 days ago (1 children)

With the steam - d bit:

  • game stopped [gameid=377160]
  • removing process 304830, 304829, 304828 for (gameid aforementioned)
[–] FauxLiving@lemmy.world 7 points 4 days ago (1 children)

That's basically the normal thing Steam does with an application is closing.

What version of Proton are you using in Steam Settings -> Compatibility -> Default compatibility tool?

[–] fleebleneeble@reddthat.com 7 points 4 days ago (1 children)

It's usually Experimental, but I've played around with others to set as default. Most recent was 8.0-4 since that's what Fo4 usually likes.

[–] FauxLiving@lemmy.world 17 points 4 days ago

Ah.

Try using GE-Proton-10-11, it's a community build of Proton using the latest patches and fixes (it updates a lot more frequently than Valve's proton). Another big advantage here is that you can use Wayland directly, bypassing the xwayland layer which will eliminate one possible thing that can go wrong.

You can install it using 'ProtonUp-Qt', which should be available on your package manager. When you run it, just click the Add version, select GE-Proton10-11 and click install. It'll download it and put it in the proper directory, you'll have to restart Steam for it to show up in Steam's list. Set it to the default (either in Steam Settings, or in the settings of whatever game you're using).

Once you have GE-Proton10-11 selected for the game, go into the launch options for the game (Properties -> General) and put:

PROTON_ENABLE_WAYLAND=1 %command%

This will tell Proton to directly output to Wayland. If your monitor supports HDR and you have enabled HDR in Plasma's display configuration, you can enable HDR support by adding PROTON_ENABLE_HDR=1. So,

PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%

Wayland and HDR support only work after Proton10 so make sure you select the right version of Proton.