Today I updated to 2.3.8.2 and launched the game to verify that everything was still working properly after the patch, but without intending to play at that moment. So I immediately clicked 'quit' from the main menu, and instead of being returned to my desktop as expected, I was logged out of my OS user account and was presented with my login screen as though I'd freshly booted the computer. Something is essentially initiating a session logout when I quit CK2. This behavior occurs consistently under the following circumstances:
I was previously using CK2 v2.8.2.1, and reverted to this version to test this issue on the same system configuration, and can confirm that 2.8.2.1 does not exhibit this problem under identical conditions.
I was able to workaround this by launching the game with a shell script that preloads the libraries from the Steam Runtime, so it looks like the issue is caused by the way CK2 interacts with the current version of one of those libraries.
I don't necessarily expect a formal solution, since I know the game is tested against and officially supported only with the libraries bundled with Steam, but I thought I'd point out that something that changed after 2.8.2.1 is not playing nicely with the current version of something included in the Steam Runtime.
- Game launched by directly running the executable, not through Steam.
- 'Quit' clicked immediately from the main menu without having first started a game.
I was previously using CK2 v2.8.2.1, and reverted to this version to test this issue on the same system configuration, and can confirm that 2.8.2.1 does not exhibit this problem under identical conditions.
I was able to workaround this by launching the game with a shell script that preloads the libraries from the Steam Runtime, so it looks like the issue is caused by the way CK2 interacts with the current version of one of those libraries.
I don't necessarily expect a formal solution, since I know the game is tested against and officially supported only with the libraries bundled with Steam, but I thought I'd point out that something that changed after 2.8.2.1 is not playing nicely with the current version of something included in the Steam Runtime.
Last edited: