- cross-posted to:
- linux
- [email protected]
- cross-posted to:
- linux
- [email protected]
Timothée Besset, a software engineer who works on the Steam client for Valve, took to Mastodon this week to reveal: “Valve is seeing an increasing number of bug reports for issues caused by Canonical’s repackaging of the Steam client through snap”.
“We are not involved with the snap repackaging. It has a lot of issues”, Besset adds, noting that “the best way to install Steam on Debian and derivative operating systems is to […] use the official .deb”.
Those who don’t want to use the official Deb package are instead asked to ‘consider the Flatpak version’ — though like Canonical’s Steam snap the Steam Flatpak is also unofficial, and no directly supported by Valve.
I’ve never had an update fail with flatpaks?
It happens constantly both on my laptop (suse) and my Steam Deck (arch). Same exact behavior. I gave up trying to debug it, and I just keep retrying the update command until the list is empty.
I am honestly surprised, my arch desktop and my steam deck got no problems of those types. If you find what makes it happens on your systems then maybe it will help improve the tech!
If no one else has this issue, it could very well be something unique to my internet connection!
I’ve never had anything like this when I used to run arch (with Archivstall). Also not on fedora for months and now back on LMDE.
How are you closing the program? I don’t mean with the X button on the desktop environment. I mean command line programs.
What program? I just let
flatpak update
run through until it returns me to my shell.I’m sorry, I must have responded to the wrong comment. That comment was supposed to be in an entirely different conversation.
Edit: Oh, I just reviewed my inbox. I thought you replied to a different comment of mine. I’m so dumb. Carry on.
Everything alright. We all have some days where just nothing seems to be working right and we make stupid mistakes.
Just this Monday was one for me, even reported an issue to the Ubuntu trackers and upstream, turned out I just had a typo in both my code and minimal working examples.
No biggie at the end of the day.