In GloriousEggroll's wine-ge-custom builds, enabling Emulate Virtual Desktop in winecfg breaks the wine prefix, so that nothing (not even wineconfig) runs in that prefix any more. Anyone know more about this?
I would report it, but I'm not on Discord and that seems to be the only place where he accepts reports. Maybe someone can copy this post to him there?
Here's the output when trying to launch winecfg after enabling that setting on Wine-GE-Proton8-22:
wineserver: using server-side synchronization.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
002c:fixme:winediag:LdrInitializeThunk wine-staging 8.0 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
006c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
006c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
006c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
006c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:err:hid:udev_bus_init UDEV monitor creation failed
00ec:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
00ec:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
Not really an answer to your question, but just to make you aware of some options:
Have you considered using subkeys for each of your machines, signing things with those, and keeping their master key someplace safe? That would limit your exposure if one of those machines is compromised, since you could revoke only that machine's key while the others remain useful (and the signatures they have issued remain valid).
Are you setting expiration dates on your keys? That can bring some peace of mind when you lose your key/revocation data.