We do often include affiliate links to earn us some pennies. See more here.

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.
9 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. You can also follow my personal adventures on Bluesky.
See more from me
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
18 comments

Mohandevir Aug 15
How long has it been since they started working on version 3.6?

I'm still on the stable branch, on my LCD Steam Deck... Am I missing a lot?
Liam Dawe Aug 15
How long has it been since they started working on version 3.6?

I'm still on the stable branch, on my LCD Steam Deck... Am I missing a lot?
It first landed into Preview back in early May.
ToddL Aug 15
I'm always tempted to try out these Preview/Beta builds but too afraid that'll make changes on my Steam Deck that might cause more problems. Now, if I had a spare Steam Deck, I would go for it but don't have the funds for another one right now.
CatKiller Aug 15
View PC info
  • Supporter Plus
I'm always tempted to try out these Preview/Beta builds but too afraid that'll make changes on my Steam Deck that might cause more problems. Now, if I had a spare Steam Deck, I would go for it but don't have the funds for another one right now.
All you need to do is run a gaming website for many, many years, and then Valve will send them to you for free. EZ.
ToddL Aug 15
I'm always tempted to try out these Preview/Beta builds but too afraid that'll make changes on my Steam Deck that might cause more problems. Now, if I had a spare Steam Deck, I would go for it but don't have the funds for another one right now.
All you need to do is run a gaming website for many, many years, and then Valve will send them to you for free. EZ.
I guess I better start cracking on that website in hopes of scoring a Steam Deck in the future
RevenantDak Aug 15
I'm always tempted to try out these Preview/Beta builds but too afraid that'll make changes on my Steam Deck that might cause more problems.

It's definitely a possibility, and why it's beta. I switch between Stable and Beta and vis a versa when I **have** a problem, and it's worked well for me. I don't switch builds to "try out" a new feature.
Claude_Lib Aug 15
Have 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?
Woodlandor Aug 15
I'm always tempted to try out these Preview/Beta builds but too afraid that'll make changes on my Steam Deck that might cause more problems. Now, if I had a spare Steam Deck, I would go for it but don't have the funds for another one right now.

I’m always running Preview, but I live dangerously 😎
jams3223 Aug 16
I'm always tempted to try out these Preview/Beta builds but too afraid that'll make changes on my Steam Deck that might cause more problems. Now, if I had a spare Steam Deck, I would go for it but don't have the funds for another one right now.

I’m always running Preview, but I live dangerously 😎
Like my grandfather always used to tell me, "Little man, if you ain't doing nothing with your life then put it on the line for you're passion".


Last edited by jams3223 on 16 August 2024 at 12:20 am UTC
Oh yes finally they fixed the display issue. It is so damn annoying if you want to play on a TV and have to reboot the Deck several times for it to pick up any display at all. If they also fixed the issue where all displays stay blank. External as well as internal 😅
hardpenguin Aug 16
Have 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.

Fixed 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... :(
scaine Aug 16
View PC info
  • Contributing Editor
  • Mega Supporter
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.

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.
Klaas Aug 16
but it's definitely triggered by Steam
What happens if you start a game without Steam?
benstor214 Aug 17
View PC info
  • Supporter
Is 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
scaine Aug 17
View PC info
  • Contributing Editor
  • Mega Supporter
but it's definitely triggered by Steam
What 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.
Klaas Aug 17
In 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.
Klaas Aug 17
https://github.com/ValveSoftware/SteamOS/issues/1093
I'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.
tistasis Aug 18
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.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register