[Linux] Launcher window not visible

[joakimlundborg]

When I try to launch Stellaris, the executable starts, and I can hear the in-game music from the launcher, but no window is visible. I can see the process running, so there is no crash. Since I can't see any window, I can't get any further. This is on an up to date Arch install running kernel 4.8.4-1-ARCH on a Radeon HD 7870 and Gnome 3.22. I have tried running with and without Wayland activated.

Stellaris used to run just fine, and other Clausewitz titles works, for example CKII.

 

[fyrkrans]

Here the link to the thread I mentioned on Steam. But you seem to have the problem with X11 to, so I fear this won't help you.

You could try to make a backup of "~/.local/share/Paradox\ Interactive/Stellaris/save\ games/" and then delete "~/.local/share/Paradox\ Interactive/Stellaris/".

 

[joakimlundborg]

Clicking the link still doesn't work for me, weird. I'm still curious about what could take care of any Wayland-related problems. I also tried deleting the folder as suggested here, but that unfortunately didn't fix my problem.

 

[joakimlundborg]

Here are my logs if that is helpful to anyone. errors.log contains messages that looks like they could be bad:

[23:50:55][gfx_opengl.cpp:1066]: SDL_GetWindowFromID failed: Invalid window
[23:50:55][gfx_opengl.cpp:1077]: SDL_GL_CreateContext failed: Invalid window
[23:50:55][gfx_opengl.cpp:1111]: glewInit failed: Missing GL version
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/text.shader(Text)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/text.shader(Text3D)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(Up)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(Down)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(Disable)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(Over)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(TextUp)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(TextDown)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(TextDisable)
[23:50:55][pdxshaderparser.cpp:1362]: Failed linking shader gfx/FX/buttonstate_onlydisable.shader(TextOver)

 

[AndrewT]

Clicking the link still doesn't work for me, weird. I'm still curious about what could take care of any Wayland-related problems. I also tried deleting the folder as suggested here, but that unfortunately didn't fix my problem.

It goes here
https://bugs.freedesktop.org/show_bug.cgi?id=98272

Given the other issues we see here on the new AMD open drivers, I suspect what you're seeing is a consequence of that.

 

[fyrkrans]

Clicking the link still doesn't work for me, weird.

I made a mistake, since I didn't pay enough attention when I directed you to this thread. The thread I have linked to is in the EU4 bug reports forum and since you don't have EU4 you can't access it. I'm very sorry about my mistake and the confusion it caused.

The gist of the mentioned bug report is that EU4 doesn't work with wayland, and I assume it's the same with Stellaris. (As of now) it doesn't feature any workaround or something else that might help you to get the game working with wayland. The thread also mentions the URL that AndrewT linked to.

 

[joakimlundborg]

I tried it today again, and now it works under Gnome3 Xorg, but not under Gnome3 Wayland,l Hooray! Maybe I didn't test properly before, I don't know. Thanks a lot for your help @fyrkrans! Now I'm off to play a nice game of Linux-powered Leviathans!

 

[joakimlundborg]

@AndrewT This is with open AMD drivers btw, so it is working just fine, just not under Wayland.

 

[fyrkrans]

You are welcome! Let's hope that one day PDS' games will work with wayland (too).

btw: People who have replied to a thread automatically get an alert when someone writes another post there. (Unless they have turned that option off.) Therefore it's usually not necessary to ping/tag people who already have participated in a thread. It's not a problem to do so though; they don't get two alerts when you ping/tag them. From what I have seen pinging/tagging is used to get the attention of a user that so far hasn't participated in the thread in question.