Ephera

Excuse me, Windows is the cheap copy of KDE.

Clickbaity title and thumbnail.

Love to see someone being happy with their 'puter.

At $DAYJOB, we’re currently using this to cross-compile a C/C++ application: https://github.com/dockcross/dockcross

If you just want x86-64 with old glibc, you can use their “manylinux” image.

But yes, this does not solve C applications being a massive pain in the ass to distribute, so you may still want to ship it as an AppImage or container image or with static linking or whatever.

Interesting that the crest also grew much quicker on the obese chicken.

Depends on the distro.

On my personal laptop with openSUSE, I have plenty confidence doing all kinds of upgrades and sidegrades (between Leap and Tumbleweed).
The package manager detects conflicts and makes me decide what to do with them. I’ve never seen the software or distro dependency definitions removed up, it was always me making a wrong decision.
Well, and if I do make a wrong decision or anything else should go wrong during the upgrade, I can roll back to the BTRFS snapshot before.

On my work laptop, the best I can get is Kubuntu. Apt is much more fickle, since it doesn’t have as clear of a concept of what constitutes a conflict, but also what a correct system should look like.
The whole packages feel much more fickle, too, because they’ve got all these custom patches, so you really don’t want to accidentally mix different versions of packages, like might happen in an incomplete upgrade.
And of course, you get one chance at upgrading. If anything goes sideways, you better have your Live USB ready right away.

So, that’s why I would prefer to install fresh right away. Of course, my workplace doesn’t actually allow me to do that either. They really like to keep me on edge.

I don’t think, it really matters whether it fixes a bug. This is about how many code changes it makes and therefore how many new bugs, it potentially introduces.

This explicit sync thingamabob was definitely a bigger code change.

I do find it weird that Ubuntu terminates this exception, seemingly from one disagreement, but hard to say what went on behind the scenes beforehand. And as the other guy pointed out, I don’t think the impact of this decision is that big, so I’m not sure, it deserves infinite scrutiny…

You can kind of think of a desktop environment as everything that’s needed to turn a server OS (which has only a CLI interface) into a desktop OS.

So, it contains (or pulls in) all the stuff for displaying any graphics at all, but then also a panel/taskbar, audio support, icons, global keyboard shortcuts like Alt+Tab, a settings menu and some utility programs like a file manager, a text editor, a calculator etc…

Switching desktop environments is kind of like switching between Windows 7 and Windows 8.
You can still run the same programs, all the CLI stuff and OS internals work the same, but the UX for interacting with that is different. Admittedly, though, different desktop environments usually have more differences than there are between Windows 7 and 8.

As for KDE Plasma, it’s available on lots of distros, but to name a few:

• Kubuntu is just Ubuntu with KDE preinstalled.
• Nobara has a KDE version.
• Personally, I’m on openSUSE. It is a somewhat more niche distro, relatively different from Ubuntu and Fedora. They really make KDE shine, though (with lots of detail work).

Well, Pop!_OS uses COSMIC, which is a customized GNOME, and Linux Mint uses Cinnamon, which is kind of GNOME under the hood, too. (In technical terms, Cinnamon is a “fork” of GNOME.)

So, yeah, that doesn’t allow ruling out that you’re always running into the same bug.
You should still try what the others are suggesting, though, before you go reinstalling or installing a different desktop environment. You’re certainly not the first person to use GNOME et al with 3 monitors. This should work.

Can you list the distros that you tried?

Monitor handling will mostly depend on the desktop environment and X11/Wayland, but different distros will ship with different defaults for these.

Ubuntu and Nobara both come with the GNOME desktop environment, which uses Wayland by default.

If you’ve tried anything with e.g. KDE Plasma as the desktop environment, that would already tell us a bit more…

This is unfortunately stupidly difficult on most Linux desktops, because the EWMH standard doesn’t support it. You mostly find support for it in niche desktops, like various tiling WMs or the Enlightenment DE.

You might want to report these. In the last This Week in KDE, it says:

This week we put some of the final Plasma 6.0 bugs to rest, and continued working towards Plasma 6.1

I mean, theoretically, this could mean that they decided these issues are a WONTFIX, but I imagine, they rather just don’t know of them.

Filesystem snapshots won’t help, if the filesystem itself corrupts. But I’ve been using BTRFS for 6 years now and haven’t had a file system corruption, so mileage may obviously vary.

Should not matter, whether you use zypper (CLI) or YaST. They use the same backend code (ZYpp).

a quick search suggests that Mint, Ubuntu, and NixOS all use bash by default

With Debian-based distros, it’s actually a bit weirder. They use dash as the global default shell (i.e. for executing sh scripts).
dash has basically no code for interactive use, so it’s supposedly faster and more secure. It is POSIX-compliant, so the treatment of whitespace should be identical, but it doesn’t support any of the added features of bash.

If you open up a terminal emulator, they’ve got that set up to use bash by default, so dash is supposed to be invisible to the user, but well, spoilers, it’s not. If you switch to a TTY, for example, it launches there and makes the TTY look completely broken.

Yeah, for this reason, lots of full-fledged programming languages actually make you specify the arguments as a list of strings directly, so for example:

Command::new("cp")
    .args(["file 1", "file 2”])

Hmm, as in you only want your home-partition to be encrypted, nothing else? Because you can do filesystem encryption for the entire btrfs (including both root and home) and that works perfectly fine.

Not sure, if it uses LUKS for that, but there’s an option in the installer for encryption…

openSUSE used to have the /home folder (so, not a specific user subfolder) on a different partition as the default setup some years ago, with 40 GB for the root partition.

They changed it, because it meant people’s root partitions would sometimes fill up from the snapshots being stored there and that’s really annoying to recover from.
Not only can a full root partition irreparably damage your Linux system, it also meant that people would try to uninstall packages to free up space, which wouldn’t actually free up space, because those packages were still contained in differential snapshots.

To actually free up space, you have to either delete old snapshots (so that there’s less difference to your current install) or delete intermediate snapshots where you happened to install a load of packages, which you uninstalled afterwards.

Yeah, in a manual car with the clutch disengaged and a gear engaged (and obviously the gas pedal disengaged), it should brake a little bit on its own. Many people don’t even use their parking brake, unless they’re parking on a slope, because that braking effect is good enough.

But I don’t think, you’d even need this braking effect. You can apply a lot of force to that brake pedal, if needed. I was taught, that if I need to brake for an emergency, I should kick, with full-force, the brake pedal and the clutch.

Not entirely sure, why that’s advised, maybe to avoid having the engine stutter or shut off, but I assume you couldn’t raise the brake amplification much more than that anyways (especially not without the driver being lifted off their seat and losing control).

The amplification is more of a comfort feature, since it means you barely need to move your feet in every-day-traffic.

It should be said, though, that brakes and steering are still possible via plain mechanics in hopefully all cars. There’s usually electronics to amplify it, meaning your car brakes harder and steers more easily without you putting in full force, but if that fails, it should degrade gracefully.

Had that happen in my old car a few years ago, that the whole engine and everything just turned off while I was rolling downhill. It was a bit of a panic moment, when suddenly the brake pedal and steering wheel took a lot more force to move, but the instinct reaction to just put in that force worked.