You and everyone else, unless you can gather more information on what is actually going wrong. Hence the suggestion to check logs and system responsiveness outside the GUI by dropping to a console or connecting over SSH when this happens.

Nah, it's a cakewalk these days. You should try LFS.
Installing Gentoo just requires a bunch of patience and an ability to follow instructions... As well as a free afternoon and about 3 gallons of coffee.
Being comfortable doing everything from the CLI (including a web-browser/reading the wiki) sure helps though, I suspect the "GUI is optional and comes last" bit is what puts people off.

I've been suspicious of the goings on at many of the big "open source" organisations for a long time, but the full-scale red-alert sounded right about when Microsoft, of all organisations, started shovelling money at open source developers and claiming to "love Linux"... Leopards and spots and all that jazz.

Then there's the whole "open source inclusiveness" movement (not to mention the RMS controversy, which we're not allowed to discuss here for some reason), which looks lovely on the surface, but fair reeks of corporate image/social media manipulation and employee codes of conduct... *politics detected: aborting*

As for Google and Firefox, yeah. That one is a pretty bitter pill, since gecko is really the only remaining independent (i.e. not  chrome/blink/webengine) browser engine in the game right now.
I'll still support Mozilla, since Mozilla was so very good to us way back when Microsoft sunk nutscrape Netscape Navigator, and that was the only GUI browser on GNU/Linux. I miss pre-google KHTML/webkit too TBH.

Google will fund any browser that punts traffic their way of course, and Firefox is no exception, but it's concerning when that's near-enough the only thing keeping a project alive. Doubly so when Google is also the main competitor in the browser space.

All is by no means lost, and there will always be old-school distros of some kind... There's also the BSD escape-pod, that's still largely uncorrupted.
IMO the days of "it's FOSS, so it's all good, it's all run by volunteer hackers and you can chat with them on the mailinglist" are pretty much over though. One might just want to be a little more careful what software one uses and who one donates to.

A shame that, Void is (or at least was, I haven't used it for many years) pretty dang cool and we need independent distros now more than ever. I don't have the time or the skill to stick my oar in in any meaningful way, but here's hoping people from the Void community will step up.

Aren't we all?

I'm here because Gentoo is too maintenance-intensive to run on a server (like all rolling release distros), Debian has fallen to system-everything, and pretty much all the small distros are too niche to package the software I want.
When it comes to large repo + init system plumbing freedom + low maintenance + stable releases, Devuan is kinda the only game in town IMO.

Back in 2000 I had rather more free time than I do now. I was also recovering from a very traumatic experience with RPM dependency hell and exploring a custom package management solution for LFS. Sadly that one was lost to the sands of time along with the hardware.

I doubt it. The truth will reveal itself soon enough, but it sure looks like a container system to me.

Apparently not. At least not where corporate agendas are concerned, and shit always flows downhill.

By which we mean embedded systems integrators, which along with IBM, Microsoft, and the US military, is where the bulk of Redhat's funding is coming from at the moment.

I was doing this sort of thing back in ~2000, when you could fit an entire GNU/Linux OS on a 1.44MB floppy disk. It's doesn't need to be complicated, it doesn't need containers, and it sure doesn't need systemd.
Of course you could do it with systemd + containers + whatever other bloated over-engineered garbage the shareholders are into at any given moment, but then you end up with something that's non-POSIX, non-portable, not even remotely Unix-like, and can't be reasoned about by a human sysadmin without 10 layers of abstraction and 30 management utilities... Not real surprising that's the approach the systemd devs are pushing, is it?

Then again. it could be a prank. If it is, it's a good one, because this is exactly the kind of "feature" I expect from the developers involved.

An excellent call. Noctua make the best air coolers available, both in terms of performance and quality. Their maglev fans are also all-around excellent, and IME will outlast pretty much anything else.
As an added bonus, the Noctua Industrial PPC series is one of the few aftermarket fan options that works properly with the BMC on Supermicro server boards while still being (relatively) quiet.

Yes yes, perhaps I should have said "let the automation pull packages from Debian without checking them for functionality on Devuan." The result is the same.

Anyone who has a passing familiarity with sed can make unattended-upgrades work. Perhaps somebody should teach amprolla the same trick.
Likewise anyone who can search a bugtracker can realise that pulling down such packages from Debian without any squishy eyeballs on them is going to reintroduce bugs just like this one.

Frankly I suspect what the community would appreciate even more would be a little look into where that fix committed 4 years ago wandered off to in the first place.

On a completely off-topic note, you're extremely unlikely to see me in the "Freedom Hacks" sub, ever. The pretentious name alone is enough to keep me away.

Indeed. Because:

It seemed that's what was being asked.

If you like:
Kwin/KDE
Dolphin
Firefox
Kmail
Kontact
KeepassXC
Filezilla
Jdownloader
Transmission-remote
Pidgin
KRDC
Libreoffice / Okular / FBreader
Gwenview & DigiKam
GIMP
Smplayer
Cantata & MPD
Easytag & Flacon
Kate
GCC, make, etc. scripted from Kate.
QCAD (I need .dwg compatibility that works)
Pre-Autodesk Eagle (I need the component libraries)
VirtualBox
Kcalc
Labplot
Lutris, WINE, DXVK etc. etc.

Konsole, bash, and all the CLI stuff therein.
All the other things I have forgotten but would miss immediately if I were to remove them

I don't have equivalent hardware so I can't check (exact names will differ), but my approach would be either:
a) If hwmon1 and hwmon2 are handled by different drivers, go see how and when they are loaded. They'll be getting an index based on which module loads first, so if you can fix the load order they should always get the same name.
b) See if there's another usable source, such as conky's {acpitemp} object or a node in e.g. /sys/class/thermal.
c) Get the values externally. IIRC conky can call external binaries, so you should be able to use lm-sensors with something like:

${execi 10 sensors | grep "Package id 0" | cut -d'+' -f2 | cut -c1-7}

"Package id 0" is from the intel coretemp driver so your sensor name will probably differ, but it should still be easily grepable.

It shouldn't be difficult to search through the /sys/class/hwmon[x]/name files for the sensor you want in a bash script either, push comes to shove.

The record industry (not to be confused with actual artists) was and still is convinced that consumers should rent access rather than own content.

Apple took things a step further, and sold a device that was essentially useless without subscribing to the content service... A content service where it looks like you've bought something, but actually using it is encumbered with DRM and tied to a subscription tightly controlled by the manufacturer. Then they doubled down and said you're not even supposed to be able to replace the battery.

You don't really own anything on iTunes, and even if you import your own DRM-free audio files it will mangle them to prevent you copying them again.
The open-source community quickly broke these restrictions and allowed us to transfer audio files freely with open-source tools, but the anti-circumvention clauses in the DMCA mean releasing software like GTKpod today would be illegal.

This "you own nothing" attitude is becoming more and more pervasive, throughout multiple industries. Be it streaming services, unrepairable hardware, cars that report to the dealership, or walled-garden app stores, the intent is the same - corporations retaining control over products long after they have left the shelf, and milking customers long after they have left the store.
All under the banner of "Don't think, just buy. Leave everything to us. For just 4.99 (plus recurring payments) you can have all the shiny things you ever wanted... Until we decide to take it away."

Calm, fitter, healthier and more productive
A pig in a cage on antibiotics

The way I see it, we have three options here:

* Keep breaking the DRM and reverse-engineering the hardware, playing cat-and-mouse with manufacturers and risking litigation under the demented monstrosity that is US copyright law.

* Pursue legal means through right-to-repair and such - if the hardware is liberated, liberating (or replacing) the software becomes considerably easier. Freedom to repair also means less waste to landfill, less profit for big corporations and more support for small locally-run businesses. As a bonus, it would also make it easier to hack on your own gear.

*Refuse to buy such products in the first place, and support open initiatives instead. Use jitsi instead of zoom, buy from System76 or Raptor CS instead of Apple. Ditch Spotify and iTunes and get your music from Bandcamp. If some shiny-new-(i)thing doesn't allow you to be in control, don't buy it.

Disclaimer: I am a unashamed software freedom advocate, and an FSF member. I'm not a hippie, and I don't eat my toenails in public... But I sure do like my freedom, and I'll donate to the FSF long before I give a cent to apple or the RIAA.

Back on topic: If you (OP) want to spend your free time circumventing the anti-freedom measures apple has surely put into it's new laptops, nobody here will try to stop you.
Asking others to do so is asking them to spend time and effort indirectly supporting a company that is diametrically opposed to everything free-software stands for, and doing so might even be illegal in some jurisdictions. Personally I feel efforts would be better spent elsewhere.

TBH I expect they're the same people who care more about what colour their car is or how expensive it looks than they do about reliability or performance.
In the good old days we'd call it "more money than sense" and leave it at that.

What I don't get is why anyone with the motivation and good taste to install a relatively obscure GNU/Linux distro (and one aimed at veteran sysadmins to boot) would want to wear the hair-shirt of running it on the latest shiny-new-shit MacBook, Apple and homebrew hacking of any kind parted ways decades ago and they've been intentionally making life difficult for us for almost as long.

Anyone with a lick of sense should already know that nothing computer-related in a movie bears the slightest resemblance to reality, so I'm not sure it'd make much difference.

Personally I take some glee in being the only one with a large GNU-head on my laptop lid in a room full of fruit, almost as much as I do at having superior performance and battery life, as well as the dents to prove my machine doesn't disintegrate when breathed on.
Then again I'm kinda nonconformist by nature, so, vOv.

I can understand the appeal of getting away from x86 (TBF I don't mind it at all, I still work with the venerable 8086 regularly), but Apple isn't the only game in town, and more arm-based projects are appearing all the time.
I can't help thinking effort would be better spent supporting (and buying) systems that are designed with GNU/Linux and software-freedom in mind.

Presumably just some variation on rm -rf /* or an obfuscation of such then. IMO if you execute commands from some random post as root without understanding what they do, you deserve what you get.
If I instructed you to set your PC on fire, you'd rightly ignore that as well, would you not?

Themes are pretty much always installable without root privileges (and so cannot wipe the whole drive and can be tested with a throwaway account), rarely have any call at all to be packaged as a .deb, and are usually either human-readable to begin with or come with source code you can inspect.
Most theme engines have an explicitly non-executable format anyway, so if something is packaged as a .deb or an installer script, you'd be wise to ask yourself why that is...

In general, the only "safe" source for any precompiled binary software is the distro maintained repository, and that's exactly as safe as the maintainers are vigilant. Any "user contributed" stuff is usually completely unchecked, because when it comes to FOSS in general it's anticipated that the user can and will inspect the source code.

That is indeed the better option, not only do you get a chance to see the source, you also ensure the resulting binary is linked against the correct libs.
Personally I'd consider a VM overkill (though useful for building packages for other distros), fakeroot and the debian packaging tools do a pretty good job of ensuring you only need root for the final installation, so you can do all building etc. as a dedicated unprivileged user.

All those people who hose their systems messing with sources.list or installing .debs from random places could have avoided that pain by spending the 10 minutes to learn how to rebuild a package from source, it's not difficult.