Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OOBE broken in steam.target #10

Closed
samueldr opened this issue Apr 30, 2022 · 5 comments
Closed

OOBE broken in steam.target #10

samueldr opened this issue Apr 30, 2022 · 5 comments

Comments

@samueldr
Copy link
Member

samueldr commented Apr 30, 2022

This is a known issue with the "PAL" beta, and happens on other non-steamos distros.

Workaround

Log-in to your steam account using the desktop steam interface.

@samueldr
Copy link
Member Author

samueldr commented May 2, 2022

Unsourced clues: look at strace during oobe, and see if it's trying to execute any of these, then "snitch" on the params with a "snitcher" script added to the FHS to see what we can do to make it happy:

  • /usr/bin/steamos-update
  • /usr/bin/steamos-session-select

@zhaofengli
Copy link
Contributor

I managed to get past the OS update step in the OOBE wizard, where the wizard would attempt to execute sudo -n steamos-update and fail. steamos-update itself is a shell script that can be found in the jupiter-legacy-support package in SteamOS. If no updates are found, it exits with code 7.

The other half of the problem is sudo not working in FHS environments. For now I'm working around it with a dummy sudo script that doesn't actually escalate privileges.

@samueldr
Copy link
Member Author

Has anyone tested the OOBE login flow since then?

@lheckemann, you're setting up a new Steam Deck, did you go through the OOBE wizard? (Setting up your Steam account using the Steam Deck interface.)

@lheckemann
Copy link
Contributor

I did, and it kind of worked? It got a bit confused by networks already being set up, but I was able to log in just fine like on SteamOS.

Also, for keeping track of execs, I can very much recommend execsnoop from linuxPackages.bcc -- it has a lot less overhead than strace, and there are loads more useful tools in bcc as well.

@samueldr
Copy link
Member Author

Closing, then. I think this was indeed meant to be solved by the recent work @zhaofengli put in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants