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
Windows is much more bloated than Linux (people like to point to the hundreds of millions of lines of code in Linux but most those are device drivers that rarely get updated) and most Linux updates don't require a system restart.
The funniest part of Windows bloat is how much code is in there just to prevent other code that is in there from breaking things.

Legacy code is a nasty, nasty mess sometimes.
 
Not on Gentoo unless you had a very powerful computer
False. Most slow-building Gentoo packages have quick installing binary packages available. Gentoo excels at building updates exactly once per config. Gentoo's benefit is that you can have weirdly configured packages and the weird configuration gets updated (and tested, if you want) automagically. This makes source versus binary distribution comparisons apples versus oranges, but even so, Gentoo takes as much pain out of it as possible.
 
False. Most slow-building Gentoo packages have quick installing binary packages available. Gentoo excels at building updates exactly once per config. Gentoo's benefit is that you can have weirdly configured packages and the weird configuration gets updated (and tested, if you want) automagically. This makes source versus binary distribution comparisons apples versus oranges, but even so, Gentoo takes as much pain out of it as possible.
But Gentoo users don't want OtHeR pEoPlE's BiNaRiEs!



Someone should fork Linux From Scratch and call it Non-Binary OS, just to piss off all the Linux troons.
 
Last edited:
Wooooo, just gave Proton a go for the first time and it runs what I want with no apparent hitch! This feels like night and day in terms of convenience compared to when I first tried Linux all those years ago (2017 or so).
 
If you aren't a free software extremist you should not be using guix. If you are, I'm not sure why these problems bother you.
Extremism is good.
ED: Poettring has been caught conspiring to allow malware to target and then hijack process dumps of suid binaries, with the purpose of enabling the CIA & Mossad to dump passwords and private keys stored in the memory of system daemons that provide critical services (i.e. anything that actually should be running on your system and doesn't have 'systemd' in the name).
 
Last edited:
I did a retarded, subtarded even, move of distro hopping back to Endeavor OS for a few months and I have had nothing but pain thanks to a perceived problem that didn't exist. I have also missed the simplicity of using the Slackware 15's "slackpkg clean-system" command to remove packages with ease.
Screenshot_2025-06-21_02-20-04.webp
 
What the fuck is going on with these HEADER issues with KDE/Qt? I have been tracking this one down for a day, but it pops up every time you mouse over Firefox on YouTube on the plasmashell/panel specifically. Should be reproducible on Arch with Plasma (updated 3 days ago).
1750471033464.webp
Qt 6 now enables HTTP/2 by default, so Plasma’s requests to Google’s servers all attempt to use HTTP/2. It then fails due to Qt’s HTTP/2 client and Google’s HTTP/2 server disagreeing on the protocol exchange. AFAIK Qt’s HTTP/2 handler (qhttp2protocolhandler.cpp) throws a connectionError(PROTOCOL_ERROR, "HEADERS on invalid stream") as soon as Google sends the frame back, Qt’s QHttp2ProtocolHandler::handleHEADERS() rejects the response headers on the grounds that Qt has already decided the stream is closed for some reason. Sometimes it still gets an image either by caching it from something or a fallback to HTTP/1. Maybe it times out and then falls back too quickly leading to conflicts when the frame is sent back? IDK. All ik is when plasmashell gets an empty QPixmap you see a blank or fallback tooltip plus log spam from qt.network.http2.connection. At least that's what I think is happening from the cryptic ass strace. I found a recent bug report that included this same protocol error elsewhere recently.

maybe I am wrong though. it's also not a super bad bug, the fallback works most of the time and nothing is crashing. Thats my guess as to why nobody is really talking about this very easily reproducible issue, but its annoying when u have a system set up to actually notify you when journalctl tells you of CRITICAL prio stuff.
 
I have also missed the simplicity of using the Slackware 15's "slackpkg clean-system" command to remove packages with ease.
Slackware is amazing, I really love using it. Always put it on computers I never want to touch because its the most stable distro I have ever used, by far.
Also a good just works distro if KDE or Xfce is your thing, which are two sane desktops included out of the box, with their main programs bundled in too.
I never found no automatic dependency resolution to be a problem either, because of how much stuff is included by default.
If you care about bloat so much that a few extra desktop icons hurts you, I think you have bigger problems to deal with.
Slackware current has mpv too. so a lot of Python stuff will be easier to deal with when the next version comes out (one day...)
Gentoo is nice but there's also something comfy about Slackware. I do miss it, my main hardware is too new for 15 and I had trouble with Current last time I tried, but maybe its time to give it another try.
 
The primary difference is that in the end Linux Mint isn't really its own distribution, it's built off stable releases of other distributions. If you're using a full distribution like Devuan, there should be testing and unstable branches that let you use the latest software, like Arch, but more coherently.

Kinda sorta. Mint does do some in house development including Timeshift, Cinnamon, and Nemo that is of course shared with the linux community. But not on the level that Canonical, Red Hat or Debian do. A lot of the real hard core development is on the kernel itself. Mint though doesn't pretend to be based on anything but Ubuntu (or Debian with LMDE).

Edit: Haven't tried slackware in a long long time since the days of WinNuke. I'll have to try it on a VM and have a round or two with it.
 
The primary difference is that in the end Linux Mint isn't really its own distribution, it's built off stable releases of other distributions. If you're using a full distribution like Devuan, there should be testing and unstable branches that let you use the latest software, like Arch, but more coherently.
In the strictest sense it's built off Ubuntu Server but with snaps removed. Everything graphical that the user actually sees is maintained or curated by the Linux Mint devs. Ubuntu server is solid if you remove snaps, it's the graphical stuff that has tranny bullshit and user hostile decisions
 
Snap implementation was bad by Ubuntu and snaps is why the iso image has blown up so much in size.. I don't think they are bad now and some of the pushback is more of a hatred of Canonical but the damage was done.. . Mint has flatpak enabled but none installed by default. Outside of the *buntu universe, I don't think any major distros/spins uses preinstalled snaps. I've dicked around with *buntu distros and removed snaps and didn't have major problems on VirtualBox afterwards, mostly having to install the Gnome software manager afterwards (though I prefer synaptic) and having to pull in a repository to install Firefox.

By the way, I went ahead and put slackware into a VirtualBox, but I had forgotten how to use basic tools like fdisk so had to Bing how to do it. I installed LXDE on it and honestly, it's not bad and boots rather well. Still got to play with it somewhat and get used to things being different outside of the GUI. Not going to use it though on real hardware as I am debian and it's children fan.
 
Also a good just works distro if KDE or Xfce is your thing, which are two sane desktops included out of the box, with their main programs bundled in too.
If Slackware packages Openbox, and I don’t see any reason why it wouldn’t, and if you are looking for stability and don’t mind using old code because "its old" then I would say that this should also be an option considered. Openbox is the most stable environment on Linux IMO. Makes sense considering it's probably the most UNIX-like by philosophy. It literally does one thing well by design. Display the desktop and the windows on top of it. That's it. It delegates everything else to other packages. There's no internal hell of 100 spinning wheels like these huge DEs have nowadays. Just pure "one thing well" simplicity. No wonder it's been over a decade without major work done on it and it still functions flawlessly. It's the most underrated *NIX environment, or at least it is with newer users.

There will be no version of Openbox for Wayland; that will finally mark the end of life for Openbox after decades of reliable service. For that we have labwc which seems promising, but it's still a bit fresh and the number of people working on it is disappointing. It's not even in the Arch repos yet so I assume it's probably rough or at least not compelling enough to drop Openbox for as long as Openbox works. Last time I tried it I wasn't too impressed but that was a while ago. I already like that they aren't fucking around with their own compositors or w/e. Just using wlroots. I need to get around to configuring it one of these days with Waybar now that PCmanFM reportedly works on Wayland with the `--desktop` flag which is something I personally need as I like having the file manager handle my .desktop launchers and background when using stacking WMs.
 
If Slackware packages Openbox, and I don’t see any reason why it wouldn’t, and if you are looking for stability and don’t mind using old code because "its old" then I would say that this should also be an option considered.
The DE/WMs included on a default install are;
KDE and Xfce for DE's,
Fluxbox, Blackbox, WindowMaker, FVWM2, TWM and MWM (Motif WM) for WMs.
1750489131469.webp
No Openbox by default, but you do get several choices for lightweight window managers. Openbox was originally a Blackbox fork, which is on brand for Slackware to still package ancient software (they still package the original XMMS and GTK1 after all).
Openbox is still installable via a Slackbuild if you want it (also has no dependencies so no trouble to install).
For that we have labwc which seems promising, but it's still a bit fresh and the number of people working on it is disappointing.
labwc is currently included in Slackware Current to get Xfce's Wayland session running, I found it worked decently for a basic session but it was buggy and several basic things were broken (e.g., scaling the desktop). Overall, pretty good considering its new, and it does look very promising to be a proper Openbox replacement in the future.
 
If you want Wayland, with Openbox, couldn't wayfire or weston serve as a decent replacement? Wayfire is the best non-DE I've ever used. The ,ini is simple enough, and it has great documentation and plugins.
 
Back
Top Bottom