this post was submitted on 24 Dec 2025
308 points (98.4% liked)

linuxmemes

28596 readers
570 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    308
    It's really not that hard! (feddit.org)
    submitted 1 day ago by mech@feddit.org to c/linuxmemes@lemmy.world
    46 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] tal@lemmy.today 4 points 1 day ago* (last edited 1 day ago) (1 children)

    Most of that is setting up third-party apt repos, which I don't believe is necessary. Steam's in the Debian trixie repo.

    https://packages.debian.org/stable/steam

    EDIT: I'd guess that the following would probably work on a Debian trixie system:

    If you have your system set up for only 64-bit packages, you'd need this at some point prior to the install, to let your system use 32-bit packages, since Steam's only available as a 32-bit binary:

    $ sudo dpkg --add-architecture i386

    I think that deciding whether to use both 64-bit and 32-bit packages or not is an option in the Debian installer, but I might be misremembering.

    You can update your list of packages at this point, upgrade, all that, but that goes for any install operation; there's nothing specific to Steam there. If you've just added 32-bit packages for the first time above, then you probably do want to update the list of packages, since your system won't have a list of 32-bit packages yet.

    $ sudo apt update

    But then it's just like any other installation of software.

    $ sudo apt install steam

    That actually just contains, as I recall, the Steam installer

    enough to pull down and install the current Steam environment for a given user, which happens next time you run the Steam binary.

    $ steam

    EDIT2: I guess that assumes that you do have "contrib" enabled on the Debian repo, and I don't know whether that's enabled by default by the Debian installer or whether it's an option during install or what. I do distinctly remember one point in time when "non-free-firmware" was not enabled by default, because I always had to turn it on to get support for , but I don't know whether contrib is always enabled or not. I have main, contrib, non-free, and non-free-firmware enabled. From /etc/apt/sources.list.d/debian.sources:

    Types: deb deb-src
URIs: http://mirror.i3d.net/debian/
Suites: trixie
Components: main contrib non-free non-free-firmware 
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
    [–] Resplendent606@piefed.social 7 points 1 day ago

    Using the official Valve repository is my preferred method because it provides a direct line to the developers, ensuring you get the latest GPG keys and installer updates immediately without waiting for them to make their way through the Debian maintainers. While the Debian repo is convenient, it requires you to enable contrib and non-free components globally across your entire system. The method I suggested adds Steam as a specific source without cluttering your main package list with other non-free software. This also makes the installation more consistent across different versions of Debian. Whether you are on Stable or Testing, you are not at the mercy of Debian’s specific package transitions or library freezes, which can occasionally break the Steam bootstrap process in the community-maintained version. I do not believe either way is better, just different for different types of users.