Steam Machine Desktop Mode: Sudo, Konsole, and Linux Basics

# Steam Machine Desktop Mode: Sudo, Konsole, and Linux Basics

Steam Machine ships with no password on its desktop account, which means `sudo` does not work until you set one. Valve's Desktop Mode FAQ documents that setup for Steam Machine and Steam Deck. That is the single most common thing people hit, so it is first below.

The rest of this page is the reference behind it: what Desktop Mode actually is, how to install software safely, where files live, and which commands to leave alone. Read the first two sections and stop, or use it as a lookup later.

Contents

• Set sudo password
• Open Konsole
• Enter and leave Desktop Mode
• Why your password does not appear when typing
• Sudo password vs Steam account password and PIN
• Install software with Discover and Flatpak
• Files, hidden folders, and where things live
• Basic commands worth knowing
• Permission denied
• The read-only filesystem
• What not to run
• Which tools need sudo
• Troubleshooting

Enter and leave Desktop Mode

Gaming Mode is the controller-driven interface you see by default. Desktop Mode is a full KDE Plasma desktop running underneath it, with a file manager, app store, and terminal.

To enter: press the Steam button, choose Power, then Switch to Desktop. Valve's Steam Machine feature guide describes the same path. No reboot, the interface just swaps.

To leave: double-click the Return to Gaming Mode icon on the desktop.

A keyboard and mouse make this far less painful than controller navigation. If you do not have one attached, Steam and X together brings up the on-screen keyboard.

Open Konsole

Konsole is the terminal application that ships with SteamOS. It is where every command on this page gets typed.

Find it in the application launcher, bottom-left of the taskbar, or search for it. There is nothing special about it, it is the standard KDE terminal.

Set sudo password

`sudo` means "run this one command as administrator". It is deliberately unavailable until you set a password, because Valve ships the desktop account without one. Valve's Desktop Mode FAQ explains that the desktop account needs a password before sudo can run.

In Konsole:

``` passwd ```

Enter a new password, then enter it again to confirm. That is the entire process.

The password you just set belongs to your desktop user account. There is no separate "sudo password", sudo simply asks for your account password when it needs to.

To change it later, run `passwd` again. It will ask for the current password first.

To confirm it worked, run any command with sudo in front of it:

``` sudo ls /root ```

If it prompts for the password and runs without error, you are set.

Why your password does not appear when typing

Konsole shows nothing while you type a password. No dots, no asterisks, no cursor movement.

This is normal Linux behavior, not a frozen terminal or a broken keyboard. The characters are being received. Type carefully and press Enter.

Nearly everyone assumes something is broken the first time.

Sudo password vs Steam account password and PIN

Three different things, easy to confuse:

Sudo password is your local desktop account password on this machine. It exists only on this device. Nobody else has it, and there is no reset link.

Steam account password is your Steam login, tied to your account across every device. Setting a sudo password does not change it, and vice versa.

Steam PIN is the short parental or lock code inside Steam itself. Unrelated to both.

Forgetting your Steam password is recoverable by email. Forgetting your sudo password is not, at least not simply, since there is no account recovery for a local Linux user. Store it somewhere.

Install software with Discover and Flatpak

Discover is the app store in the taskbar. It is the recommended default for installing desktop software on SteamOS, and for most software it is all you need.

Everything in Discover installs as a Flatpak, a sandboxed package that uses the writable portion of SteamOS rather than modifying the protected system. That distinction matters more than it sounds, and the next two sections explain why.

Common installs: Firefox or Chrome for browsing, Heroic Games Launcher for Epic and GOG titles, VLC for media, ProtonUp-Qt or ProtonPlus for managing Proton versions.

Flatpaks do not need sudo. If a tutorial tells you to install something with `sudo pacman`, read the read-only section before you follow it.

Files, hidden folders, and where things live

Dolphin is the file manager. `~` is shorthand for your home folder, which is where everything of yours lives.

Linux hides any file or folder starting with a dot. In Dolphin, Ctrl+H toggles them visible. A great deal of what you will look for is hidden by default, so this shortcut is worth memorizing.

Paths worth knowing:

That `compatdata` path is the one that matters if you ever switch Proton versions, since game saves can live inside those prefixes.

Your home folder path includes your username. SteamOS is built around a fixed default account name, so unless you deliberately changed it, `~` resolves correctly and you rarely need to type the full path.

Basic commands worth knowing

Five commands cover most of what a guide will ask you to do. None of these change anything, except the last two.

``` pwd show which folder you are currently in ls list what is in this folder ls -la list everything, including hidden files cd Downloads move into a folder cd .. move up one level cd go back to your home folder ```

