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
I didn't know Slackware had an ARM version all the way back then. Such a cool distro, it's one that I will always respect a lot even if I don't see myself daily driving it. It seems like the stable releases has gone down from twice or once a year to maybe once every 5 years or so.
I didn't know that either, I'm glad Slackware is still going. It was literally my first distro back in high school. I even remember getting a winmodem working in it and getting PPP connected. Recently Adrian's Digital Basement did a video on restoring one of the very first ARM desktops ever made. It's pretty interesting. Wonder if it would be possible to get an older 32-bit ARM Linux kernel booting on it.


You made a fatal mistake in thinking a Discord server would be the best way to get support. They are all full of the most smug, entitled pieces of shit that make you want to die after talking to them once.
You're better off on using stuff that has an IRC channel. People there can still be assholes, but if you explain your problems well you'll usually get pointed in the right direction (although it might take an hour or two to get a response).

This is such a weird thing to ponder, but the Arch "community" as it is now feels starkly different to the way it was 12-13 years ago. When I was in high school using Arch for the first time, all the Arch dudes on the forums, the subreddit, even the IRC channels I ran for help in, they were all in their 40s and 50s. Arch's 10th birthday in 2012 had a ton of overly sentimental comments about first installing Arch Linux off floppies across Reddit and YouTube.
I think the Arch and Gentoo communities were both like that back in the 2000s. I don't really participate in the communities, other than a occasionally getting on IRC, filing bugs or a small handful of forum posts.
 
I think the Arch and Gentoo communities were both like that back in the 2000s. I don't really participate in the communities, other than a occasionally getting on IRC, filing bugs or a small handful of forum posts.
More technical discussion places still have this feel; I've had a great time with people on the Devuan, Guix and Trisquel IRC chats at the very least. The System Crafters forum, which has become the de-facto main Guix System distro forum, is also pretty high quality, as is the Qubes forum. Privacy schizos tend not to like tranny cruft.
 
Linux gamers on Steam finally cross over the 3% mark
Linux users be like "we gotta save the Winorities"
winorities.png
 
Not to shit up further Lunduke slop videos in here but is there an ongoing trend of every major Distro to force Rust down their users throat? (Debian as of late)
Debian has so far been the first to fall, but the Linux kernel has included mandatory rust code for a minute now, and I remember that caused a stir back when it got implemented. This feels like the second coming of systemd.
 
You're better off on using stuff that has an IRC channel. People there can still be assholes, but if you explain your problems well you'll usually get pointed in the right direction (although it might take an hour or two to get a response).
Yeah as long as you try to demonstrate some critical thinking ability and you've tried to fix it yourself most people on IRC are helpful.

Everyone's sorta burnt out on Pajeets asking the dumbest questions.
 
Debian has so far been the first to fall, but the Linux kernel has included mandatory rust code for a minute now, and I remember that caused a stir back when it got implemented. This feels like the second coming of systemd.
There's also been mandatory rust in Python's Cryptography library which is probably used by half the Python scripts that interact with the Internet(web, etc) since 2021 it looks like.
 
Debian has so far been the first to fall, but the Linux kernel has included mandatory rust code for a minute now, and I remember that caused a stir back when it got implemented. This feels like the second coming of systemd.
I don't remember exactly when Python became a part of the base of most distros (for Gentoo it was forever since Portage has been written in Python for as long as I can remember), but no one screamed about that because, despite some of its shortcomings, it was small (python2-mini fit onto 8MB OpenWRT devices) and far better a system scripting language than Perl or Bash.

Python was a good change for most distros. Systemd and Wayland have been horrible. I use to be okay with Rust, but now that I see how far its gone and how bloated and shitty most Rust programs are, I can say I was totally wrong about it.
 
I don't remember exactly when Python became a part of the base of most distros (for Gentoo it was forever since Portage has been written in Python for as long as I can remember), but no one screamed about that because, despite some of its shortcomings, it was small (python2-mini fit onto 8MB OpenWRT devices) and far better a system scripting language than Perl or Bash.

Python was a good change for most distros. Systemd and Wayland have been horrible. I use to be okay with Rust, but now that I see how far its gone and how bloated and shitty most Rust programs are, I can say I was totally wrong about it.
Im still ok with rust. What I am not ok with is the adoption of it at a state where it's adoption still doesn't make sense, for integral pieces of the system.

I use programs written in rust every day. And some of them I like a lot. Ripgrep and fd in a lot of cases are genuinely faster, and simpler to use than grep, and find. There has been a few times where I've used both back to back to compare, and it's not even close how much faster fd and rg are. Other situations like piping some output to grep to search, are basically identical so I use normal grep for that. Same for find, there are places where it makes more sense to use normal find.

My point is, some of these programs are actually pretty nice. But there is a key distinction. They aren't core packages the system needs to function. Them existing isn't breaking support for who knows how many machines.

I see in most of these cases the adoption of rust as a downgrade. If these people were thinking clearly they would value not relying on more dependencies. Not breaking userland, and keeping the program as simple as possible, while doing the job they wanted to do. And if they are fine putting in all the work needed to convert these programs. Why couldn't they just put in that same effort into making sure they wrote safe C?
 
Last edited by a moderator:
Not to shit up further Lunduke slop videos in here but is there an ongoing trend of every major Distro to force Rust down their users throat? (Debian as of late)
1762218330936.png
"I plan to introduce hard Rust dependencies and Rust code into APT, no earlier than May 2026. This extends at first to the Rust compiler and standard library, and the Sequoia ecosystem.

In particular, our code to parse .deb, .ar, .tar, and the HTTP signature verification code would strongly benefit from memory safe languages and a stronger approach to unit testing."
(src)

Debian is the only one as far as I can tell. - This has put some ports in jeopardy:
1762218421105.png
 
Saars I am requesting you to help with my login screen. I distro hopped to CachyOS because vanilla Arch was giving me issues. I've solved just about everything else but for some reason I cannot get my theme to apply to the login screen. It's just a black screen with a basic white box for my name and password. It works but it's not pretty, and ChatGPT seems to have no idea what to do other than the basics, making sure I'm clicking the right buttons. I'm running KDE Plasma so all I want is the breeze theme to apply to the login screen and I cannot figure out why it doesn't work. I'm ready to start burning incense, and reciting prayers to the machine spirit. I checked /etc/sddm.conf.d/kde_settings.conf to confirm the theme is set to breeze, is there some other config I can check to force it through?
 
I cannot get my theme to apply to the login screen
Your "login screen" is technically a different program called a display manager. It sounds like your display manager is broken. Cachy uses SDDM by default which should be more themed than you're describing. https://wiki.archlinux.org/title/SDDM this article should explain how to customize/fix it.
 
Saars I am requesting you to help with my login screen. I distro hopped to CachyOS because vanilla Arch was giving me issues. I've solved just about everything else but for some reason I cannot get my theme to apply to the login screen. It's just a black screen with a basic white box for my name and password. It works but it's not pretty, and ChatGPT seems to have no idea what to do other than the basics, making sure I'm clicking the right buttons. I'm running KDE Plasma so all I want is the breeze theme to apply to the login screen and I cannot figure out why it doesn't work. I'm ready to start burning incense, and reciting prayers to the machine spirit. I checked /etc/sddm.conf.d/kde_settings.conf to confirm the theme is set to breeze, is there some other config I can check to force it through?
KDE Plasma pushed out a minor update a few days ago, so naturally a bunch of shit doesn't fucking work.
 
Saars I am requesting you to help with my login screen. I distro hopped to CachyOS because vanilla Arch was giving me issues. I've solved just about everything else but for some reason I cannot get my theme to apply to the login screen. It's just a black screen with a basic white box for my name and password. It works but it's not pretty, and ChatGPT seems to have no idea what to do other than the basics, making sure I'm clicking the right buttons. I'm running KDE Plasma so all I want is the breeze theme to apply to the login screen and I cannot figure out why it doesn't work. I'm ready to start burning incense, and reciting prayers to the machine spirit. I checked /etc/sddm.conf.d/kde_settings.conf to confirm the theme is set to breeze, is there some other config I can check to force it through?
https://wiki.archlinux.org/title/SDDM#Testing_(previewing)_a_theme Does this work at least?
sddm-greeter-qt6 --test-mode --theme /usr/share/sddm/themes/breeze
 
Against my better judgement, I decided to purge my perfectly functional, quite lovely, and altogether comfortable Artix installation on my external hard disk in favour of giving Fedora 43 a shot since it just recently released. I'm also deciding to roll with Wayland instead of immediately switching over to the much more comfortable, far less finicky X11. Here's a rather tedious process I went through, just to see how far I could go. I opted against Bazzite or Nobara because I stand by what I said previously: why go with a rebuild of Fedora when I can just put my money where my mouth is and install mainline Fedora instead? There's just one specific thing that pissed me the hell off that I'd like to rant about.

Wayland gave me this error on Fedora 42, still shows up on Fedora 43. Both times, I've opted for the KDE Plasma image: "[abrt] maliit-keyboard: _mm_loadu_si128(long long __vector(2) const*)(): maliit-keyboard killed by SIGSEGV." I had the option to report the bug, I think sure, why not? I go through the motions, and as fate would have it, I'd need to either create a Red Hat Bugzilla account or log in through a Fedora account. Whatever, I create the alias for Fedora online, try to link the two together, Red Hat Bugzilla shits itself and says "oi m8, u need a fookin Red Hat Bugzilla account anyway," I grit my teeth and make it. Pop in my fucking API key, and oh no! You know what happened? the goddamn bug report failed because there was already a duplicate I wasn't aware of. 2373885 made all the way back in fucking June in the year of our Lord 2025. Most recently updated as of 28OCT2025. So apparently, Red Hat knows about this goddamn bug but apparently absolutely fucking nothing is being done about it despite some douchebag named Jan Grulich being assigned the ticket?! What the shit? Literal fucking IT jeets at my goddamn job are more efficient at resolving IT support tickets than Red Hat is from my point of view.

At any rate, here's the obligatory fastfetch screenshot. I already went through the song and dance of updating Fedora, setting up everything via RPM Fusion, and installing Steam.

1762272314109.png

KDE Plasma pushed out a minor update a few days ago, so naturally a bunch of shit doesn't fucking work.

Brother, you don't know the half of it.
 
After extensive testing I think the issue I had was SDDM was not properly enabled and LightDM was. After consulting with both ChatGPT and Grok, and also bricking my system a few times I went the nuclear option and reinstalled the distro. Could I have fixed it? Maybe. This was faster and easier for me. Thanks for the help though.
 
Back
Top Bottom