Proton isn't functioning properly on Arch even though my GPU is working in all other tests I've run.
Proton isn't functioning properly on Arch even though my GPU is working in all other tests I've run.
I'm not sure about dpkg-configure, but a Google search suggests it restarts package settings as set by debconf. Arch Linux requires users to set up everything manually. Most software comes with its own config files or auto-generates upon installation and doesn't come pre-built. For instance, Samba lacks a smb.conf file. To clear configurations, locate the relevant files and delete them, then reinstall if needed. Details about included packages can be found on the Arch Wiki under "Package Contents." Information on custom configs is available on the Arch Wiki as well. The accuracy of these details depends on the source repositories and how packages are modified. Environment variables might also play a role—see the Arch Wiki for more. Personally, I think the issue could relate to the AMDGPU kernel version or Mesa installation, or it might be a problem with your setup. If you're open to it, trying TKG builds from chaotic-aur might help resolve Vulkan issues. You can always remove the repository if it doesn't work.
Hey, I could definitely connect with you. I switched to TKG but it didn’t work until after I updated. Once I did that, I tried launching Steam using the environment variables you shared earlier and it functioned properly for C&C. I’ve added those settings to /etc/environment so they load automatically. C&C now runs perfectly. MSFS still crashes sometimes, but now it launches and shows the loading icon before closing back to the desktop. I’m trying to move the proton beta from Steam to see if that fixes things. Thanks!
I'm not entirely confident about this, but switching to TKG made the whole system feel much faster. Previously, it took about 20 seconds just for the terminal to open. When I moved the mouse up to the top left for the app menu, there was a clear stutter each time. Certain programs, like mailspring and Steam, seemed to be having trouble, and even launching Conky at startup took around 5 seconds before it appeared. Now Conky works instantly, the stutter is gone, and everything feels smoother. In my process list, Xwayland is actually functioning properly now, something I hadn't noticed before. It seems the GPU driver installation might have been problematic, possibly because Wayland was still relying on older X libraries. Thanks again. Also, no, it didn't work as expected—you did.