3.11.2 Crash on start with Steam for Linux + Proton
Since the 3.11.2 patch the game will crash every time while starting. I’ve tried several different Proton versions to no avail.
All the technical details can be found in the ticket I submitted with Valve:
https://github.com/ValveSoftware/Proton/issues/4188
But since I don’t know if the error is with Proton or PoE itself, I’m posting here too.
Linux is not an official port
Also other people has posted the fix on Proton somewhere
This is the start of forum signature: I am not a GGG employee. About the username: Did you know Kowloon Gundam is made in Neo Hong Kong?
quote from the first page: «Please post one thread per issue, and check the forum for similar posts first»
This is the end of forum signature
I know. We all know. And It’s becoming really tiresome to repeatedly being told so. Not to mention that GGG does actually support it unofficially, meaning that while there is no guarantee for perfect operation like on officially supported platforms, they do try to help making it work. A lot of people play this game on Linux actually.
Also other people has posted the fix on Proton somewhere
It’s not a fix but a workaround, and it isn’t stable for everyone.
I posted here to provide information that could help the devs find the cause and thus lead to a real solution on either PoE’s or Proton’s side.
Источник
Linux steam proton crash on launch
Steam for Linux
Typical steps are:
try different proton vertion
check proton log for what causes the problem
Game settings -> custom command -> and paste this: PROTON_LOG=1 %command%
run game and wait it for it to stop/crush
then check the log and you will find hints about what causes the problem.
Also you can check the protondb site to check if your game needs any tinkering
https://www.protondb.com/app/1036950
I’m having a similar problem too.
After some random update, no games function with any version of Proton above 5.0.0, and crash before the «loading window» appears.
Strangely enough, every game will load with the use of Wine.
So, anyone have a theory on what sabotaged modern Proton?
All of my Proton games stopped running recently. I would assume it is on Steam’s end with Proton. I noticed another user on a Linux forum had the same exact issue as me starting the same time.
Typical steps are:
try different proton vertion
check proton log for what causes the problem
Game settings -> custom command -> and paste this: PROTON_LOG=1 %command%
run game and wait it for it to stop/crush
then check the log and you will find hints about what causes the problem.
Also you can check the protondb site to check if your game needs any tinkering
https://www.protondb.com/app/1036950
Typical steps are:
try different proton vertion
check proton log for what causes the problem
Game settings -> custom command -> and paste this: PROTON_LOG=1 %command%
run game and wait it for it to stop/crush
then check the log and you will find hints about what causes the problem.
Also you can check the protondb site to check if your game needs any tinkering
https://www.protondb.com/app/1036950
where do I find the proton log?
where do I find the proton log?
In the directory of the games exe file
(Probable right click on the game in your library > manage > browse local files)
Typical steps are:
try different proton vertion
check proton log for what causes the problem
Game settings -> custom command -> and paste this: PROTON_LOG=1 %command%
run game and wait it for it to stop/crush
then check the log and you will find hints about what causes the problem.
Also you can check the protondb site to check if your game needs any tinkering
https://www.protondb.com/app/1036950
where do I find the proton log?
there are two possible locations:
one: in your game install folder
two: in your $HOME dir
log will be something like this: steam-
I have a problem with Super Jigsaw Puzzle: Generations, the game used to work fine before but now it won’t even start. I tried verifying the files, re-installing the game and it still wont play. Not sure what I can do.
All of my Proton games stopped running recently. I would assume it is on Steam’s end with Proton. I noticed another user on a Linux forum had the same exact issue as me starting the same time.
There is no critical issue like this in Proton, at worse there is regressions from a game to another but if everything does not run on your computer, 99.9% chances it is your problem
I have a problem with Super Jigsaw Puzzle: Generations, the game used to work fine before but now it won’t even start. I tried verifying the files, re-installing the game and it still wont play. Not sure what I can do.
Systemspecs (Hardware and Software) please!
see items [6] and [7] to provide us more detailed info about your system, because some issues are specific to a gpu brand/model, a driver version, a distro, etc.
also check comment #11 for info on breaking changes proton 5.13 brought (especially relevant for mangohud, vkbasalt and oldish nvidia users)
https://steamcommunity.com/app/221410/discussions/0/1636417404917541481/#c4070650515251703663
(re)downloading Steam Linux Runtimes (Soldier) also looks like it could help, if not done yet.
check comments #24 and #26 for more issues related specifically to newer versions of proton:
finally, move/rename the proton profile folder and then let proton rebuild it (test this with new version directly and if it doesn’t work clean it again and try rebuildung+running it with 4.11 then running it with new versions on the same profile
Источник
Linux steam proton crash on launch
i have my windows proton games on NTFS AND the linux native games too. the linux native games work but, Doom 2016 and Wolfinestien the old blood refuse to launch. Ryzen 5 1600, gtx 750 Ti, 8gb ddr4, eOS Juno 5.0 (ubuntu 18.04 LTS)
EDIT: it looks like ubuntu repos show latest driver for 700 series is v390 and minimum reqs is 41x.x, which is weird v390 works on my 4gb gtx 770 on my other machine and Doom 2016 launches.
EDIT: no change updating to nvidia prop v418
1- confirm you are already following Proton Requirements as described here (only those that apply to your hardware):
https://github.com/ValveSoftware/Proton/wiki/Requirements
Since you have edited your post to warn us the 418 driver is now in use, I imagine this is done, but never hurts to ask, most people with proton issues are because of this
2- have a look at ProtonDB entries for those 2 games to see if it’s not a known issue with those (maybe someone already posted a workaround there, maybe you’ll find out everyone gets the same issue and can’t be fixed, etc):
https://www.protondb.com/
3- Using NTFS is not ideal for linux in the long run and it might be the source of these issues, though not very likely if other games are working fine over it.
Can you install any of those proton games on a normal linux partition just for testing? The most common partition format for linux is ext4 amd your main linux partition will most likely be fine if there is enough free space in it. You could move one of those games over temporarily for that.
4- If none of the above helps, can you post the proton log files for these 2 games? these might have important clues to why it is failing.
https://www.protondb.com/help/troubleshooting-faq#how-do-i-create-logs-of-a-game-i-run-with-proton-
Also run steam from terminal and post the output here, for the same reason.
def not an issue as far i could see, those are officially supported titles. HOWEVER i found something interesting last night. uninstalled form the NTFS volume and reinstalled to the main linux volume and it worked. HOWEVER all of the linux native titles are still installed on the NTFS vol and they work fine! So i’m not sure if it’s because of the cache files steam is keeping on the NTFS vol or it’s truly a file system thing. ESPECIALLY since one of the last bug fixes for the latest version of Proton was improved NTFS support.
The catch is switching working windows 7 systems over to linux without erasing terabytes of media, one windows up keeping the existing NTFS volumes. i’ve never really had that act up before.
ANYWAYS, i have a cheap 512gb ssd i’ll just toss in the m.2 slot and format with ext4 and keep my games on an SSD anyways. have not tested doom 2016 yet but, the old blood launched and ran!
Источник
Linux steam proton crash on launch
I’m running arch on a Nvidia-optimus enabled laptop, all native games I have tried works flawlessly, but most Proton games refused to launch, the only exceptions being Cuphead
and Human Fall Flat.
Games will randomly either be stuck on the «Preparing to launch x» or appear to run, but without any window (or sound) displaying.
Heres a log of me trying to launch Noita:
https://pastebin.com/DBRNKhSK
I tried:
- All of available proton versions (even GloriousEggroll)
- Launching with intel graphics
- Using a EXT4 partition instead of my BTRFS one
- Using various launch options such as PROTON_USE_WINED3D=1
Some specs:
- OS: Arch Linux (5.10.60-1-lts kernel)
- CPU: Intel i7-9750H (12) @ 4.500GHz
- GPU: Intel CoffeeLake-H GT2 [UHD Graphics 630]
- GPU: NVIDIA GeForce GTX 1660 Ti Mobile
- NVIDIA drivers: nvidia-lts 1:470.63.01-2 nvidia-utils 470.63.01-1
- Bumblebee: 3.2.1-21
Any help with fixing this issue would be greatly appreciated!
Thank you, that’s a lot of datas to dig into
I will look again after my play session but there are indications that your iGPU is being used and no indication that your nvidia card is used.
Did you made a simple test like, disabling the iGPU in the bios settings and look if there is changes in the proton log ?
I know for sure that using a iGPU with recent Proton versions could fail as these GPUs do not implement the latest vulkan specifications, it is often a requirement to run the newest proton version properly
This error seems the culprit:
Invalid resolutions constraints: 0x0
I see many threads when searching for this error which relate to video not being able to play. Another mentioned the use of a wide screen monitor. Although, that was an old game.
from an old thread with similar error:
as in. if you go to the properties menu in the steam libray before launching them?!
that’s beyond bizarre
maybe the menu has been implemented as a floating window and isn’t destroyed properly, ends up as parent to the launched process and doesn’t carry a proper screen reference for it to inherit. or whatever quirk like that.
idk. it’s very buggy behaviour, and definitely steam’s fault in some way!
did you try alt-tabbing back and forth before launching? does that shake the issue away?
does it affect any game you launch afterwards? or just the one whose properties were opened/edited?
Your log reveals you are using
— An outdated version of Proton, v5.13-6b, you should always use the latest release or the latest Proton experimental
— This crash seems connected to a wrong use of PROTON_USE_WINED3D. You should never use at all this option. It will downgrade all the rendering engines in Proton, like using a simple Wine installation and so on, even if it works, you will have bad performances because all the components being developped by Valve will be disabled (DXVK, VKD3D, etc. ). It is best to not use launch parameters unless you really know for what they are intended to be used for, protondb has a lot of misinformations about this, peoples are posting parameters they don’t even know what they realy do.
You should focus on getting the game to run without using this launch option at all in all your games
If I were you, I’d start fresh by dropping the proton prefix in steamapps/compatdata/881100/ to reset it from scratch and make sure you use the latest proton release 6.x or experimental and no special launch options.
Источник
