Valve have released yet another Beta for the upcoming release of Steam Deck SteamOS 3.6, this time fixing some really annoying issues. Maybe "Tenth time's the charm" will get us closer to the stable release?
This is included in the Beta and Preview update channels.
Here's what's changed:
Bluetooth
- Fixed a 3.6 regression with the Steam Controller and some other third-party controllers causing session crashes.
- Fixed an issue where Bluetooth peripherals would disconnect on session switch.
Display
- Fixed an issue where the internal display could remain blank after disconnecting an external display.
- Fixed a 3.6 regression where the selected refresh rate setting would sometimes not apply immediately.
Is there a particular bug you think needs to be solved before it goes stable? Let me know in the comments.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
hardpenguin Aug 16
Quoting: Claude_LibHave they fixed the issue where Steam Input remains in desktop mode rather than emulating a gamepad when running certain non-Steam games, namely emulator Flatpaks like PCSX2?Sounds annoying. That's the reason I use the RetroArch Steam build instead of standalone emulators.
QuoteFixed a 3.6 regression with the Steam Controller and some other third-party controllers causing session crashes.You were supposed to bring balance to force, not destroy it! :( Please Valve, more love for Steam Controller and Steam Controller revival please... :(
0 Likes
I wonder if that bluetooth fix is related to what I see on my Debian desktop - every time I start a game, my bluetooth headphones disconnect for a moment, then reconnect. Every game. Every launch. Native, proton, every time.
I wouldn't mind, but if I have a Discord chat running when it happens, Discord goes wonky which means disconnecting and reconnecting.
It's likely a wireplumber problem, but it's definitely triggered by Steam.
I wouldn't mind, but if I have a Discord chat running when it happens, Discord goes wonky which means disconnecting and reconnecting.
Aug 16 17:03:58 Groovy plasmashell[4583]: org.kde.plasma.pulseaudio: No object for name "bluez_output.B0_F0_0C_06_C9_B0.1"
Aug 16 17:03:58 Groovy plasmashell[4583]: org.kde.plasma.pulseaudio: No object for name "bluez_output.B0_F0_0C_06_C9_B0.1"
Aug 16 17:03:58 Groovy wireplumber[4193]: pw.node: (bluez_output.B0_F0_0C_06_C9_B0.1-110) graph xrun (0 suppressed)
Aug 16 17:04:00 Groovy plasmashell[4583]: org.kde.plasma.pulseaudio: No object for name "bluez_output.B0_F0_0C_06_C9_B0.1"
Aug 16 17:04:00 Groovy wireplumber[4193]: pw.node: (bluez_output.B0_F0_0C_06_C9_B0.1-110) graph xrun (0 suppressed)It's likely a wireplumber problem, but it's definitely triggered by Steam.
1 Likes, Who?
Quoting: scainebut it's definitely triggered by SteamWhat happens if you start a game without Steam?
0 Likes
benstor214 Aug 17
QuoteIs there a particular bug you think needs to be solved before it goes stable? Let me know in the comments.I would like to see this bug removed:
https://github.com/ValveSoftware/SteamOS/issues/1093
0 Likes
Quoting: KlaasQuoting: scainebut it's definitely triggered by SteamWhat happens if you start a game without Steam?
True story - I don't have any games installed outside of Steam!
But I have both a GOG account with about 50 games, and loads of freebies from Amazon Prime, so I downloaded Heroic and gave it a shot. And... goddamit, it still happens! I get the exact same errors!
So it's not Steam, it's Plasma (probably). In fact, it looks like a weird clash between pulse and pipewire, but given that I was convinced it was Steam before... I'm doubting everything!
I suspect part of the problem is that because Siduction is a rolling release, there's a few upgrades that need additional work, but I haven't noticed. For example, when wireplumber upgraded from 0.4 to 0.5, they ditched all the Lua script support, and moved everything to a new json format. So I've changed all that to support the newer 0.5 version... but what else have I missed?
I'll dig into the legacy pulse support a bit, and see what I can find.
1 Likes, Who?
Quoting: scaineIn fact, it looks like a weird clash between pulse and pipewire, but given that I was convinced it was Steam before..Well… you were mentioning pipewire and your log has
org.kde.plasma.pulseaudio errors. That's why I asked.If I were you I'd install Openbox or any other light WM and do a test without Plasma/KWin.
2 Likes, Who?
Quoting: benstor214https://github.com/ValveSoftware/SteamOS/issues/1093I've got a Logitech mouse connected to the official dock via USB dongle all the time, which I use with an USB-C extension cable and don't get the constant teleportation. Weird.
I run Firefox in gaming mode, which is tricky, since it requires a different profile if you want to keep saved tabs. If that profile is started in desktop mode, hell breaks lose, since the window in gaming mode gets resized and it is impossible to get it back to the resolution specified via command line. Also switching any element to fullscreen mode causes display issues until Firefox is restarted. Why am I writing this, since the issues are obviously caused by Firefox? Because I don't have any mouse issues in Firefox in gaming mode.
0 Likes
A bug I encounter is when trying to access the quick access menu with an Xbox controller inside a game the button combination access de QAM and the Steam menu ( the one with quit, resume options) and noticed that if the controller turns off and then on the game wont register any input.
0 Likes
Patreon
PayPal
See more from me