Corben Dallas

Just realized, that ctrl+shift+f1 can reload the file. That helps already.

Cross posting from https://github.com/ValveSoftware/Proton/issues/215#issuecomment-742403711 as that issue is closed: If core dumps are enabled, and the game crashed once, just the mere existence of the core file in `/steamapps/common/BioShock Remastered/Build/Final`...

Ah, that's why I wasn't able to test it with adding `use protonfixes` in the `user_settings.py` and having the file beneath `.config/protonfixes/localfixes`. What I ended up with was using GE...

No change with kernel 5.16.9-surface. When previously having the device running with a different resolution, 1600x1024 is in the dropdown, but when selecting and activating it, it doesn't work. Also...

Same, when I want the 1600x1024 resolution, I'm back on 5.15.14-surface. For newer kernels 1680x1050 seems to be close enough to 1600x1024 to not make too much of a difference....

Unfortunately this is still an issue with Kernel 5.19.

I guess the nVidia issue is not related to my Surface Pro 7 with only integrated Intel graphics.

I'm now also affected by this issue with my Surface Pro 7 Strange is the /unknown instead of /focal after the package name. ``` libwacom-surface/unknown 1.12-2 amd64 [upgradable from: 1.12-1]...

When I try to grab the file manually, I get: ```bash wget "https://objects.githubusercontent.com/github-production-release-asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A/20211105/us-east-1/s3/aws4_request&X-Amz-Date=20211105T142216Z&X-Amz-Expires=300&X-Amz-Signature=b746b1c261d9470935b0612f44c53076cde5597da7391835ecc7577145a7cebf&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=139604852&response-content-disposition=attachment" -O libwacom-surface_1.12-2_amd64.deb --2021-11-05 15:29:37-- https://objects.githubusercontent.com/github-production-release-asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A/20211105/us-east-1/s3/aws4_request&X-Amz-Date=20211105T142216Z&X-Amz-Expires=300&X-Amz-Signature=b746b1c261d9470935b0612f44c53076cde5597da7391835ecc7577145a7cebf&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=139604852&response-content-disposition=attachment Resolving objects.githubusercontent.com (objects.githubusercontent.com)... 185.199.109.133, 185.199.111.133, 185.199.108.133, ... Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|185.199.109.133|:443... connected....

Looks like with current beta (1.24.5) it works now and doesn't crash.