That’s amazing!
That’s amazing!
I get it, I actually use the exact same distros you mention: Pop!_OS, Endeavour and Fedora.
Had the same experience with Pop!_OS: those few things that did not “just work” but needed tinkering caused quite some issues. And yeah, somewhat more bleeding edge than Ubuntu LTS is nice: to use neovim on the 22.04 base, I’d need to use distrobox or build vim from source, but on Fedora and Arch, it “just works”.
I liked Endeavour, though I haven’t really used it with a DE, I went with Sway. So hard to compare, but the manual sysadmin intervention everyone keeps talking about has been minimal. AUR is amazing, pacman is fast and sane.
I went to Fedora because it is bleeding edge enough, but seems better tested and more stable than Arch. Also wanted to see how BTRFS is setup on there and test the rollbacks. The codec stuff has been terrible though. Even after enabling RPMFusion and installing a bunch of them, the Fedora source Firefox still refuses to do video calls in MS Teams. I’m using Flatpak browsers now but downloading flatpak updates is way slower than even the worst package manager for “native” binaries. Feels a bit odd to have to use a Flatpak for the browser.
If I had to install a new pc today, I’d go EndeavourOS with KDE (which I’m using on Fedora now), BTRFS and systemd-boot. I got to know systemd-boot in Pop!_OS and have tried a different boot manager (rEFInd), but systemd-boot is amazing.
Genuine question: what is it about Fedora that keeps you coming back? I have also used Debian based and Arch based distros, as well as Fedora.
Ubuntu does not require the model either. It’s an optional service that Canonical offers. They just market it in a weird way (inside the package manager)
I’ve been trying to explain that choosing to pay for this “extended security service” this is completely unnecessary if you just upgrade your OS every few years.
I think the average Mint user is not a wealthy enterprise with tons of systems they don’t want to upgrade so they don’t need to consider this, whether it’s available for their distro or not.
IIRC, Canonical is using Ubuntu to push an “extended security maintenance” program or something like that.
These kinds of services are all the same. RedHat does it, Microsoft does it, many others too probably.
The idea is: (stop reading if any of these don’t apply)
Wayland Nvidia compatibility will be here soon™ Nvidia drivers needed explicit sync, which was not supported in Wayland. However, explicit sync has been merged into the Wayland protocol and should be here shortly. Gnome 46.1 already ships with it.
I do not understand fully but maybe drivers need a bit of configuration too to use this? I’m not sure of all the steps but it should be here soon
Could be a (too) old version if you’re still on the Ubuntu 22.04 base
Yes but at least Hue (and IKEA and LIDL and many other brands’) lights work well with open Zigbee coordinators, like deconz and ZHA in Home Assistant.
I wish there were more Zigbee and Zwave and less WiFi IoT devices too. I don’t even have a Zwave coordinator because I never found anything I wanted with Zwave support.
My guess would be 3rd line from the bottom: a systemd service named gnome-terminal-server
is being started. Why is it being started?
Maybe it crashed and is set to always restart? Not sure.
I though Ctrl+Shift+T also worked to restore windows?
I agree that Konsole are Kitty are both lovely terminals that are very configurable. Kitty for text file people vim enthusiasts and Konsole for GUI lovers.
By “questionable update policy”, do you mean that it is updated by the package manager when installed from official repositories but it has an auto-updater functionality for users installing it manually?
IIRC someone who compiled from source but didn’t set the flag/config to disable the auto-updater was surprised about that.
I don’t see the big deal of it to be honest. The vast majority of users will be installing through the package manager. If you compile from source, you can decide yourself whether you want it to auto-update. The whole point of compiling from source is the extra control, not the defaults, I’d guess. Unless you don’t know what you are doing and the package was not available for your distro and in that case, enabling auto-update by default even serves that user group.
Nice! I missed that.
So Lemmy communities have a third form:
That’s a Mastodon thread. This is Lemmy.
While Mastodon users can subscribe to Lemmy communities (such as this one: !linux@lemmy.ml or lemmy.ml/c/linux ) and see Lemmy posts in their feed, Lemmy users cannot normally comment on Mastodon threads.
I know what they mean, but: I run an immutable Linux distro on my phone that is maintained by Google. I’m sure more than 0.01% of Europe does the same.
I guess “FLOSS phone” doesn’t have the same ring to it as “Linux phone”
Ubuntu 18.04 is end-of-life since Spring 2023. VS Code is going to require a newer version of glibc than Ubuntu 18.04 comes with. One does not simply upgrade glibc.
This new requirement was announced 6 months in advance, but no one reads the changelog, and enough companies still use Ubuntu 18.04 (hopefully while paying for the Extended Security Maintenance), so many people were surprised and unhappy when their VS Code stopped working for remote development over ssh on Ubuntu 18.04 servers. VS Code installs and runs stuff such as language servers on the remote machine.
This is pretty sick. Not just flatpaks but easily install any application, using apt or dnf package managers, or deb or rpm files, in a container with a simple syntax. Wow. Wrap a GUI around it and this may be a winning formula for an easy and stable Linux desktop.
FYI: Pop!_OS 22.04 uses systemd-boot, not GRUB.
I use rEFInd, which auto-detects my Windows boot partition. Though I had the Windows installation before the Linux one.
Systemd-boot should be able to detect a bootable Windows too. Those 3 boot options you saw once was systemd. Try to set that up as preferred boot manager in your BIOS/UEFI and you’re set.
deleted by creator