Linux

48333 readers

614 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

770

Canonical's Steam Snap is Causing Headaches for Valve (www.omgubuntu.co.uk)

submitted 10 months ago by pnutzh4x0r@lemmy.ndlug.org to c/linux@lemmy.ml

262 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] dandroid@dandroid.app 2 points 10 months ago (1 children)

My only complaint about flatpak is that updating them fails like 50% of the time for seemingly no reason, and I just have to run the update command over and over until they are all updated.

[–] PlexSheep@feddit.de 6 points 10 months ago (1 children)

I've never had an update fail with flatpaks?

[–] dandroid@dandroid.app 2 points 10 months ago (2 children)

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.

[–] UnsavoryMollusk@lemmy.world 2 points 10 months ago (1 children)

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!

[–] dandroid@dandroid.app 1 points 10 months ago

If no one else has this issue, it could very well be something unique to my internet connection!

[–] PlexSheep@feddit.de 1 points 10 months ago (1 children)

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.

[–] dandroid@dandroid.app 1 points 10 months ago (1 children)

How are you closing the program? I don't mean with the X button on the desktop environment. I mean command line programs.

[–] PlexSheep@feddit.de 1 points 10 months ago (1 children)

What program? I just let flatpak update run through until it returns me to my shell.

[–] dandroid@dandroid.app 1 points 10 months ago* (last edited 10 months ago) (1 children)

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.

[–] PlexSheep@feddit.de 2 points 10 months ago

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.