DASHBOARD freezing after 10th anniversary updates UBUNTU

[buncis]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist: REDACTED
• Have you checked for system updates?: [Yes/No] yes
• Are you using the latest stable video driver available for your system? [Yes/No] yes
• Have you verified the game files?: [Yes/No] yes

Please describe your issue in as much detail as possible:

I dota client freezing with 1 FPS when I click anything on the dashboard

Steps for reproducing this issue:

1. open the game
2. wait it load then
3. app freezing with 1 FPS

Idk but I think ES animation freeze it it makes dota hang

USING -safe help a bit with the load and launch but it hang when I clicking something

[regtyit]

I installed nvidia-driver-535 and dota 2 now works.(I don't know why nvidia drivers don't auto update)

[buncis]

I installed nvidia-driver-535 and dota 2 now works.(I don't know why nvidia drivers don't auto update)

installing nvidia-driver 535 solved this issue

[Turmfalke2]

Possibly have the same issue here. Getting an xid 32 from the nvidia driver.

[Brokenbar]

Same here on Debian. The 535 drivers aren't available in the repositories yet. Does anyone know if manual installation from the download on Nvidia's page is going to work like it'll just overwrite the drivers I already have, or do I have to go through a full purge of the existing drivers to install them?

[Zawah]

Same issue, sometimes the dashboard will load with missing textures hang there for a while, until textures are loaded(opening a previous match details from profile, or just changing the highlighted heroes, or the new treasure screen) and then freeze.

I'm not sure if others have the same issue but I checked running steam from terminal and found this error:

Loaded libpangoft2-1.0.so, got (nil)

failed to dlopen "libpangoft2-1.0.so" error=libpangoft2-1.0.so: cannot open shared object file: No such file or directory

which triggers more warnings, but not sure if this is what is causing the issue, was working properly before last update.

Tried verifying files integrity, and reinstalling but couldn't fix it.
Also tried running with Steam Linux Runtime and had the same issue.

I'm running on MXlinux and I have the same issues whereas nvidia 535 drivers are not yet ready(nor in test repos).

[paboum]

On gentoo, updating nvidia-drivers to non-stable 535.98 version indeed helps, the split locks still occur however.

This is obviously unacceptable, the game should detect and report unsupported driver version, a beta test process should be executed prior to production release, bug should be resolved faster than my comments are marked as off-topic (whilst they are exactly on topic - Valve SUCKS at programming).

[kisak-valve]

Hello @paboum, for transparency, the split lock issue you're referring to is being tracked at ValveSoftware/steam-for-linux#8003 and is unrelated to Dota 2, making that off topic feedback for the specific issue reports you've decided to insult Valve on.

[Zawah]

Game is working with proton 8.0-3 but still crashing in native or Steam Linux Runtime...

You may need to tweak your configuration for getting dota working with proton, if it's just crashing after the dota logo appears, this configuration change may work:

sysctl -w vm.max_map_count=262144

[helix-d2]

It seems, on Debian 12, the 535 series driver will not be available for a while (https://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/2023-August/022362.html). The only hope is if Valve tries to fix this issue, if possible, on their end. Can we please have any sort of progress or response? Even if Valve is not going to fix this issue and leave it to NVIDIA, it would be nice to know.

[diniciacci]

@helix-d2 from outside, but with enough years of dev experience, I just want to cut straight your expectations (no polemics naturally).

The bug is exactly like the other 3 times dota had a very similar bug (i.e. probably a shader use in a out-of-spec way). In none on the other instances Valve fixed the issue until there was a new release sometimes major, sometimes minor. No hotfix has been delivered for this type of problems in the past. I would be more than happy to be wrong, but lower your expectations.

Given the context and the history, the issue is likely not from Nvidia and it would be strange if it were. This does not mean that they can't monkey patch it, that is likely what they did in 535 series. Sentences like "series 525 of nvidia drivers is problematic" should be avoided, because they might be misinterpreted of where the problem lies. Notice that the problem is present on AMD also.

Afar from critics, this is not the point, just do not wait a fix, but if someone can't hold to play for some weeks, here is a list of workarounds:

1. Hack the intro file to have it not load or, if you feel brave, edit it to remove the problem. Requires Dota 2 technical skills.
2. Manually install the driver for you distro. Requires linux technical skills.
3. Run the emulated version of Dota 2 using Proton. Has minor performance implications. Requires basically no skills.

Here a short shot guide for 3).

1. Open Steam
2. Right click on Dota 2:
   
3. Select "Properties"
4. Select "Compatibility":
   
5. Tick "Force the use of a specific Steam Play compatibility tool"
   
6. Select "Proton 8.0-3" from the drop-down select. Any other version will likely work, this is just the latest I tested working on my system.
   
7. Steam will download quite some data, but that that will remain self-contained.
8. Start Dota 2 and play

Bonus) Keep 30 mins to regenerate the Vulkan shaders or skip their caching. In case you skip, notice that the lower performance is likely because of that.

