SteamOS 3.6 is live on the “main” update channel, and it is very buggy. (Note: the most bleeding edge update channel is called main. 3.6 is only live on the “main” channel, not any of the stable or beta channels).

I had switched to main to get 3.5 early, and 3.5 had spent so much time in the main channel that it’s been very stable for the last few months. However 3.6 has been rough, game mode would crash and restart everytime a decky plugin did something, and it broke my desktop mode completely. I’ve downgraded to beta-candidate (which is still 3.5) and things are much better.

I know that staying off the most bleeding edge update channels if you want a stable experience is common sense, but I think a lot of people got impatient for 3.5 and may have been lulled into a false sense of security by how stable the 3.5 main update builds were recently.

  • Fubarberry@sopuli.xyzOPM
    link
    fedilink
    English
    arrow-up
    25
    ·
    1 year ago

    Sorry, I think I misled you. The “main” channel is the most bleeding edge update channel name. After that you have beta-candidate, beta, stable candidate, and stable. 3.6 is live on the “main” channel only, so it definitely shouldn’t affect regular steamOS users.

    • OCT0PUSCRIME@lemmy.moorenet.casa
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I haven’t touched my steam deck in a month or 2. Is there a process for switching back? Just ignore the pending update, switch the channel, then check for updates again?

      • Fubarberry@sopuli.xyzOPM
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        Yes, you just pick a different update channel, check for updates, and it will let you rollback to an older update.

        There can be problems though, one time I updated and it wouldn’t let me downgrade. I had to wait until the next update fixed it before I could downgrade. And this time when 3.6 broke part of my desktop mode, downgrading didn’t fix it and I had to do a lot more troubleshooting to get it going again.