Remove that patch, yes. Although it fixes the black screen problem it causes another with font rendering of specifically Valve developed games. This can easily be worked around by not using steam-native (or STEAM_RUNTIME=1 with it installed) but we should not introduce one bug to fix another.
If it is the most recent AUR workaround you mean, this one - https://aur.archlinux.org/packages/steam-native-webhelper/ then I can confirm that it currently works (with the minor change of
exec steam-native to
exec steam in line 10 of 'steam-native-webhelper'). However I don't think that it is a good distro-level solution as it may cause trouble later:
Comment by Maarten de Vries (de-vri-es) - Friday, 19 April 2019, 16:35 GMT
It's not hard to adjust the file automatically to have a new checksum. However, the big question is if we should do that when the checksum changes, since then apparently the original script changed. So whatever is bundled with steam-native-runtime might not match upstream anymore.
A straightforward solution that works until the upstream script changes:
- Check if the script in the user home folder has the expected checksum. If not, abort and hope for the best.
- If it did match, overwrite it with a fixed version that delegates to /usr/lib/steam/steamwebhelper.sh, which isn't checked by steam. The last script I uploaded does this.
I'm not sure we want to deal with it if 'hope for the best' fails. (The client updates frequently - several times a week - at least on the 'publicbeta' branch that I am on and that is, I think, the default for Manjaro.) How often this particular script gets updated I have no idea but when it does it will be outside of our control.
If on the other hand you mean the earlier AUR package - https://aur.archlinux.org/packages/steam-native-pcre-fix/ I can't recommend that since it pulls in
Sorry if it is not helpful but my recommendation would be to leave the black screen issue unaddressed.