Quite a capable machine for my uses.
Not supported in Windows 11. Maybe with some additional config? Can’t be bothered with something hat might turn out to be fragile and need more maintenance than I can be bothered with. That’s a young man’s gane.
Ok, I’m about due to give Linux another tickle anyways.
Hmm, which distro… can always give a few a spin.
Keep it simple, Pop!_OS.
Installed fast, no issues, runs fine, stable. Seems entirely usable.
Customisations? Nah, keep it simple.
I’ll set a black background though.
Nope.
win11 ltsc works perfectly on it. With a solid background :D
Based on: Arch. Init: systemd. https://cachyos.org
Based on: Debian. Init: Non-systemd. https://www.devuan.org
Based on: Arch. Init: systemd. https://garudalinux.org
Based on: Independent. Init: Non-systemd. https://www.gentoo.org
Based on: Red Hat Fedora. Init: systemd. https://nobaraproject.org
Switching to upstream (Ubuntu) with KDE would probably be more your speed.
Something that should be a default option, or a single-tap switch in settings, turned into a chore consisting of a period of agonising disbelief, doubt, denial, search, and eventually bitter acceptance.
The best thing to do is just take a file same as your screen resolution into your favorite image editor and fill it with actual true black. Save as png and send to phone.
As for "same image as your screen resolution": screenshot sounds like the exact fitting thing here. As a challenge, tried making screenshot black using stock Samsung "Gallery" and it seems that repeated Edit - Brightness: -100 - Save as copy, then open the copy and goto back to Edit can do the trick as well, after four or so copies. (Copies, because there is no way to re-apply same effect on the same photo, apparently.)
There's the peak GNOME experience.
At some point they decided 2x (3x?) scaling was enough for anyone and took away 4x, I didn't notice because I was already set at 4x and it continued working. Somewhat later they took away the backend, and then my system crashed with no error message immediately at login.
After much troubleshooting replaced a movie night, I inquired about the functionality being removed and was berated for using an undocumented/unsupported feature (because I was continuing to use it after the interface to set it had been removed, without my knowledge).
I'll never use gnome again if I can help it.
It also shows you the screen you set it for, and a boolean to set it for all screens at once.
I'm not trying to be mean here, I'm just fascinated by what people will consider to be a waste of time.
This, sometimes it's enough for things to just work as you expect so you can do your actual work. I don't really understand why so many people are unpaid part time evangelizers.
KDE used to be the "bloated" desktop way back when (I know, pretty silly and laughable now given the current state of things).
That cemented Gnome/Mate into a lot of major distros as the primary DME. Ubuntu being the most famous.
The QT licensing situation is also a bit of a bizarre quagmire. There are certainly people that don't like KDE for more ideological reasons.
Personally, none of this bothers me and it's what I use for my personal computer. KDE is just so close to exactly how I'm used to interacting with computers anyways growing up through the Win95 era. It is so close to the Windows experience you want to have.
Doubling down on short judge-y stacatto contributes to an aggressive "I don't need to tell you" vibe that would be sassy and fun, maybe, if in person. In writing online comments, it just means we need to get a 3rd comment from you before we get to anything I'm interested in (I don't particularly care what your one word description is, I don't know you)
To the exact contrary to what you assert, one of the prominent argument against Gnome that I've been seing times and times again in DE debates, is the "dogmatic" opposition to SSD from the Gnome project.
But what things in KDE do you consider 'bloat'?
That’s not my recollection. I believe that the non-free license you mention was the major factor, in addition to the fact that KDE was written in C++ at a time when the free software community still preferred to write software primarily in C.
GNOME was written using a free software toolkit, and it was written in C, and it was associated with the FSF.
Nowadays the major problem with KDE is that by the time it is stable a new QT major version gets released and along with that it essentially gets a major rewrite, which takes years to stabilize and once it does a new QT version is released, etc etc etc.
There are a lot of people that bitch about it, but that is only because it is the most popular one and they think that Linux desktop is a zero sum game. They don't use Gnome most of the time and arguments tend to be parroting somebody else and probably out of date for years or just kinda made up conspiracy theories about Redhat or something.
The whole thing is pretty confused. Gnome being popular doesn't make KDE not be popular.
However, I've noticed, there's not much point in changing it. Showing the desktop is a waste of screen real estate because of the generations of abuse of desktop shortcuts. Even if you are careful, it becomes a cluttered wasteland (on Windows anyways). I just learned to never use the desktop for anything and always have windows up on various monitors.
The situation is better these days, with windows store apps. Still, I developed the habit of just never using the desktop in the XP days when things were really bad.
There was a war over your eyeballs, which had shady software vendors warring over desktop space, start menu space, taskbar space, even fucking file associations. I recall for a little RealPlayer and Windows Media Player used to yank back and forth file associations each time they ran, even if you tried to make them stop.
They've also disabled auto-save if you don't have the documents backed up by OneDrive, which is the most egregious for me.
https://thetechmentors.com/f12-a-better-alternative-to-the-s...
# Disable icons on Desktop
defaults write com.apple.finder CreateDesktop false
I suspect this is related to the System Preferences rebuild, since it's worked fine for 20+ years of OS X before that.
Just offer a background picker, and have it generate a 1x1 PNG, for the color selected. Just like that, you can use the image background code path for everything; and the code for generating the image almost certainly exists in the OS already. Maybe add some metadata to the generated image to filter it from the images picker, and you're done.
https://discussions.apple.com/thread/256028948?answerId=2613...
I also ran into it with 15.4.0 and worked around it by creating an image that's the solid color I like to use. It turns out that the system-supplied solid color options are themselves just 128x128 pixel PNG images too:
https://discussions.apple.com/thread/256028948?answerId=2613...
A non-textured triangle will be faster than a textured one as it can just return a literal in the pixel shader instead of wasting time sampling a texture for each pixel.
However a single texture sample is so cheap on modern hardware that a specialized path for solid colors wouldn't be worth the complexity in a 2D setting. It's fast enough.
Some additional examples beyond the OP:
- In the latest macOS, trying to set a custom solid color background just gives you a blinding white screen (see: https://discussions.apple.com/thread/256029958?sortBy=rank).
- GNOME removed all UI controls for setting solid color backgrounds, but still technically supports it if you manually set a bunch of config keys — which seem to randomly change between versions (see: https://www.tc3.dev/posts/2021-09-04-gnome-3-solid-color-bac...).
The pattern here seems pretty clear: a half-baked feature kept alive for niche users, rather than either properly supporting or cleanly deprecating it. Personally, I’d love to simply set an RGB value without needing to generate a custom image. But given the state of things, I’d rather have one solid, well-maintained wallpaper system than flaky background color logic that’s barely hanging on.