Just install the lib32-libnm package. The one Steam is supplying is outdated with the new libgudev 238-1, by installing your own lib32-libnm your system will use that over Steams one and it should launch fine.
Debian 12 shipped with the latest kde plasma version, but the distro is designed to be stable, with a capital S. The packages will not update until the version does.
Flatpaks are a great way to get modern software on a stable OS like debian. If neon has a flatpak version, it would be a good answer.
I was using EndeavourOS when I ran into the wall that a lot of stuff didn’t have builds on AUR that I needed (and didn’t feel like compiling myself or they didn’t provide source code)
I would recommend using Linux Mint. It is Ubuntu without Gnome Shell and snaps. They use Flatpak instead. I have been enjoying it ever since I jumped ship from Ubuntu about 2 years ago.
It seems you translated it. 😅 Well it is a saying… When someone is excited or proud of someone/something. I don’t know the specifics (even though I am a native). So please, if anyone else wants to explain, feel free to do so…
I’m not a native but I can try to explain. Greek has two forms of expressing possession: the first is simply the genitive of the personal pronoun (in this case μου is the genitive of the first person singular pronoun εγώ). When expressing possession in this way it always follows the noun it refers to whereas the article comes before e.g. “my house” > “το σπίτι μου” and it’s invariable. (Note that in English possessives are determiners and can not co-exist with articles it’s either one or the other, in Greek this is not the case). The second form is in combination with “δικός” and these behave more like adjectives and must agree in gender and number with the noun they refer to “my house” > “το δικό μου σπίτι” vs “my houses” > “τα δικά μου σπίτια”.
I used it as my main distro for about a year, and moved on right before the “abandonment saga” happened. It was a nice and performant distro, but lacked some stuff I needed, mostly support from a few projects and apps I needed to use.
I wouldn’t recommend it as a main distro for at least 5 years after what happened, but would keep an eye out to use on a spare machine or a VM.
Nowadays I’d either settle on openSUSE Tumbleeweed for rolling-release. I’m personally more insterested in stability though (and not having to update stuff every 2 days or so), so I’m going team Debian.
Snaps I get, but Ubuntu? Aside from an asinine application process to get hired a Canonical, they did a lot to push for a more straightforward Linux desktop experience. Their time has passed, but cancer is a bit too much for me, considering all the fantastic offshoots.
Context: I came to Ubuntu from Gentoo. Debian before that and a brief flirt with the hot fantastic mess that was Mandrake when I first discovered Linux.
Snaps is just the latest controversial tech they haved pushed for. They have a long history of pushing for things they have created that people don’t want or don’t want their implementation of (like upstart or the original unity desktop env). Or pushing for stuff before it is ready (like pulseaudio).
Nothing wrong with pushing for your own tech, but they do seem to miss the mark a lot on what they want to introduce. And keep upsetting the community over it.
There is a problem with pushing tech if that tech is proprietary — such as with Snaps.
Unity I don’t think was ever that controversial, except that Ubuntu was sending all desktop search queries to Amazon at one point, which was, of course, terrible privacy-wise. The reason why Unity died is because Ubuntu decided it’s not worth the money to maintain it.
There was a lot of community backlash when they first released unity as its own thing. Lots of people hated it because it was very different from what came before. That is what made it controversial.
I faced this as well on KDE and got around it by creating a window rule to match it by window title and force a .desktop name to the vs code window, so it shows the correct icon on the taskbar. I wonder if there is a similar functionality on Gnome?
KWin allows the end-user to define rules to alter an application’s window attributes.
For example, when an application is started, it can be forced to always run on Virtual Desktop 2. Or a defect in an application can be worked-around to force the window above others.
It’s not a click bait per se. Even after deb support they will use only snap for applications that has a snap package and only debs if it hasn’t got any snap package afaik.
This is my preferred way off doing things, but trying to glue VSCode + Android Studio + the Flutter SDK + Docker + … together via Flatpack was an exercise in pain and sadness last time I tried it.
Getting all my normal boring desktop apps via Flatpack is awesome, but for a developer it just doesn’t seem practical right now
I’ve been using more and more flatpaks lately on arch and fedora based distros, i have no idea how snaps compare but seems similar? Seems an odd push from Ubuntu, but could make more sense than deb packages for non techy users perhaps?
Snap is portable to other distros, look at the official website and you see a list of distros, you can use snap on. That doesn’t mean that there is no vendor lock-in, just a different kind. Snap as a format grew out of Cannonicals effort in the mobile field. Snaps where supposed to be the truly convergent successor to click, the packaging format used by Ubuntu Touch. And this history is baked into its DNA. It’s right there on the snapcraft website: “The app store for Linux”. As such Cannonical has always courted proprietary software and/or software by big companies (VS Code was first released as a snap for a reason). I think that they have always have had an eye on one day adding app payments and the sweet, sweet 30% cut they can take from every sale
Solus and Manjaro are shipping Snap installed by default and I’ve never had a problem installing snapd on fedora. All I ever had to do for that was run a single standard dnf install. Apparmor doesn’t pose the problem you think it does
Running software unsandboxed is breaking most of the value of snap. Not only is it insecure many of the portability promises are actually broken and it can load incorrect libraries, etc.
Fedora deleted snap from its repos years ago then it returned. It is a broken mess.
Canonicals response has been: We don’t care, fix it yourself.
It is an awful non-portable solution when a real portable solution exists.
Because it’s extra work to make it open source and few outside of Canonical are interested in contributing. Open sourcing an existing component and maintaining it as such has non-trivial overhead. In that case that work is better spent on other, higher priority items. My guess is that they’ve gauged that the cloud end being open source won’t move the needle on who uses Snap and Ubuntu so they’ve deemed it low priority. Personally I’m using Debian and Ubuntu and therefore Canonical has root on some of my systems. Given I can implement a cloud end for Snap, it bares very little importance to me that today the cloud end isn’t open source since it’s run by the folks that have root on my system anyways as well as supply all other packages on my Ubuntu systems. In fact we don’t even know what the cloud end for the apt repos is. It could easily be Sonatype Nexus. For me the important bit is the client and installer side of Snap since I can’t implement that in a relatively small amount of time. :)
Ubuntu / Canonical were working on Snap for some years when Flatpak came on the scene. They’ve been shipping Ubuntu bits using it since 2016. In addition to the legacy, Snap is more versatile than Flatpak in that it can be used to package pretty much anything, including system bits. It’s also had a secure sandbox from the start. Changing to Flatpak would be a functionality downgrade for Canonical and Ununtu maintainers using Snap. In addition Flatpak can be used along with Snap on Ubuntu so there’s no need to not use both for whoever finds that useful. Snap lets Ubuntu ship software using less work, which means more up-to-date bits in Ubuntu. Users can install other software via Snap or Flatpak, whichever they find more useful.
In my experience, performance of snap apps is just abhorrent. The consume a huge amount of disk space and, whether it’s due to that or not, they have extremely long load times.
Principles aside, this just makes them unusable for me. I use flatpak when there’s no other option, but strive to use deb either natively or through PPA.
What is your definition of stability? I have used Arch for about ten years without any major breakage, but sometimes you do have to do some manual tinkering if a package stops working. So it’s stable enough for me, but maybe not for others. Since it is a rolling release, packages are generally being updated quite rapidly.
I think that any modern rolling release distro would fit the bill though.
This here! I actually have had really good luck using Arch. I’ve been running it for only a month now and I make certain to patch/update once a week. Thus far it has not left me stranded. I think Arch is underrated as an OS.
I don’t think Arch is anywhere near “underrated”. The “I use Arch, btw” meme didn’t come out of nowhere. A lot of distros are based on Arch too. Even SteamOS (so the Steam Deck is essentially powered by Arch).
In that regard: yes, Arch is awesome. I use it, btw.
You will only notice the downside of a rolling release distribution when using it for years. Large breaking changes might unexpectedly be applied to your system, instead of at fixed points in time like with other distributions.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.