ptkato

> by the way, i found it surprising that cabal init --overwrite changes the working directory to `$PWD.save$n`. I think we should at least add a message informing the user...

That message stuff doesn't seem right, it is already like that, kinda: https://github.com/haskell/cabal/blob/5a8e99788b0d5793de7af9ec9d70e4bf35ee8765/cabal-install/src/Distribution/Client/Init/Types.hs#L360-L362

There are a few weird behaviours at play here. I remember discussing about allowing only 1 backup at a given time, instead of having multiple of them, for example if...

All in all, the backup feature is being a bit disruptive considering all the rest, I propose that we move that functionality from within the inner bowels of the `cabal...

Perhaps. Note that it doesn't make a difference if I use steam-runtime or not, also the news & highlights section works just fine, but that can be retrieved from an...

Update: now with Proton 3.7-5 Beta, it throws me a little "Fatal error" window with an OK button and the game closes itself shortly after.

audit: type=1701 audit(1536973247.900:13): auid=1000 uid=1000 gid=1000 ses=8 pid=28637 comm="War-Win64-Shipp" exe=2F686F6D652F70746B61746F2F2E6C6F63616C2F73686172652F537465616D2F737465616D617070732F636F6D6D6F6E2F50726F746F6E20332E3720426574612F646973742F62696E2F77696E6536342D7072656C6F61646572 sig=11 res=1 Now I'm getting this audit log from dmesg.

Now with Proton 3.16-4, the game is working as intended.

I got a similar problem, and it changes from game to game. The command I use is ``` ENABLE_HDR_WSI=1 gamescope -f -W 3840 -H 2160 --hdr-enabled --hdr-debug-force-output --force-grab-cursor -e --...

I'm encountering a weird behaviour on the game part, some things straight out don't appear, for example the characters' portraits:  What is weird is that sometimes rarely, they do...