Copying and moving:

``` cp file.txt ~/Documents/ copy a file cp -r folder/ ~/Documents/ copy a folder and its contents mv file.txt ~/Documents/ move a file mv old.txt new.txt rename a file ```

Two habits worth building early. Press Tab to autocomplete file and folder names, which prevents typos in long paths. And `mv` with an existing destination filename overwrites it silently, with no confirmation and no undo.

Permission denied

The most common error you will see. It means the file or folder you are touching belongs to the system rather than to you.

Three causes, in order of likelihood:

You need sudo. The command is fine, it just requires administrator rights. Put `sudo` in front and enter your password. If you have not set one yet, that is the sudo password section.

You have not set a password at all. Sudo will not work regardless of what you type. Same fix.

You are trying to write to the read-only system. Sudo alone will not help here, and the next section explains why.

A related error, `command not found`, means something different: the program is not installed, or it is a Flatpak that is not on your path. Not a permissions problem.

The read-only filesystem

SteamOS is built on Arch Linux, but with an immutable core. The system partition is read-only, and SteamOS updates overwrite it wholesale rather than patching it piece by piece.

Two consequences:

It is hard to break permanently. A bad tweak usually does not survive an update, which is a feature. Updates apply cleanly because the system does not have to reconcile your changes.

Anything you install outside Flatpak may be wiped by the next update. Packages installed with `pacman` live on the system partition, so a SteamOS update replaces them. This is not a bug, it is the design.

You can disable the protection:

``` sudo steamos-readonly disable ```

And restore it:

``` sudo steamos-readonly enable ```

Check the current state with `status` in place of either.

Do this only when a specific task requires it, and turn it back on immediately after. Leaving it disabled buys you nothing and removes a safety net.

The practical rule: use Flatpaks when one is available. They use the writable portion of SteamOS and avoid touching the read-only system at all.

What not to run

`sudo rm -rf` on anything you are unsure about. No confirmation, no recycle bin, no undo. Retyping the path slowly before pressing Enter is a good habit.

Random commands from forums and videos. Especially anything piping a downloaded script straight into a shell. Read what it does first, or do not run it.

`sudo pacman -S` for general software. It works, it puts files on the read-only partition, and the next update removes them. Use Discover.

Changing your username. SteamOS is designed around its default account name and depends on it in ways that are not obvious. Attempts to change it typically fail, and the ways that succeed create problems later.

Leaving read-only disabled after you have finished whatever needed it.

If you follow a pacman tutorial anyway, you will likely hit keyring and signature errors, which is its own rabbit hole. Another reason Flatpak is the better default.

Which tools need sudo

Most popular tools do not, which surprises people.

Decky Loader does need it. The installer sets up a system-level service, so it prompts for your password during installation. This is the most common reason people find this page.

EmuDeck is mostly user-space and installs emulators as Flatpaks, but parts of setup can ask for elevated access depending on what you enable.

ProtonUp-Qt and ProtonPlus generally do not. They install custom Proton versions into your user folder, which needs no special permission.

Drive and storage utilities usually do. Formatting, partitioning, and mounting a drive at a system path all touch hardware and system configuration.

Anything from Discover does not. Flatpaks install to user space by design.

If a tool asks for your password and you did not expect it, that is worth a moment's thought rather than reflexive typing. Legitimate reasons exist, and so do bad ones.

Troubleshooting

"passwd: Authentication token manipulation error" usually means the command was run in an odd context. Close Konsole, reopen it, try again.

Sudo says my password is wrong, but it is right. Check Caps Lock, and confirm you are entering your local desktop password rather than your Steam account password. They are different, see above.

I forgot my sudo password. There is no reset link. The recovery path involves booting into a recovery environment, which is more involved than most people expect, so this is the argument for writing it down when you set it.

A guide told me to run something and it failed with read-only errors. The read-only system is doing its job. Check whether a Flatpak version of what you want exists before disabling it.

Everything I installed disappeared after an update. Installed via pacman, almost certainly. See the read-only section. Reinstall as Flatpaks if possible.

Desktop Mode will not go back to Gaming Mode. Use the Return to Gaming Mode desktop icon rather than logging out. If it is unresponsive, a reboot returns to whichever mode is set as default.

One note on sources

The commands here are standard SteamOS behavior documented by Valve. Steam Machine runs the same Desktop Mode documented in Valve's Steam Machine feature guide and Desktop Mode FAQ, so those are the references to check when a future SteamOS update changes a detail. Anything device-specific that changes will be updated here.