Reading PKGBUILD won't save you if you don't read the code or if the PKGBUILD installs a prebuilt bin.
Same as Slackbuild or a third-party APT repository: you need to understand what a supply-chain attack is and do your duly work to prevent it, or stick with the consequences.
My experience with Bazzite was good but far from perfect. It worked out of the box, but was really slow compared to a Fedora Kinoite installed on a lower-spec laptop.
Then I have some issues with flatpaks, but that was my fault for not understanding the system and being to used to a traditional linux (I'm coming from Slackware and Debian).
But the last straw was the driver/kernel combo which broke some of my games: they work day 1, starts to crash after an update and no load at all after another upgrade.
It was because my PC was really old and the hardware and the drivers are not supported anymore on the main kernel, so it's kind of a ME problem and one which I would have with other modern distros, but is also a problem that is harder to fix on Bazzite then other distros. Not impossible, but harder beyond what was my available patience.
So I switched to Debian stable, everything works, my PC is faster then ever and I have no fear of broken updates.
Bazzite is really great, but it's not for everyone.
My case: I have an nvidia GTX 980. It's old but it's what I have.
Nvidia dropped its support from driver version 595.
Driver 580 is what I need, it worked until 7.0 but no longer in 7.1 (was using Fedora 44). Since my hardware is old I switched to Debian Trixie.
Another example is the facetime HD Webcam of macbook pro: to make it work you have to install OSx or download a recovery image, compile a C program to extract a specific binary blob, then use that blob to recompile the driver on your kernel.
There are lots of examples: it's a big world, with lots of hardware and mostly no producer interested in the Linux world.
Broadcom hardware (WiFi cards an webcams in particular).
Plus there are quirks with some proprietary driver version not building against some kernel version...
With unsupported hardware and closed drivers you are always on the lookout for some breakage.
And it's not a Linux problem nor a complaint on distro maintainers. It's manufacturers that are shit.
Unfortunately this is the beauty and the bane of choice and freedom: everyone has it's own opinion of what is good and what is not, and can easily make it so, fragmenting the offer and confusing the newbie losing it to the less free alternative. Works in Linux, works in politics.
There is no way to have freedom of choice AND a united front against the alternative.
I use transmission through sonarr, radarr and prowlarr, and those are the folders. Then I tag a torrent of it is a freeleech or if it has been already managed by sonarr or radarr.
I tried GrapheneOS last Sunday and cannot male whatsapp work. Tried the play store, the aurora, github, official website, nothing worked, the authentication always failed.
Unfortunately my whole social life and family are there, so for me it's a no go for now.
Yes: it was the only way to update the software inside. It was so old some pages refused to load, and was really slow.
It was a painless and quick procedure and it has been working better than ever since then: decent hardware with (now) very good software.
My wife has a 2015 MacBook that was too slow/old with MacOs.
I installed Fedora Kinoite, choosing an immutable distro because I wanted to make sure the base system always works.
The only issue I had was (as always) with wifi drivers, but done that it was smooth sailing for the last year. She is not Linux savvy but every week says how much she loves the KDE interface.
The system is quicker than MacOS and battery runs for much longer than before.
It's a work PC so I cannot vouch for gaming.
On my 2014 PC I'm using Fedora 44 with KDE, which defaults to Wayland: not problems whatsoever, but some applications say "Wayland support is experimental, beware".
I switched to X11 after a suggestion to debug some issues with a game. The issues was not fixed, all the other applications I've tried are still working flawlessly. PLUS the KDE night light feature is working (was not in Wayland). So I stayed with X11.
On my wife MacBook (2015) I installed Kinoite, defaults to Wayland. Everything works, but Rustdesk renders VERY small. I have not tried X11 on that, and will not try it.
Try both with all your applications and setups and choose the smoother experience. Make security a secondary priority: if it was the first you have less attack surface sticking to terminal only.
It's not, it's a problem of every package manager that do not use sources and checksums, like rust and python.
Take a look at this article that does a better job then me at explaining the situation.
I'm Italian and I would try this. Also, fudge those "purists" of Italian food: every family has it's own recipe for everything different from their neighbors', there's no or little historical documents about dishes still served and most "based" Italian food was invented by Italian emigrants coming back home with inspiration from where they were.
Cuisine is mixing and experimenting, tradition is the death of good food.
I switched to Bazzite on my gaming rig a month ago and felt great. I managed to install and mod Skyrim effortlessly and yesterday I installed Tarkov and SPT with no problem whatsoever.
Highly recommend.
But check if your favorite games are compatible, mainly the multiplayer ones: Tarkov can only be single player PvE, GTA is story mode only and forget about Destiny 2.
Not a problem for me, plenty of alternatives, but you should check for yourself.
Exactly, that is IMHO a not-so-sane default that some application launcher adopts. Thankfully you can switch to a more "normal" behavior, it's a flag somewhere in the configuration menus for the application launcher, at least in KDE and in XFCE
Reading PKGBUILD won't save you if you don't read the code or if the PKGBUILD installs a prebuilt bin. Same as Slackbuild or a third-party APT repository: you need to understand what a supply-chain attack is and do your duly work to prevent it, or stick with the consequences.
My experience with Bazzite was good but far from perfect. It worked out of the box, but was really slow compared to a Fedora Kinoite installed on a lower-spec laptop. Then I have some issues with flatpaks, but that was my fault for not understanding the system and being to used to a traditional linux (I'm coming from Slackware and Debian). But the last straw was the driver/kernel combo which broke some of my games: they work day 1, starts to crash after an update and no load at all after another upgrade. It was because my PC was really old and the hardware and the drivers are not supported anymore on the main kernel, so it's kind of a ME problem and one which I would have with other modern distros, but is also a problem that is harder to fix on Bazzite then other distros. Not impossible, but harder beyond what was my available patience.
So I switched to Debian stable, everything works, my PC is faster then ever and I have no fear of broken updates.
Bazzite is really great, but it's not for everyone.
It is not stupid, it just has a different use case.
My case: I have an nvidia GTX 980. It's old but it's what I have.
Nvidia dropped its support from driver version 595.
Driver 580 is what I need, it worked until 7.0 but no longer in 7.1 (was using Fedora 44). Since my hardware is old I switched to Debian Trixie.
Another example is the facetime HD Webcam of macbook pro: to make it work you have to install OSx or download a recovery image, compile a C program to extract a specific binary blob, then use that blob to recompile the driver on your kernel.
There are lots of examples: it's a big world, with lots of hardware and mostly no producer interested in the Linux world.
Broadcom hardware (WiFi cards an webcams in particular). Plus there are quirks with some proprietary driver version not building against some kernel version...
With unsupported hardware and closed drivers you are always on the lookout for some breakage.
And it's not a Linux problem nor a complaint on distro maintainers. It's manufacturers that are shit.
Unfortunately this is the beauty and the bane of choice and freedom: everyone has it's own opinion of what is good and what is not, and can easily make it so, fragmenting the offer and confusing the newbie losing it to the less free alternative. Works in Linux, works in politics.
There is no way to have freedom of choice AND a united front against the alternative.
I use transmission through sonarr, radarr and prowlarr, and those are the folders. Then I tag a torrent of it is a freeleech or if it has been already managed by sonarr or radarr.
Transmission has tags and folders
I tried GrapheneOS last Sunday and cannot male whatsapp work. Tried the play store, the aurora, github, official website, nothing worked, the authentication always failed. Unfortunately my whole social life and family are there, so for me it's a no go for now.
Before Fedora I was using Bazzite and fell on the same problem. I can see the use case of an immutable distro, but it's not mine ¯\(ツ)/¯
Yes: it was the only way to update the software inside. It was so old some pages refused to load, and was really slow. It was a painless and quick procedure and it has been working better than ever since then: decent hardware with (now) very good software.
My wife has a 2015 MacBook that was too slow/old with MacOs. I installed Fedora Kinoite, choosing an immutable distro because I wanted to make sure the base system always works. The only issue I had was (as always) with wifi drivers, but done that it was smooth sailing for the last year. She is not Linux savvy but every week says how much she loves the KDE interface. The system is quicker than MacOS and battery runs for much longer than before. It's a work PC so I cannot vouch for gaming.
On my 2014 PC I'm using Fedora 44 with KDE, which defaults to Wayland: not problems whatsoever, but some applications say "Wayland support is experimental, beware".
I switched to X11 after a suggestion to debug some issues with a game. The issues was not fixed, all the other applications I've tried are still working flawlessly. PLUS the KDE night light feature is working (was not in Wayland). So I stayed with X11.
On my wife MacBook (2015) I installed Kinoite, defaults to Wayland. Everything works, but Rustdesk renders VERY small. I have not tried X11 on that, and will not try it.
Try both with all your applications and setups and choose the smoother experience. Make security a secondary priority: if it was the first you have less attack surface sticking to terminal only.
You can use a yubikey or a custom file to be provided when you open the database. It's a kind of MFA.
It's not, it's a problem of every package manager that do not use sources and checksums, like rust and python. Take a look at this article that does a better job then me at explaining the situation.
Thanks! I'm using too many of those IRL, plus I couldn't miss the opportunity to use "fudge" in a culinary context 😁
I'm Italian and I would try this. Also, fudge those "purists" of Italian food: every family has it's own recipe for everything different from their neighbors', there's no or little historical documents about dishes still served and most "based" Italian food was invented by Italian emigrants coming back home with inspiration from where they were.
Cuisine is mixing and experimenting, tradition is the death of good food.
I switched to Bazzite on my gaming rig a month ago and felt great. I managed to install and mod Skyrim effortlessly and yesterday I installed Tarkov and SPT with no problem whatsoever. Highly recommend.
But check if your favorite games are compatible, mainly the multiplayer ones: Tarkov can only be single player PvE, GTA is story mode only and forget about Destiny 2. Not a problem for me, plenty of alternatives, but you should check for yourself.
We call this Krapfen
Exactly, that is IMHO a not-so-sane default that some application launcher adopts. Thankfully you can switch to a more "normal" behavior, it's a flag somewhere in the configuration menus for the application launcher, at least in KDE and in XFCE