The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
If anything I would expect Debian to be one of the last distros to remove X11 support, if ever.
Debian capitulated to systemd so fast it was staggering. Even recently, Rust has become a prerequisite for Debian all of a sudden, putting the future of several ports in danger. I don't have your faith in the Debian administration.
 
I haven't heard that distro in probably years, never liked it's update system thing and it ran kinda bad on my old pc.

Have you tried with other distros? My guess it's that KDE Plasma is not that well integrated in KDE Neon.
It's Ubuntu LTS with latest stable KDE, and maintained by the KDE team. I'd assume it is integrates well?
 
Fedora is really just as retard friendly as Ubuntu and Mint these days if you leave it alone IMO.

Yes but also no. It's like 45% Yes normie friendly, 45% No normies allowed, and like 5% "goes either way."

(+) Fedora ships the latest versions of GNOME, KDE, Xfce, Cinnamon, MATE, LXQt, and so on. Minimal patching so no distro-specific paradigms in the GUI.
(+) All versions of Fedora (official, Atomic, Spins, etc) ship with a modest, but adequate set of user goodies like LibreOffice, media players, and stuff like that. Fedora Spins even go a step further with stuff like Exaile, MPV, and YT-DLP shipping by default.
(+) Fedora does a fantastic job showcasing the FOSS ecosystem without unnecessarily kneecapping itself. All editions only ship FOSS programs, all the official repos are strictly FOSS, no binary drivers, but binary firmware in the kernel is the sole exception.

(+/-) Fedora's commitment to FOSS isn't necessarily a purely ideological commitment. Red Hat is a company created in and operating out of the USA. Software patents, export controls, civil liabilities, and stuff along those lines apply to them.
* All software in the repositories, even fonts, must be under FOSS licenses.
* Even then, some FOSS programs are too risky to ship by default.
* libdvdcss is a wholly FOSS library, but it's a tool that breaks content encryption.
* ffmpeg is deliberately gimped to avoid infringing on codec patents.
* You have gimped versions of Mesa that still function, but get rid of hardware codecs (i.e. VAAPI, VDPAU, etc).
* NVIDIA's binary drivers require the user to agree to NVIDIA's terms.
** Clement Lefebvre can get away with shipping everything OOTB because Mint only makes money through sponsorships and small dollar donations are the norm.
** Canonical can kinda sorta get away with it because Canonical's a British company. They still ship a mostly FOSS stack, but then you also have ubuntu-restricted-extras from official repositories to offset the gaps.
(+/-) Fedora Workstation allows you to enable RPM Fusion for Steam and the NVIDIA binary drivers, along with a COPR for PyCharm at the time of installation via the live USB medium. No other Fedora version does this.
(+/-) I don't know what it's called, but there's some type of Python thing that activates if a command ain't found but the binary can be downloaded. It happened to me on Fedora Workstation for yt-dlp. I know it's Python because it all installs to $HOME/.local and there are various .py scripts lying around. Convenient sure... but if it exists in the official repositories, I'd rather have that version.
(+/-) Fedora Flatpaks ship all the runtimes in a single binary. Problem is that Fedora Flatpak selection is sparse, can conflict with overlap from Flathub, and can even break due to poor QA (re: OBS)
(+/-) GUI tools vary wildly from one version to another, contingent on the desktop environment itself. GNOME has adequate tools, KDE has an overwhelming amount of GUI tools, XFCE is a bit sparse but workable, Cinnamon is more of the same, MATE has a bunch of obtuse menus but still plenty workable... but then you have LXQt, i3, Budgie, COSMIC, and so on... you tell me how good the GUI tools are for those.

(-) RPM Fusion is a hard necessity when using Fedora. Even if you skip the non-free repositories, RPM Fusion still has the full ffmpeg, full Mesa stacks with hardware codecs, and various FOSS tools that are too damn risky to ship by default.
(-) Not necessarily a problem; setup is relatively painless. Problem is that normies don't wanna copy/paste the most basic and clearly outlined commands just to get things up and running. I think the terminal hatred from Linux refugees is a touch overblown, acclimatisation to using the CLI is nowhere near as bad as people make it out to be, but normies don't wanna hear it.
(-) Fedora Atomic is not an adequate equivalent to SteamOS, and Bazzite is complete fucking garbage because of it. SteamOS does the "atomic" shtick better because you don't need to speedrun amateur distro maintainer any% whenever you need to rebase your system between version increases. rpm-ostree is only meant for system utilities, Flatpaks are what Fedora Atomic wants you to use, but so much shit just doesn't exist on Flatpak to where layering it in with rpm-ostree (often via RPM Fusion) is a necessity. But if you layer shit on with rpm-ostree, you need to speedrun amateur distro maintainer any% by hosting your own images, upgrading, and then rebasing.
 
I've been using Omarchy on my work machine for a bit, and I quite like DHH's "opinionated" settings, but brother, why do you have to fuck with the keybinds? If there was an option to retain keybinds somewhere in their custom "omarchy-update" command (which just updates all packages from all sources, so snap, flatpak, all repos etc.) I must have fucking missed it. Need to permanently migrate this it to Guix one of these days, stinky caca nonfree hardware notwithstanding.
 
Normal Computer user: OK guys turns out I need to get GCC 4.2. Oh there is no mipsel binary online? I guess Ill have to build it. im sure that will be easy.
I've also had to deal with that shit at work. I just asked the gentoo chad to do it. Anyways, I believe you could have avoided this problem by using zig cc, which allows you to cross compile to mips and also specify glibc version, without having to download or setup anything extra.
 
I've been using Omarchy on my work machine for a bit, and I quite like DHH's "opinionated" settings, but brother, why do you have to fuck with the keybinds? If there was an option to retain keybinds somewhere in their custom "omarchy-update" command (which just updates all packages from all sources, so snap, flatpak, all repos etc.) I must have fucking missed it. Need to permanently migrate this it to Guix one of these days, stinky caca nonfree hardware notwithstanding.

Wait... Omarchy has Snaps out of the box???

At this point just install your hyprslop on top of Ubuntu, damn.
 
Wait... Omarchy has Snaps out of the box???

At this point just install your hyprslop on top of Ubuntu, damn.
It doesn't install any snaps out of the box.. or at least I dont think so? I installed omarchy (to contribute to it) on this beauty that I start with a screwdriver:
IMG_20250616_212734.jpg
 
I've been using Omarchy on my work machine for a bit, and I quite like DHH's "opinionated" settings, but brother, why do you have to fuck with the keybinds? If there was an option to retain keybinds somewhere in their custom "omarchy-update" command (which just updates all packages from all sources, so snap, flatpak, all repos etc.) I must have fucking missed it. Need to permanently migrate this it to Guix one of these days, stinky caca nonfree hardware notwithstanding.
Imagine ever using someone else’s keybindings. Imagine ever letting some faggot who’s most famous for making a shitty framework for the worst web dev language decide what’s best for your desktop. Imagine letting that bald bastard fuck your computer raw while you sit in the cuck chair and call him based.

I use void btw
 
Wait... Omarchy has Snaps out of the box???

At this point just install your hyprslop on top of Ubuntu, damn.
Nah, only Flatpaks, just mentioned it off the top of my head because AFAIK it also updates them if you have them installed. Funny you should mention Ubuntu, cause DHH also made Omakub, which, you guessed it, is Omarchy on Ubuntu (except worse).

Oh no no no troon bros, not like this
 
I've been using Omarchy on my work machine for a bit, and I quite like DHH's "opinionated" settings, but brother, why do you have to fuck with the keybinds? If there was an option to retain keybinds somewhere in their custom "omarchy-update" command (which just updates all packages from all sources, so snap, flatpak, all repos etc.) I must have fucking missed it. Need to permanently migrate this it to Guix one of these days, stinky caca nonfree hardware notwithstanding.
I think you set custom keybinds in another file somewhere that doesn't get overwritten. If I used omarchy I would be able to give more advice. But i just use hyprland itself set up how I like it.

I imagine you can if nothing else make your own file, then in the normal keybinds file include that one and comment out the keybinds he has set. That would if nothing else make changing them back after an update super quick.

There is probably another way you are supposed to do it though.

Actually I want to say on the update thing.

I believe at least one or two of the aur helpers will update everything for you. Maybe paru. Idk I haven't had flatpaks on arch in a while. Even if they don't you can make a 2 line script that will do it.

Bash:
#!/bin/sh

paru
flatpak update

That will update all normal packages, all aur packages, then your flatpaks.
 
Still no real replacement for x11vnc. I tried krfb on plasma with wayland and it simply did not work. krdc just fails silently and tigervnc says the screen framebuffer is null size.

Someone tell me I'm doing something wrong. That I'm missing something. I don't know how Wayland apologists can keep insisting how it's "ready" despite lacking basic functionality after a million years.
Adding to this. KRFB started working at some point, but has issues with unattended, permissionless connections. There's an entire multi-year thread about it. I like the dev just shrugging and being like "yeah it'd be nice it someone fixed it": https://discuss.kde.org/t/krfb-on-wayland-have-to-confirm-remote-control-requested/2650/25

1765322064035.png

Also the Wayland backend "pw" is way slower and choppier than x11vnc, even when it works.
 
Adding to this. KRFB started working at some point, but has issues with unattended, permissionless connections. There's an entire multi-year thread about it. I like the dev just shrugging and being like "yeah it'd be nice it someone fixed it": https://discuss.kde.org/t/krfb-on-wayland-have-to-confirm-remote-control-requested/2650/25

View attachment 8268496

Also the Wayland backend "pw" is way slower and choppier than x11vnc, even when it works.
This exact shit bit me earlier this week. It's hilarious how often stuff like this shrugged off as "IDK who would need that" and there's a sea of people saying "umm me". Swapped back to x11 and all good.
 
Fuck passkeys these things are bullshit
"Um so like you cant use a password because its insecure"
"heres a plaintext password reset key."
1765324101701.png
1765324108452.png
1765324119048.png
"Um you lost your phone? Well guess your getting permanently locked out of your account"

LIKE FUCK PASSKEYS I HATE THEM SO MUCH.
 
void > arch
It’s just better
Until you need to run some proprietary software that isn't packaged by void.

Sometimes you can get around that easily, sometimes its not that simple. At least compared to using arch, it makes some things complicated.

Like if you want to run hyprland. The void people refused to package hyprland. There is a whole thing you can read, with the back and forths about it. But with the way the void team leans politically, you can tell that had an effect on their decision. They could have easily just pinned down hyprland to the dependencies it needs, and update it when those get updates.

So you need to enable a seperate repo for hyprland, or you need to add hyprland to your xbps-src packages and maintain it from there.

There are a lot of situations like that on void. There are a lot of things I like about void. I like runit, I like that its mostly a pretty solid system while being rolling release. I like that its pretty minimal out of the box. But when a lot of the things you want/need aren't packaged, or there are other complocations with the software. At a certain point just using arch becomes simpler. If you don't have any, or only a few packages like that then void is pretty great.

Fuck passkeys these things are bullshit
"Um so like you cant use a password because its insecure"
"heres a plaintext password reset key."
View attachment 8268623
View attachment 8268625
View attachment 8268626
"Um you lost your phone? Well guess your getting permanently locked out of your account"

LIKE FUCK PASSKEYS I HATE THEM SO MUCH.
Sorry for the double post.

Yeah, they are annoying. You basically need to set up a git helper to handle credentials if you want to use github. Which seems like a bad thing to not give people a choice about.

Anyway, definitely move the backup codes to an encrypted drive to back it up. Maybe multiple if you have a few extra usb's around. Its worth taking the time to do.

You don't necessarily have to encrypt the drive if you dont care that much but backing it up is worth the effort. Also I recommend using ecryptfs if you want to keep a the file on your computer. Just throw it in the Private directory so you have it there if you ever need it. Then just open up your private dir and grab a code.
 
Adding to this. KRFB started working at some point, but has issues with unattended, permissionless connections. There's an entire multi-year thread about it. I like the dev just shrugging and being like "yeah it'd be nice it someone fixed it": https://discuss.kde.org/t/krfb-on-wayland-have-to-confirm-remote-control-requested/2650/25

View attachment 8268496

Also the Wayland backend "pw" is way slower and choppier than x11vnc, even when it works.
Nvidia also brought up that permission issue recently in a talk:
 
Back
Top Bottom