There is no reason to “hate” Ubuntu but there are better choices.
What are those better choices then (for those who currently use the non-LTS Ubuntu releases and don’t want to move to rolling releases or LTS-only releases)?
I was an Ubuntu person for a long time, and when reading criticism about the inability to upgrade versions, I realized that had been my entire experience. I decided to give a rolling release a chance, and it’s been amazing.
I use arch(installer)btw. 🐧 AURs are pretty ingenuous, which is just pulling and compiling a git. Maybe a little less secure, but look at what happened to the snap store this year.
If you want to try a rolling release but didn’t want to use Arch, there’s always Fedora, & OpenSuSE Tumbleweed.
Outside of that, for non Ubuntu distros you could do OpenSuSE regular, or for true LTS use Rocky. Or take the red pill and go with Hannah Montana’s Linux.
This is looking really promising! Pipewire already has pretty much solved audio issues (at least for me) entirely and now with HDR on the cusp, the year of the Linux desktop is nigh! Barring some Adobe BS and CAD stuff, there really isn’t much left
Ubuntu is nice. Apt/DEB works as they should. Some default apps, mostly browsers, are snaps now, but this does not bother you at all. You were getting them from your distro anyway.
Flatpak and AppImages work just fine if you need them.
The Ubuntu desktop (any flavour) just works. Others are different, but nothing is bad about Ubuntu.
Ubuntu is trying new things, proprietary to their ecosystem, e.g. Unity or smap. On the big picture, those are experiment. Ubuntu is still Linux.
The community reaction to snap is overblown. So Canonical developed something you don’t like? Ignore it. This has mostly been a waste of time for them.
(Yes, maybe that dev time would be better soent on flatpak or open-source apps. But that’s their time. I’m not paying Ubuntu developers, so can I really complain?)
Not spesifically a tool to put on a USB stick, but Ventoy is worth checking. I’ve had a bit mixed results with it on older hardware but when it works it’s pretty easy to manage your carry-on-tools.
In the tint2 docs do a ctrl-f for ‘icon’ — does any of that look like it could be of any use to you? I am not sure I understand the issue but maybe this:
launcher_icon_theme = name_of_theme : (Optional) Uses the specified icon theme to display shortcut icons. Note that tint2 will detect and use the icon theme of your desktop if you have an XSETTINGS manager running (which you probably do), unless launcher_icon_theme_override = 1.
launcher_icon_theme_override = boolean (0 or 1) : Whether launcher_icon_theme overrides the value obtained from the XSETTINGS manager. (since 0.12)
If not try searching for ‘icon’ in the rest of the repo, issues etc.
Hibernation or suspend? 2 different things. For hibernation you need a swap space at least the size of your RAM, and then the laptop is powered off after this.
For suspend, in your dmesg, see if you have:
ACPI: PM: (supports S0 S3 S4 S5)
if you have S3 your laptop should lost only a few percent.
do a:
cat /sys/power/mem_sleep
what does it says?
New CPU/BIOS/PC/Laptop only support something called “s0 idle” meaning it is like a cellphone, everything is running, and each drivers/components/os should enter low power themselves, if they do not, well, your battery is draining.
S3 means “suspend to RAM”, only RAM is powered and everything else is off, your laptop can stay like this for days. I don’t know who decided that this is bad and your laptop should be like your cellphone, always running?!?
I wouldn’t call it hate, more like disapprobation with Canonical’s choices. No one have to use Ubuntu, we have tons of distro to choose. If someone wants LTS, you can always go pure Debian way, it’s not hard to install as it’s used to be (for beginners), or there is Linux Mint Debian Edition. You can easily use flatpaks with these and keep your software up-to-date.
strictly speaking, NixOS doesn’t have repositories.
NixOS has “derivations” (rules are written in the Nix language to generate a script that builds a package, which is called a derivation - yes, everything is built from source to the extent possible/reasonable) and “platforms” (the system that builds the derivation OR the system the derivation is built for). A “platform” is e.g. the CPU architecture, the libc used, the target kernel (there’s most support for Linux and Darwin, which is the macOS kernel, but e.g. FreeBSD is supported to some extent too). The derivation code may well be shared across platforms, though often platform-specific workarounds are required.
Of course, different platforms have different support. Some platforms have derivations from nixpkgs (the NixOS git repo) regularly built for them and put into the official binary cache (which stores the derivation outputs, i.e. ready-built packages for a certain set of inputs, which generally match what you would’ve built from source because Nix strives for reproducibility, you’re still free to override a package’s inputs and build it from source). linux-aarch64 is one of such platforms. Other platforms may only have a small set of core packages like gcc built for them, or simply require building absolutely everything from source.
The reason nixpkgs is not a repository (though I guess you could call it one) is because it only provides rules to build a package, but not the package itself. Some derivations (e.g. for Gog games) even require you to add some non-redistributable files to the Nix store manually. The derivations may or may not build correctly for each platform they’re supposed to work on.
The reason the binary cache is not a repository is because it’s just a cache for nixpkgs - it stores every derivation’s output (if the build doesn’t fail), even if that derivation is one that downloads a package’s source code (yes, that’s a derivation too), even if the derivation is from many years ago (which has historical value, as you can revert nixpkgs to an old version and still be able to download prebuilt versions of packages).
Together, they form something like a repository, but it’s still way too different. For example, unlike on Arch, I can stay on the same nixpkgs version for a long time without updating, which I really prefer because I have to build 3 kernels on each update, since I’m syncing the nixpkgs version of my 4 NixOS devices, only 1 of which doesn’t require a custom kernel config. Or I can always revert back to an older version of nixpkgs if a new one breaks something and it will still work. Or I can fork nixpkgs and change some stuff, and the stuff with changed inputs will have to be rebuilt locally, with stuff that didn’t change still available from the binary cache.
yes, if that AUR was in a centralized git repository, kept track of inter-package compatibility, and centrally cached prebuilt versions of the packages for every single update, and you could also easily modify any of the packages, and there was a way to autogenerate build scripts, and and and…
Snaps are centralised packaging, a’la Apple App Store or Google Play. Now if someone forked snapd, added third party repo and made It so you could select which repo is the main one, that’d be a start.
But as long as Canonical commits to a centralised form of distribution with no third party support I’m going to advise desktop users to stay away from Ubuntu.
They have the ability to arbitrarily push out Snap updates.
That’s right! Your production server is getting patched without your knowledge or consent. Thankfully they magnanimously decided to let admins delay it by a few weeks.
Linux is about control. I decide what my machine does. When it updates. What it updates. The feedback from Canonical regarding Snaps was so tone dead and condescending it made Steve Balmer look sane. It boiled down to, don’t worry your pretty little head off. We know what’s best.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.