flathub / com.valvesoftware.Steam

https://flathub.org/apps/details/com.valvesoftware.Steam
337 stars 70 forks source link

Proton games do not launch in KDE Plasma Wayland session #885

Open ishchow opened 2 years ago

ishchow commented 2 years ago

Game information All games run using Proton. Specifically observed with YS VIII: Lacrimosa of Dana, Nier Replicant v1.22, and Sonic Mania.

Distribution name and version where applicable

~$ cat /etc/os-release 
NAME="openSUSE Tumbleweed"
# VERSION="20220324"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20220324"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20220324"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"

Desktop environment: KDE Plasma 5.24.3 Wayland session

Flatpak info

~$ flatpak --version
Flatpak 1.12.7
flatpak --gl-drivers
default
host

Problem description Steam games running via Proton do not launch at all when Flatpak steam is running in Wayland session. The play button state changes to STOP and then the game process seems to die before drawing any UI.

Error log

Seems there is an earlier issue filed with GNOME Wayland two years ago: #578. But error messages from that issue seem to be different and that issue was fixed by sdk update. Running flatpak update did not fix this issue for me.

Does this issue reproduce with native Steam Does not reproduce with native steam (either with X11 or Wayland). Does not reproduce with proton games in Flatpak Steam + X11. Does not reproduce with native games in Flatpak Steam + Wayland (ex. Celeste).

Meister1593 commented 2 years ago

Same thing (tested on DRG)

[plyshka@fedora plyshka]$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="35.20220411.0 (Kinoite)"
ID=fedora
VERSION_ID=35
VERSION_CODENAME=""
PLATFORM_ID="platform:f35"
PRETTY_NAME="Fedora Linux 35.20220411.0 (Kinoite)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:35"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora-kinoite/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=35
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=35
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Kinoite"
VARIANT_ID=kinoite
OSTREE_VERSION='35.20220411.0'
[plyshka@fedora plyshka]$ flatpak --version
Flatpak 1.12.7
[plyshka@fedora plyshka]$ flatpak --gl-drivers
default
host

Plasma 5.24.3 Running proton through distrobox arch container with steam installed works perfectly fine With flatpak, i see in proton logs this:

25193.845:0020:00c4:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
25193.845:0020:00c4:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
Meister1593 commented 2 years ago

I'm on Gnome Wayland and it works just fine there. But there was update not long ago, maybe it was fixed?

sean-gray commented 1 year ago

Im also having this issue. And this is not fixed.

junocomp commented 1 year ago

I am also having this issue

DaAwesomeP commented 1 year ago

I'm seeing this issue on openSUSE Leap 15.4 with Proton in Steam. I am seeing the nodrv_CreateWindow for all games.

DaAwesomeP commented 1 year ago

Interestingly, setting Proton to 3.16 seems to work but 7.x, 6.x and Experimental do not work.

sean-gray commented 1 year ago

For me on KDE plasma 5.26.9 there is massive flickering. But only on wayland. on x11 its great.

DDR0 commented 1 year ago

Dang it, I've definitely just reproduced this here, Debian + Wayland yields no window & flickering. If I can provide any details, or help test a fix, let me know.

jacobckelly commented 10 months ago

This is still an issue from what I can see. OpenSUSE Aeon \ Gnome \ Wayland \ Nvidia Binary Driver

It appears whatever change happened happens between Proton 4.2-9 (which will launch your non-native game) and 4.11-13 (which will just quietly exit).

stacyharper commented 10 months ago

From my tests, 5.0-10 works with Celeste, but not 5.13-6, 6.3-8. 7.0-6, 8.0-3, or experimental. But the Flatpak community build 7.0-5 works.

Here Sway on Alpine Linux x86_64, Flatpak Steam, AMD graphical card.

Here the logs with working Flatpak Proton 7.0-5, notworking Proton 7.0-6, and the diff:

https://paste.sr.ht/~stacyharper/a28ff1d046f06cb71dedd3c7af63971a91eaa558

We also read:

2771.102:0144:0148:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
2771.102:0144:0148:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.

I confirm that Celeste Proton 7.0-6 works under Xorg.

stacyharper commented 10 months ago

My issue was that I didn't update the dbus DISPLAY environment variable when xwayland is availabe.

doraskayo commented 10 months ago

My issue was that I didn't update the dbus DISPLAY environment variable when xwayland is availabe.

Can you elaborate on this? Did you run the Steam Flatpak in a separate DBus session?

stacyharper commented 10 months ago

Can you elaborate on this? Did you run the Steam Flatpak in a separate DBus session?

No, I was running dbus before my Sway session, then I was updating the dbus environment variables with dbus-update-activation-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP. Adding DISPLAY to this list solved my issue.

sagehane commented 7 months ago

Adding DISPLAY to this list solved my issue.

@stacyharper, this solved my issue on River. Kind of obvious in hindsight but you saved me lots of time and confusion, thanks.

supagu commented 3 months ago

I am having the same problem with KDE 6 + wayland. I am using EndevourOS. How would I setup these environment variables for a non-flat pack version of steam to see if that was my issue?

Edit: I just found my solution. I needed some working vulkan drivers installed: https://forum.endeavouros.com/t/should-i-get-vulkan-for-amd-igpu/40309