steamcompmgr blocks GTA V from starting

[ardje]

Your system information

• Steam client version: 2018-09-26
• SteamOS version: brewmaster_beta
• Opted into Steam client beta?: Yes
• Opted into SteamOS beta?: Yes
• Have you checked for updates in Settings > System?: Yes

Please describe your issue in as much detail as possible:

When changing the .xsessionrc to: (sleep 4;exec steam) & exec icewm GTA V starts up normally. When using the steamos steam session however, GTA V stops with a black screen until I kill steamcompmgr and start icewm.

Steps for reproducing this issue:

• Make GTA V work on steamos using desktop wm.
• start steamos with bigpicture mode.

[Lyle-Tafoya]

I attempted to reproduce this issue.

First, I did some testing on my Arch Linux installation. I created a .xinitrc which only contains:

steam -steamos -tenfoot &
exec steamcompmgr

Using that setup, I was able to successfully run GTA V on Arch Linux using steamcompmgr. I also ran with "PROTON_NO_ESYNC=1 %command%" in the launch options and installed mscorefonts as recommended by others on protondb: https://www.protondb.com/app/271590.

After successfully playing GTA V for a period of about 30 minutes in Arch Linux, I installed SteamOS, opted in to brewmaster_beta, opted in to the client beta, did an upgrade and dist-upgrade. I believe that provides me with a similar environment to what is described in the initial bug report. At first, all my testing on SteamOS was performed without mscorefonts installed. I was unable to get consistent test results with any environment. I did manage to get it working once (with steamcompmgr running), but it did not sync my save file from the cloud, and I was unable to get it to work afterwards until installing ttf-mscorefonts-installer from the debian wheezy software repository. Now that ttf-mscorefonts-installer is installed (and with PROTON_ESYNC_DISABLE=1) it works (including the cloud syncing) without any tweaking of the environment. I did not find disabling steamcompmgr to help at any point in the process (ie. by using metacity or icewm). Perhaps there is something different about my hardware or environment.

My experience has not led me to believe that steamcompmgr interferes with this game. However, I would be interested to know if the problem still persists with the recommended tweaks mentioned on protondb.