You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What seems to consistently work for me is resetting my package versions to the Arch repo from June 16 2024 (https://archive.archlinux.org/repos/2024/06/16/$repo/os/$arch, following the instructions from the How to restore all packages to a specific date Arch wiki entry), rebooting (steam will fail to launch on this boot, but it tries to upgrade) and then upgrading back to current packages and rebooting (steam will open, update, and prompt me to login). If I reboot again, after having a working configuration, the original failure happens again.
The reason I chose the June 16 2024 archive repo is because its before the KDE 6.1 update hit the Arch repos. I also tried the same procedure with the June 22 archive, and it didn't work. It could also be a coincidence.
This gist has the list of packages that were available in the June 16th repos.
I currently have Steam running properly after my downgrade/reboot/upgrade/reboot dance, and I just won't reboot until I figure it out, lol. Sorry for the wall of text, I'm kinda at a loss here as to what could be causing this. Please let me know what steps I can take to help debug.
Steps for reproducing this issue:
Fully upgrade Arch with KDE desktop packages installed/configured
Reboot into a Wayland session
Try to launch steam
The text was updated successfully, but these errors were encountered:
Many Arch users (including me) probably had xorg-xwayland-git installed because it provided explicit sync in xwayland before version 24.1 was officially released. Now that it is released, there's no real reason to use the AUR package.
Fixing this on Arch looks like running sudo pacman -S xorg-xwayland and allowing it to replace the xorg-xwayland-git AUR package.
The user on the Arch forums mentioned that its an issue with GTK2, but I'm not sure how they discovered that. I looked into the 2 packages to see if I could spot anything substantial but checking the PKGBUILD file of the xorg-xwayland-git package, it seems like its using the same upstream branch (24.1), so I'm not sure why this would behave any differently from the xorg-xwayland package (PKGBUILD link). From what I can tell, the biggest diff is in the meson build options?
Your system information
Please describe your issue in as much detail as possible:
When running the
steam
command, I expected steam to launch. Instead, Steam hangs when launched with the last log line emitted beingI tried all of the solutions in #11018, #9383, and #6148, including but not limited to:
steam --reset
steam --vgui
pacman -R steam
/pacman -S steam
)flatpak run com.valvesoftware.Steam
), with some of the previously mentioned CLI options tooSTEAM_RUNTIME=0
)~/.local/share/Steam/
and~/.steam
What seems to consistently work for me is resetting my package versions to the Arch repo from June 16 2024 (
https://archive.archlinux.org/repos/2024/06/16/$repo/os/$arch
, following the instructions from the How to restore all packages to a specific date Arch wiki entry), rebooting (steam will fail to launch on this boot, but it tries to upgrade) and then upgrading back to current packages and rebooting (steam will open, update, and prompt me to login). If I reboot again, after having a working configuration, the original failure happens again.The reason I chose the June 16 2024 archive repo is because its before the KDE 6.1 update hit the Arch repos. I also tried the same procedure with the June 22 archive, and it didn't work. It could also be a coincidence.
This gist has the list of packages that were available in the June 16th repos.
I've also been participating in this Arch BBS thread where another user is experiencing a similar issue: https://bbs.archlinux.org/viewtopic.php?id=297127
I currently have Steam running properly after my downgrade/reboot/upgrade/reboot dance, and I just won't reboot until I figure it out, lol. Sorry for the wall of text, I'm kinda at a loss here as to what could be causing this. Please let me know what steps I can take to help debug.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: