SteamOS 3.8.28 has broken the ROG Ally Z1 Extreme
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- linux
- Domain
- operating-systems
Research direction
No source file or test is named. Start by reproducing the four reported behaviors on a ROG Ally Z1 Extreme running SteamOS 3.8.28, comparing them with the prior behavior described in the issue. Done means identifying and resolving the relevant regressions, including LED startup, POST brightness, VRR performance, and shutdown hangs.
Written by the indexing model from the issue text.
Description
Your system information
- Steam client version: SteamOS 3.8.28
- SteamOS version: SteamOS 3.8.28
- Opted into Steam client beta?: [Yes/No] No
- Opted into SteamOS beta?: [Yes/No] No
- Have you checked for updates in Settings > System?: [Yes/No] Yes
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen.
I have updated to the latest build of the steam os via settings and it has caused very bad bugs I have described below. Prior before this update everything was fine.
Steps for reproducing this issue
- Turning on rog ally z1 extreme causes the led ring lights to turn on for 3 sec than turn off(they never did this) prior before the update
- At the POST the screen brightness is very high once I get to the steam os logo it goes back to my setting (never used to do this)
- VRR toggle is causing very bad performance in game and home screen game mode(never used to do this)
- Rare bug but when I click shutdown in game mode the rog ally just hangs I had to force shut it down.
- Dominant language
- No language data
- Stars
- 2.6k
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ValveSoftware/SteamOS
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repairOpen
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ValveSoftware/SteamOS#2829 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
ValveSoftware/SteamOS#1743 · 1 comment · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ValveSoftware/SteamOS#2849 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
ValveSoftware/SteamOS#2848 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ValveSoftware/SteamOS#2846 ·
All issues in ValveSoftware/SteamOS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ComplianceAsCode/content#15152 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
paperclipai/paperclip#14372 ·
Maintainers usually reply within 1 day
-
bug 🐛 hwdb
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day