The biggest drawback of not providing any SSDs even as a fallback is obviously… what if the app just doesn’t draw CSDs?

Wayland requires apps to be able to draw CSDs, so that’s just a broken app. SSDs are optional extension. So the app should either use X11 (and rely on Xwayland to provide the decorations), or implement Wayland properly.

In fact, I think you’d be better off writing a deep dive into what/how environment variables work at build time, and also invoking commands on the CLI.

But LD_PRELOAD doesn’t really have much to do with build time behavior (unless you’re talking about replacing parts of the compiler) - it allows you to force a shared library to be loaded with higher priority than anything else, so it overrides symbols from other libraries.

It is recognized and used by Linux’s dynamic linker, which is run-time, not build-time.

You don’t need any swap space for suspend to work

The download will simply fail if the version pacman wants to download isn’t available on the mirror. The version is part of the download URL.

Wayland does force clients to be able to cope with a compositor that doesn’t do SSD - CSD support is mandatory, SSD optional.

It’s a crappy clickbait title, I don’t see why it shouldn’t get downvoted

I guess how much people care also depends on whether they tend to use laptops in ways and places that are prone to causing damage to the ports. I’ve never damaged any port on any laptop I’ve ever owned, and it’s unlikely I ever will because I like to keep the cables organized and out of the way (so it would require conscious effort to tug on them), and when I want to pick my laptop up, I always quickly run my hand around its perimeter to make sure everything is disconnected.

I do not claim that this is the correct way to use a laptop or that others should do the same, it is a tool that should be used the way its user needs, I just want to point out that for some usecases, this is simply a non-issue in the same way a non-replaceable CPU is - nothing’s going to happen to it.

Also, my current laptop does have both a barrel jack (probably works, I’ve never used it) and a USB-C charging connector, so it’s not necessarily an either-or proposition.

deleted by creator

deleted by creator

Virtual memory isn’t swap, it is a mechanism that allows the operating system to give processes a view of memory that is almost completely decoupled from real physical memory and other processes. For example some programs require their code and data to be placed at exact memory locations in order to work - virtual memory allows you to run as many of these programs as you wish, because one process’s address 0x1000 has nothing to do with another one’s 0x1000, unless they set it up as shared memory (but even the same chunk of shared memory might be mapped to different addresses in the processes that share it).

Swapping is a cool trick that you can do with virtual memory, though. Basically you store a piece of memory somewhere outside the physical memory, and then make the address invalid in virtual memory. When the process tries to access it, it will crash. The OS will be notified of the crash, see that it was due to the process trying to access swapped out memory, load the chunk back from disk (maybe to a different physical location), update the virtual memory to correctly point to this chunk, and restart the crashed process from the instruction that caused the crash. So from the point of view of the process, nothing went wrong at all, except that one instruction took a very long time to execute.

Also, isn’t it harmful to SSDs?

Swapping doesn’t do enough writes to matter, unless your system is running really low on RAM.

xfwm is XFCE’s window manager, and it’s eating almost 30% of the total system memory, so that’s the prime suspect (I’m not exactly sure how much it interacts with other apps, so it’s possible something else is forcing xfwm to use all that memory, but that is IMHO unlikely).

An ugly “fix” is to log out and log back in (yes, not much better than just rebooting), or you could try to somehow restart xfwm - running xfvm --replace in terminal might work.

Edit: there’s an issue on the Manjaro forums that might be related: https://forum.manjaro.org/t/xfwm4-memory-leak-since-4-20/173910/7

That was my deleted comment, but then I realized the article specifies they are Rome CPUs (Zen 2), while the 4000 series of EPYCs is based on Zen 4

deleted by creator

I don’t think overheating would cause random corruptions (it should throttle down when overheating, and then shut down if the temperature gets too high even when throttled, but there should never be an incorrect result of any computation), and surely the RAM will run at the standard 2133 speed on default settings - OP says they reset the BIOS settings to default between CPU swaps.

A simple rm -rf says hello