-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing on Ubuntu 20.04 after Ringmaster #2807
Comments
I will try again to reinstall the driver with different options and see what happens. It seems I am the only one with this problem so far. |
Same. All super up to date and yet crashing. Smaller error, although.
|
Your system information
Please describe your issue in as much detail as possible: Same problem here on PopOS. Game loaded in the menu when I click randomly it crashes. |
Same Linux Mint |
Try adding "-threads 0" to the launch parameters. |
@Vortelio nice! It worked for me too. The loss is not neglectable but better than not playing for the 3rd week in a row. |
Same here, crashing on Pop Os, so I've switched Nvidia Drivers from 470.x.x (default) to newer version 560.x.x, and it fixed the crashing issue, but now facing an old nemesis of issue where my game not running on dedicated GPU, though I was able to play few games when it did decide to run the dedicated GPU couple of times. I'm only speculating this based on fps drop, and less fan noise coming from the GPU, and it doesn't just happen at the start, it even happened in the middle of the game, where everything suddenly becomes super sluggish and fps dropped like crazy. Maybe it's related to my very old GPU (Nvidia Quadro P600) which may not fully support Vulkan, but I'm not entirely sure. |
works for me, hope it helps
|
Thanks for bringing it up. I'm having the same issue.
Steps to reproduce:
Stuff I've tried:
Some data from latest crash dump:
|
@Vortelio yes! it worked with |
Its over for me. Stopped working with |
@theflockers your crash is In the properties -> compatibility setting for the game, make sure 'Force the use of a specific Steam Play compatibility tool' is unchecked. |
Thanks @TTimo, but that is not the issue. I also reviewed the errors I posted and there was nothing about libpango, maybe you saw in someone else's error. Mine only mentions librenderdoc, which after add it, did not solve anything, but the complain on the librenderdoc missing. At the same time, the game worked with I am using the native runtime. I will try to remove and reinstall, although I still thing stopping wasting time with Dota 2 might be more healthy than keeping being stressed with this every time a big update comes. |
And I was close to get a SteamDeck but every time I see the black hole which is valve's support for this game on Linux, I gave up. |
Ok, after having a second look at your runtime info report, I see there may be a problem with your graphics drivers. Your GL driver report This may be why you are crashing, making sure you update both your GL and Vulkan drivers may fix your problem. |
It is weird that Vulkan is outdated as it comes with the amd gpu driver. I installed the latest one available and also choose the proprietary Vulkan driver. But let me try once again. |
Btw, after uninstall and install it again, at least the |
In fact it might have a conflict:
Thanks for noticing that. Hope removing the dist ones it fixes the issue. |
Yeah. Not lucky at all. Letting only the amd mesa packages vulkan stops working. Anyhow, I tried to downgrand the amdgpu, it works a bit better but still crashes. At least |
We recommend RADV over AMDGPU. On Ubuntu it is often necessary to use the kisak-mesa ppa in order to have reasonably up to date drivers (https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa). |
Your system information
Steam
->Help
->System Information
) in a gist:Please describe your issue in as much detail as possible:
Still crashing since the update. A small comment saying that someone is working to fix the Linux version it would be nice.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: