Opened an issue about British Columbia's new time zone not being supported in SteamOS/Gaming Mode. Hopefully our neighbours to the south will get us the updates promptly :)
とりあえず問題発生したらゲーム名込みで検索してみるべきと学んだ
というかこんな限定的な問題だったのか…
Steam Controller Pausing all games on Pop OS
I have been using Pop OS for years and love the progress with COSMIC. I also recognize this issue may not pertain to Pop OS specifically, but the fixes I have seen are not seeming to work on Pop OS 24.04 so I am curious to see if y'all have found a fix for this.
The crux of the issue is that my new steam controller thinks its in 'Desktop Mode' when I am playing games, and the B button is mapped to Escape, so it pauses all the games when I press b.
From what I can tell, the main point of the issue is that Steam cannot tell what window is active in Wayland, so Steam Input is falling back to the generic Desktop Mode.
I have tried un-mapping the B button in Desktop Mode under the advanced controller settings with no success.
I tried env -u WAYLAND_DISPLAY %command% and PROTON_ENABLE_WAYLAND=0 %command% in the command line options for some of my games to try to force the game to be rendered through XWayland with no success.
I have also tried the wrapper script mentioned in this github issue comment with no results. I did notice that there are some interesting things happening since the wrapper script exposes what %command% is. From what I can tell, Steam is trying to use some 32-bit .so files, but I am not sure if that really is the case. Here are some lines from the log from the wrapper script that show some linker issues due to the shared libraries being referenced are 32-bit (from what I can understand).
11:00:46 [wrap] start appid=367520 output=DP-2 cmd=gamemoderun /home/isaacsmith/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- /home/isaacsmith/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=367520 -- /home/isaacsmith/.local/share/Steam/steamapps/common/SteamLinuxRuntime_4/_v2-entry-point --verb=waitforexitandrun -- /home/isaacsmith/.local/share/Steam/steamapps/common/Proton 11.0/proton waitforexitandrun /home/isaacsmith/.local/share/Steam/steamapps/common/Hollow Knight/hollow_knight.exe
ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Anyone else experience this same behavior?
5 points · 4 comments
@supahvee1234 "AI is slop! Don't use AI!"
"Bro, if you think humans did not make slop pre-ai..."
Just two examples from the past of open source projects that nuked all users files.
steam-for-linux#3671
bumblebee-Old-and-abbandoned#123
2 likes · 25 views
Valve is confirming that 32-bit host libraries (especially the graphics stack) are staying for the foreseeable future, mainly for compatibility with older native 32-bit Linux games.
steam-for-linux#13015
1,470 points · 135 comments
@LuvMeSumBots @TimSweeneyEpic @wawilow108 @FortniteLinux funny because the steam linux client did have this exact issue a decade ago, without any vibe coding steam-for-linux#3671
1 like · 31 views
#Valve dice que no ofrece soporte para #Steam en procesadores #ARM 🙄
> steam-for-linux#13689 t.co
1 like · 195 views
How to get steam games to open on primary monitor?
I recently switched from Fedora KDE to Fedora Workstation because I thought Gnome had a similar workflow to my MacBook which I enjoy.
I am using two monitors, one HDMI on the left and a DisplayPort one on the right. The DisplayPort monitor is set as my primary, but many steam games start on the left. A lot of them refuse to be dragged to the right monitor altogether and just snap back to the left. I have tried many things, including setting my scaling to 100% and 200% on both monitors, setting random environment variables (recommended by the google ai) using Flatseal , trying to use gamescope (also ai recommended), and setting launch options in the game’s properties. I have had a few successful attempts, but they never last long and on reboot the same bad behavior resumes.
I have seen a similar issue posted here:
steam-for-linux#7205
But no real solution. I am wondering if anyone has managed to fix this behavior if they encountered it? There is no way you all live like this.
5 points · 3 comments
Mentions
Opened an issue about British Columbia's new time zone not being supported in SteamOS/Gaming Mode. Hopefully our neighbours to the south will get us the updates promptly :)
とりあえず問題発生したらゲーム名込みで検索してみるべきと学んだ というかこんな限定的な問題だったのか…
Steam Controller Pausing all games on Pop OS I have been using Pop OS for years and love the progress with COSMIC. I also recognize this issue may not pertain to Pop OS specifically, but the fixes I have seen are not seeming to work on Pop OS 24.04 so I am curious to see if y'all have found a fix for this. The crux of the issue is that my new steam controller thinks its in 'Desktop Mode' when I am playing games, and the B button is mapped to Escape, so it pauses all the games when I press b. From what I can tell, the main point of the issue is that Steam cannot tell what window is active in Wayland, so Steam Input is falling back to the generic Desktop Mode. I have tried un-mapping the B button in Desktop Mode under the advanced controller settings with no success. I tried env -u WAYLAND_DISPLAY %command% and PROTON_ENABLE_WAYLAND=0 %command% in the command line options for some of my games to try to force the game to be rendered through XWayland with no success. I have also tried the wrapper script mentioned in this github issue comment with no results. I did notice that there are some interesting things happening since the wrapper script exposes what %command% is. From what I can tell, Steam is trying to use some 32-bit .so files, but I am not sure if that really is the case. Here are some lines from the log from the wrapper script that show some linker issues due to the shared libraries being referenced are 32-bit (from what I can understand). 11:00:46 [wrap] start appid=367520 output=DP-2 cmd=gamemoderun /home/isaacsmith/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- /home/isaacsmith/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=367520 -- /home/isaacsmith/.local/share/Steam/steamapps/common/SteamLinuxRuntime_4/_v2-entry-point --verb=waitforexitandrun -- /home/isaacsmith/.local/share/Steam/steamapps/common/Proton 11.0/proton waitforexitandrun /home/isaacsmith/.local/share/Steam/steamapps/common/Hollow Knight/hollow_knight.exe ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. Anyone else experience this same behavior?
@supahvee1234 "AI is slop! Don't use AI!" "Bro, if you think humans did not make slop pre-ai..." Just two examples from the past of open source projects that nuked all users files. steam-for-linux#3671 bumblebee-Old-and-abbandoned#123
Valve is confirming that 32-bit host libraries (especially the graphics stack) are staying for the foreseeable future, mainly for compatibility with older native 32-bit Linux games. steam-for-linux#13015
@LuvMeSumBots @TimSweeneyEpic @wawilow108 @FortniteLinux funny because the steam linux client did have this exact issue a decade ago, without any vibe coding steam-for-linux#3671
#Valve dice que no ofrece soporte para #Steam en procesadores #ARM 🙄 > steam-for-linux#13689 t.co
How to get steam games to open on primary monitor? I recently switched from Fedora KDE to Fedora Workstation because I thought Gnome had a similar workflow to my MacBook which I enjoy. I am using two monitors, one HDMI on the left and a DisplayPort one on the right. The DisplayPort monitor is set as my primary, but many steam games start on the left. A lot of them refuse to be dragged to the right monitor altogether and just snap back to the left. I have tried many things, including setting my scaling to 100% and 200% on both monitors, setting random environment variables (recommended by the google ai) using Flatseal , trying to use gamescope (also ai recommended), and setting launch options in the game’s properties. I have had a few successful attempts, but they never last long and on reboot the same bad behavior resumes. I have seen a similar issue posted here: steam-for-linux#7205 But no real solution. I am wondering if anyone has managed to fix this behavior if they encountered it? There is no way you all live like this.