Posted October 09, 2018
blakstar: Interesting... very interesting... I just tried Crusader Kings II, in Ubuntu BTW, and it ran without giving me access to any DLC in the launcher, but crashed when I exited, just as Stellaris did when I tested it in Antergos -- please note, I performed the Antergos test just to make sure that the Stellaris crash wasn't confined to Ubuntu.
However, when I altered the icon's command line, just as I did in Stellaris, Crusader Kings II ran normally, giving me full access to the DLC in the launcher, and not crashing back to the login screen at any point.
The only minor problem I got was when the game had fully loaded, it sent me back to the desktop, but the game was still running -- I only had to bring the game back into focus by clicking on the taskbar icon.
From what I can tell, and as Kaaedus originally pointed out, it definitely seems to be a Paradox issue. I guess the only remaining thing is to kick it back to GOG support, and let them know.
Interesting indeed. I didn't even think to check which DLC was running during my initial test. That said, my findings were similar. The terminal showed that the CK2 process was trying to find an active Steam process or steamclient.so a couple of times, but this didn't interfere with the game running. I can also confirm that the game has been minimizing after initial loading for the past couple of updates, even when running through Steam, so I'd think that's an unrelated minor bug. As you've said, the game is still running in the background, and clicking the icon in the taskbar brings it back into focus with no ill effects.However, when I altered the icon's command line, just as I did in Stellaris, Crusader Kings II ran normally, giving me full access to the DLC in the launcher, and not crashing back to the login screen at any point.
The only minor problem I got was when the game had fully loaded, it sent me back to the desktop, but the game was still running -- I only had to bring the game back into focus by clicking on the taskbar icon.
From what I can tell, and as Kaaedus originally pointed out, it definitely seems to be a Paradox issue. I guess the only remaining thing is to kick it back to GOG support, and let them know.
Post edited October 09, 2018 by Kaaedus