Best Regards

P.S.
The "visual effect" causing the problem, looks like also the same between all those instances, so well, it might also be that they are copying and pasting the same bugged code over and over, maybe from some outsourcing gfx coder. That would also explain why of the late delivery. Reliability of contractors.

P.S. However, for sake of completeness, from Nvidia documentation on the error generated
4.3. XID 32: PBDMA Error This event is logged when a fault is reported by the DMA controller which manages the communication stream between the NVIDIA driver and the GPU over the PCI-E bus. These failures primarily involve quality issues on PCI, and are generally not caused by user application actions.
The error is usually associated with:
32 Invalid or corrupted push buffer stream: Driver error, System Memory Corruption, Bus Error, Thermal Issue, FB Corruption.
This deposes in favour of Nvidia fault.

[JoaquimEsteves]

@diniciacci none of your solution seems to not have worked for me.

I tried to look for the intro file that's breaking the startup; but no luck - none of the panorama videos look like what we see at the start of the game.

The config:
+map_enable_background_maps 0 seems to help; as I now can actually hop into the menu and click about. But whenever I try to demo a hero or watch a game it'll just crash.

This is a sad situation - hope valve fixes it.

[diniciacci]

@JoaquimEsteves if you can hop in, you can toy with the video settings and that might help. However notice that it's strange that the proton workaround does not work, because apparently it fixes this particular issue (many reports that it does). I.e. proton is using dx 11 rendering. I suspect the problem might also be in the "hero presentation video" like has happened before.

[helix-d2]

Replying to #2414 (comment)

Thank you for the detailed reply. Yeah I thought Valve might not fix the issue soon. So I chose option 4 - Reinstalled the OS (Kubuntu 23.04) and installed the 535 series driver. Seems to have fixed the issue, tried one bot game and it was working well, although the performance seems to have dropped a bit. Still have to try a matchmaking game. Hopefully that works as well.

[JoaquimEsteves]

@diniciacci

I played around with a variety of settings; -safe -gl and some other launch options that didn't help.

After discovering the +map_enable_background_maps 0 trick I was able to jump into the actual menu and attempted to set all of the visual settings to "best performance" - this didn't help either.

I did not try to force dota to use dx11, the option to do so was not apparent to me, if anyone has had any luck with that I'd love to hear results.

Truth be told I was annoyed enough having to spend a tuesday debugging a game as opposed to playing it for two hours.

[paboum]

Truth be told I was annoyed enough having to spend a tuesday debugging a game as opposed to playing it for two hours.

Well, my fee for doing any debugging, test reports, project management or code review starts from $150/h. When my input is not appreciated, I play other games. Since they are presenting ostrich mentality with these issues, the project is likely going to be dead in 12-18 months and will stop earning money at all. I'm optimistically looking forward to new moba games that will take its place.

[diniciacci]

Just a small update. After 1st September 2023 update that claims:

• Fixed a crash in the Vulkan renderer on Linux
• Fixed a crash on Linux GPUs with low memory
• Fixed fullscreen flickering on multi-monitor Linux systems

The problem is still present, at least on NVIDIA 525 drivers.

Notice that installing NVIDIA 535 drivers is not an option. They are known to be buggy and some distros might skip them entirely. I.e. they might make Dota 2 work, but they will break something else apparently.

This is still an outstanding bug. Would be nice to have official feedback and no polemics.

[nh2]

On Ubuntu 22.04, sudo apt install nvidia-driver-535 and rebooting fixed the issue for me (while it crashed on the 525.125.06 Nvidia driver; I posted in #2420 (comment) before).

Thanks @kisak-valve for referring me here.

[diniciacci]

Just a reference, of many ¹, so it's clear that "upgrade to 535" is not a solution, neither can be a suggested workaround:

"According to a Proton developer, there has been progress in understanding the issue. It appears that the problem is related to address space exhaustion. DXSETUP is a 32-bit process with a memory address limit of 4GB. The newer NVIDIA drivers from the 535 series reportedly require more memory compared to the previous versions, causing crashes. NVIDIA is aware of this issue."

[diniciacci]

nvidia-driver 530.41.03 hit Debian experimental branch. I installed it today (not recommended).

I confirm that version 530.41.03 does not fix the problem.

Proton workaround does not work also anymore with:

• linux-image-6.5.0 + nvidia-driver-525.125.06-2
• linux-image-6.5.0 + nvidia-driver-530.41.03

Game is not playable anymore.

[BloodyIron]

I've been battling monitor freezing of this nature for most of this entire year. Switched between many different nVidia versions, and lots of other stuff. My 3060 ti isn't hardware faulty, because this issue only started happening after I had to replace my OS NVMe earlier this year (previous one failing) and had to reinstall Ubuntu. Xid 32 and a few other numbers seem to come up randomly, and I have yet to find a solution and a pattern. I'm going mad with it, and I for sure am not switching to AMD for my GPU (I'm not explaining why).