While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations: 
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
Patreon. Plain Donations: PayPal.This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Oh dear - ARC Raiders was logging your private Discord chats [updated]
- California law to require operating systems to check your age
- Ubuntu and Fedora devs comment on California's new Digital Age Assurance Act
- Valve reconfirm the Steam Frame, Steam Machine and Steam Controller are due in 2026
- SteamInputDB is a new site to help you find Steam Input configurations for your gamepads
- > See more over 30 days here
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam DeckRecently Updated
Linux Distribution: Pop!_OS
Desktop Environment: GNOME
Graphics Card: Nvidia RTX 2070 Super (Founders)
GPU Driver Version: 455.38
Have you checked for system updates?: [Yes]
[Gist](https://gist.github.com/HellsBells24/8a3ea7bdbd0b5e476219c8fa2582c6fe)
You can note your issue below here
I recently loaded Pop!_OS onto a gaming PC I built with the intent of running DVDs and everything that can be run on Proton on the Linux side, and Blurays and games that won't play nice on the Windows side. Since under taking this project, I've run into issues with two games that I've successfully run on previous Linux boxes and are classified Platinum by ProtonDB.
Wolfenstein 3D is the lesser of the two; it runs when Steam is not in Big Picture mode, but crashes upon "Press Any Key" if it is in Big Picture mode. I'm rarely out of BPM, and this issue does not seem to occur with other DOSBox games from iD Software, so if a fix is out there I'd love to hear it but it's not the end of the world if there isn't.
My bigger issue is Call of Duty 4 Modern Warfare (the original), which upon launch attempts First Time Setup, bringing up some sort of Punkbuster dialogue that subsequently fails, followed by a pop up reading "Application Load Error (0x02)." I've tried different Proton versions, validating content, uninstalling, reinstalling, even booting Windows, installing there, and then moving the files over to my Linux partition, all of which have failed to successfully launch the game
Note any particular steps to reproduce it below here
Simply attempting to run either game results in the described issues (I did attempt to run CoD4 outside of BPM after my Wolf3d discovery, to no avail).
Thanks in advance for any help that can be provided!
My thinking was since Ultimate Doom/Doom II/Final Doom are whitelisted games that run via DOSBox, Wolf3d would run without issue. Obviously this was not the case and I've set a launch command to run ECWolf whenever I play Wolf3d. Runs fine, can run some mods as well, only thing is it seems to slow a tad when I pick something up.
Hopefully a solution presents for CoD!
You could you try running Steam from a terminal, and see if it outputs any useful information when you attempt to start the game. Try running the game with different Proton versions. And verify integrity of the game files (in the properties dialog) just in case something got borked and needs to be re-downloaded.
Also just to be sure that your graphics setup is correct, have you confirmed that native games, such as Counter-Strike: Global Offensive, work?
Strafe, Quake II RTX, Bioshock Infinite, and Shadow of War run on my machine without issue.
I have it installed, my Steam, GoG, and Humble Bundle info is all there. I went to the website and insisted that I wanted to install via Steam. When I did this for Doom 3 BFG, it installed on Steam exactly as any other game would, on the hard drive I have set aside for Linux games, and can be launched from steam. When I attempted CoD just now, a new steam instance popped up over my existing one, and asked if I wanted to install the game on drive "C:\," which obviously doesn't exist on a Linux box. So yeah, not sure how to go forward there. Also, my preference would be to get this working under Proton since I have before.
Last edited by Schattenspiegel on 23 Jan 2021 at 1:26 am UTC
It looks like there is a report of this happening on Pop!_OS on ProtonDB. I'm starting to wonder if I just have to accept that MW used to work on Linux but no longer does. Puzzling, but I suppose it's one of those things.
Another gist, generated by running "PROTON_LOG=1 %command%" launch option. Anything in here that could be helpful?
I've seen at least one report on ProtonDB that is my exact situation, but no idea how to find out if he had any better luck. You're right that Pop and Ubuntu are similar, but I have noticed oddities when it comes to gaming: for example, I was able to successfully create installer files for Quake II on my Kububtu laptop but not my Pop desktop.