Hello @angela-d, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/6826#issuecomment-2388529939.
ipv6 was the culprit.
Following up in case anyone having a similar problem in the future lands on this issue.
If you disabled ipv6 (like I did) via grub, you'll see the following in /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet"
Removing ipv6.disable=1 allowed Arena to run on my Debian machine:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
(after a reboot)
Compatibility Report
System Information
GPU: Intel Mesa Intel(R) HD Graphics 630 (KBL GT2)
Video driver version: 4.6 (Compatibility Profile) Mesa 22.3.6
Kernel version: 6.1.0-25
Link to full system information report as Gist: https://gist.github.com/angela-d/a815f77eb42cb9ab076bec61d467046f
Proton version: 9.0-3 (have tried others, also)
I confirm:
The game launches from Steam without issue; sign in works.
From
~/.local/share/steam/common/MTGA/MTGA_Data/Logs/Logs/:Symptoms
~/.local/share/steam/to a larger harddrive w/ a symlink, assuming /home was low on space / maybe Arena is trying to cache locally (home is partitioned and definitely smaller than your average harddrive) - no change (Steam still works fine)Reproduction
Suspecting this is a combo of hardware/software or missing firmware? Debian probably isn't the ideal OS for gaming, but it's what I like to use as my daily driver.
Also worth mentioning: