You are not logged in.
Pages: 1
Hey all, I'm having an issue with steam not launching under wayland. I tested this with KDE Plasma Wayland, Hyprland,KDE Plasma X11, and AwesomeWM. While steam launched perfectly in Plasma X11 and AwesomeWM, it did not under wayland. Something to note is that I am running Nvidia beta drivers (555). Another thing to note is that the flatpak version of steam also appears to not be working, with a very similar log to regular steam.
Below is the output of running steam in the terminal in Hyprland.
steam.sh[7874]: Running Steam on arch rolling 64-bit
steam.sh[7874]: STEAM_RUNTIME is enabled automatically
setup.sh[7947]: Steam runtime environment up-to-date!
steam.sh[7874]: Steam client's requirements are satisfied
[2024-06-25 20:02:44] Startup - updater built Jun 20 2024 17:13:49
[2024-06-25 20:02:44] Startup - Steam Client launched with: '/home/ender/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
06/25 20:02:44 minidumps folder is set to /tmp/dumps
06/25 20:02:44 Init: Installing breakpad exception handler for appid(steam)/version(1718904662)/tid(8006)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2024-06-25 20:02:45] Loading cached metrics from disk (/home/ender/.local/share/Steam/package/steam_client_metrics.bin)
[2024-06-25 20:02:45] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2024-06-25 20:02:45] Using the following download hosts for Public, Realm steamglobal
[2024-06-25 20:02:45] 1. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-06-25 20:02:45] Checking for update on startup
[2024-06-25 20:02:45] Checking for available updates...
[2024-06-25 20:02:45] Downloading manifest: https://cdn.steamstatic.com/client/steam_client_ubuntu12
[2024-06-25 20:02:45] Manifest download: send request
[2024-06-25 20:02:45] Manifest download: waiting for download to finish
[2024-06-25 20:02:45] Manifest download: finished
[2024-06-25 20:02:45] Download skipped: /client/steam_client_ubuntu12 version 1718904662, installed version 1718904662, existing pending version 0
[2024-06-25 20:02:45] Nothing to do
[2024-06-25 20:02:45] Verifying installation...
[2024-06-25 20:02:45] Performing checksum verification of executable files
[2024-06-25 20:02:46] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/ender/.local/share/Steam/logs
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe43c9dc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe43c8500
From my own research, the log looks normal, but it just gets stuck at XRRgetCrtcInfo. Any info would help. Thanks in advance.
Offline
lib32-nvidia-beta-utils installed?
Offline
Since I restarted my PC yesterday (after a few days of leaving Steam open), I've been having the same problem with pretty much the same logs. The flatpak is also not working for me, with the same failure mode. My setup is KDE 6.1 on Wayland, with nvidia 555 beta.
Tried a bunch of things recommended in these upstream threads (but tbh a lot of it wasn't applicable to me since I don't have an iGPU)
Also, the problem is not just that the GUI isn't starting or is crashing. The API is also not working according to the logs of XIVLauncher.Core, which calls the API. I've noticed some interesting kf.windowsystem logs that come up around the same time I launch steam
Jun 26 10:56:13 kwin_wayland[1329]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Jun 26 10:56:15 xdg-desktop-portal-kde[1560]: xdp-kde-settings: Namespace "org.gnome.desktop.interface" is not supported
And here are the XIVLauncher.Core logs showing the API not working
Jun 26 10:56:33 systemd[894]: Started XIVLauncher.Core.
Jun 26 10:56:33 xivlauncher-core[63818]: [S_API] SteamAPI_Init(): Loaded '/home/$USER/.local/share/Steam/linux64/steamclient.so' OK.
Jun 26 10:56:33 xivlauncher-core[63818]: [S_API FAIL] SteamAPI_Init() failed; create pipe failed.[S_API] SteamAPI_Init(): Loaded '/home/$USER/.local/share/Steam/linux64/steamclient.so' OK.
Jun 26 10:56:33 xivlauncher-core[63818]: [S_API FAIL] SteamAPI_Init() failed; create pipe failed.X Error of failed request: BadMatch (invalid parameter attributes)
Here's some of the relevant packages I have installed:
$ pacman -Q | grep nvidia
libva-nvidia-driver 0.0.12-1
nvidia-beta-dkms 555.52.04-1
nvidia-settings 555.42.02-2
nvidia-utils-beta 555.52.04-2
$ pacman -Q | grep steam
steam 1.0.0.79-6
All of my kde/plasma packages are consistent with the 6.1.0-1 release in the Arch repos as far as I can tell.
Last edited by pendo324 (2024-06-26 15:05:05)
Offline
You need lib32-nvidia-utils-beta, without that nothing of this is surprising. Steam is a 32bit application and needs 32bit libraries to establish a graphics context.
Offline
You need lib32-nvidia-utils-beta, without that nothing of this is surprising. Steam is a 32bit application and needs 32bit libraries to establish a graphics context.
Just installed it and rebooted for good measure, still not working. Apparently, I've never had that package installed and yet it was working previosuly (assuming I ran the right command to check my pacman logs and I haven't cleared them):
$ grep "lib32-nvidia-utils-beta" /var/log/pacman.log
[2024-06-26T11:16:33-0400] [PACMAN] Running 'pacman --upgrade --noconfirm -- /home/justin/.cache/paru/clone/lib32-nvidia-utils-beta/lib32-nvidia-utils-beta-555.52.04-1-x86_64.pkg.tar.zst'
[2024-06-26T11:16:34-0400] [ALPM] installed lib32-nvidia-utils-beta (555.52.04-1)
[2024-06-26T11:16:34-0400] [PACMAN] Running 'pacman --database --asexplicit -- lib32-nvidia-utils-beta'
$ pacman -Q | grep nvidia
lib32-nvidia-utils-beta 555.52.04-1
nvidia-beta-dkms 555.52.04-1
nvidia-settings 555.42.02-2
nvidia-utils-beta 555.52.04-2
Still getting the same error, even with the flatpak and steam-native and the
-vgui
flag. Tried reinstalling the steam/steam-native-runtime packages as well.
Last edited by pendo324 (2024-06-26 15:26:53)
Offline
I downgraded to plasma 6.0.5 by setting my repos to use the archive from June 16 2024 and it still didn't work, but when I re-upgraded to current repos, it worked. The logs look the same, except it got past the
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe481adc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe4819500
lines
(uploaded full log to gist since its long: https://gist.github.com/pendo324/2865c8 … 71418d283)
Offline
I downgraded to plasma 6.0.5 by setting my repos to use the archive from June 16 2024 and it still didn't work, but when I re-upgraded to current repos, it worked. The logs look the same, except it got past the
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe481adc0 XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe4819500
lines
(uploaded full log to gist since its long: https://gist.github.com/pendo324/2865c8 … 71418d283)
Rebooted again for science, and now Steam is not working with the original failure mode.
Offline
pendo324 wrote:I downgraded to plasma 6.0.5 by setting my repos to use the archive from June 16 2024 and it still didn't work, but when I re-upgraded to current repos, it worked. The logs look the same, except it got past the
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe481adc0 XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe4819500
lines
(uploaded full log to gist since its long: https://gist.github.com/pendo324/2865c8 … 71418d283)
Rebooted again for science, and now Steam is not working with the original failure mode.
This downgrade/upgrade thing is working for me consistently. I noticed its also logging me out of Steam. That might be the real solution? Not sure which files I have to delete to test that.
I just won't be closing steam / rebooting for a few days I guess.
Offline
$ pacman -Q | grep nvidia
libva-nvidia-driver 0.0.12-1
nvidia-beta-dkms 555.52.04-1
nvidia-settings 555.42.02-2
nvidia-utils-beta 555.52.04-2
$ pacman -Q | grep steam
steam 1.0.0.79-6
I have more packages, try installing them all.
⋊> ~ on master ⨯ pacman -Q | grep nvidia 23:28:24
lib32-nvidia-utils-beta 555.52.04-1
lib32-opencl-nvidia-beta 555.52.04-1
libva-nvidia-driver 0.0.12-1
nvidia-beta-dkms 555.52.04-1
nvidia-hook 1.5-2
nvidia-inst 24-1
nvidia-settings-beta 555.52.04-2
nvidia-tweaks 545-2
nvidia-utils-beta 555.52.04-2
opencl-nvidia-beta 555.52.04-2
Offline
Maybe you have the same issue as me? Does steam work when starting it directly from the console? If so, disable Hardware Accelerated Interface from Steam Settings. It's just a workaround, unfortunately.
Offline
I have the same problem and after some debugging it seems the problem is between GTK2 and xorg-xwayland-git package.
Changing xorg-xwayland-git to xorg-xwayland package seems to fix the problem to me.
Offline
I have the same problem and after some debugging it seems the problem is between GTK2 and xorg-xwayland-git package.
Changing xorg-xwayland-git to xorg-xwayland package seems to fix the problem to me.
Thanks a lot! It seems like this fixed my issue! I have reported this as a fix in the upstream issue I created as well, in case anyone stumbles upon the issue report there.
How did you end up discovering it was a GTK2 issue?
It seems like both packages are building from the same 24.1 branch and the biggest diff I see between the AUR package and the xorg-xwayland package is the meson build command?
diff --git a/official b/aur
--- a/official
+++ b/aur
- arch-meson xwayland-$pkgver build \
+ arch-meson xserver build \
-D ipv6=true \
-D xvfb=false \
+ -D xnest=false \
-D xdmcp=false \
-D xcsecurity=true \
+ -D xorg=false \
+ -D xephyr=false \
+ -D xwayland=true \
+ -D xwin=false \
+ -D xquartz=false \
-D dri3=true \
-D glamor=true \
-D xkb_dir=/usr/share/X11/xkb \
-D xkb_output_dir=/var/lib/xkb
Offline
Gothem wrote:I have the same problem and after some debugging it seems the problem is between GTK2 and xorg-xwayland-git package.
Changing xorg-xwayland-git to xorg-xwayland package seems to fix the problem to me.
Thanks a lot! It seems like this fixed my issue! I have reported this as a fix in the upstream issue I created as well, in case anyone stumbles upon the issue report there.
How did you end up discovering it was a GTK2 issue?
It seems like both packages are building from the same 24.1 branch and the biggest diff I see between the AUR package and the xorg-xwayland package is the meson build command?
diff --git a/official b/aur --- a/official +++ b/aur - arch-meson xwayland-$pkgver build \ + arch-meson xserver build \ -D ipv6=true \ -D xvfb=false \ + -D xnest=false \ -D xdmcp=false \ -D xcsecurity=true \ + -D xorg=false \ + -D xephyr=false \ + -D xwayland=true \ + -D xwin=false \ + -D xquartz=false \ -D dri3=true \ -D glamor=true \ -D xkb_dir=/usr/share/X11/xkb \ -D xkb_output_dir=/var/lib/xkb
I figured GTK2 might be also part of the problem because GIMP (a program that uses GTK2) also had launching problems.
The difference between xorg-xwayland and xorg-xwayland-git is in the source code. The first uses a tagged release (1.24.1) from the code and the second uses the latest commit.
This makes me think that the problem might be from a recent change in xwayland (maybe they removed some compatibility code that broke GTK2).
Offline
you should not be using -git packages of core libs without a good reason, assuming the good reason you had was explicit sync, that has been merged a couple releases ago and you can use the stable package.
Offline
Pages: 1