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
That is very weird. I've installed Artix on like 3 different computers and every single one has gone flawlessly. I'd make a bug report if I were you.
Curious, what size drive are you installing it on and are you partitioning it yourself? I'm just trying to do the least amount of work possible and telling it to erase and use a whole 4TB drive.

I would probably recommend flameshot. It works on wayland, and x11. And most people that want a screenshot tool with a lot of features use that. On x11 its probably one of the most recommended screenshot tools I see.
I'll try it. Ksnip was just the first tool I found searching with pacman, and I only wanted the functionality to bind Meta+Shift+S to let me copy a rectangular region directly to clipboard, which it did. I think it works on Wayland now, last time I ended up on there that wasn't what gave it away to me.
 
I'll try it. Ksnip was just the first tool I found searching with pacman, and I only wanted the functionality to bind Meta+Shift+S to let me copy a rectangular region directly to clipboard, which it did. I think it works on Wayland now, last time I ended up on there that wasn't what gave it away to me.
In that case flameshot will definitely do that for you. I can't remember the exact command off the top of my head for it with flameshot. I think flameshot gui, but you can look it up and it should just work. Even if you aren't using Wayland it's a good tool. For Wayland specifically from what I remember you just need to make sure the xgd_current_desktop is set correctly.

If you are willing to use something more simple. The line I typed with grim does exactly that. If you want to save it to disk you can make some slight changes, and it will do that instead of sending it to the clipboard (or it can do both)

You can put that in a file make that executable, and put it on your path. Making it a script just ads some convenience. So you can just run that like it's own program, Like when you add it to your keybinds. Or you can just the script itself in the keybind if you don't want to ever use it any other way.
 
Apparently, x11 codebase is a plate of spaghetti and it’s difficult to maintain, and a total rewrite runs risk of breaking applications that rely heavily on its current behavior.

That’s all i got, idk why everyone is bent on switching over.
Code:
(computers)
%
X windows:
        Accept any substitute.
        If it's broke, don't fix it.
        If it ain't broke, fix it.
        Form follows malfunction.
        The Cutting Edge of Obsolescence.
        The trailing edge of software technology.
        Armageddon never looked so good.
        Japan's secret weapon.
        You'll envy the dead.
        Making the world safe for competing window systems.
        Let it get in YOUR way.
        The problem for your problem.
        If it starts working, we'll fix it.  Pronto.
        It could be worse, but it'll take time.
        Simplicity made complex.
        The greatest productivity aid since typhoid.
        Flakey and built to stay that way.

One thousand monkeys.  One thousand MicroVAXes.  One thousand years.
        X windows.
%
X windows:
        It's not how slow you make it.  It's how you make it slow.
        The windowing system preferred by masochists 3 to 1.
        Built to take on the world... and lose!
        Don't try it 'til you've knocked it.
        Power tools for Power Fools.
        Putting new limits on productivity.
        The closer you look, the cruftier we look.
        Design by counterexample.
        A new level of software disintegration.
        No hardware is safe.
        Do your time.
        Rationalization, not realization.
        Old-world software cruftsmanship at its finest.
        Gratuitous incompatibility.
        Your mother.
        THE user interference management system.
        You can't argue with failure.
        You haven't died 'til you've used it.

The environment of today... tomorrow!
        X windows.
%
X windows:
        Something you can be ashamed of.
        30% more entropy than the leading window system.
        The first fully modular software disaster.
        Rome was destroyed in a day.
        Warn your friends about it.
        Climbing to new depths.  Sinking to new heights.
        An accident that couldn't wait to happen.
        Don't wait for the movie.
        Never use it after a big meal.
        Need we say less?
        Plumbing the depths of human incompetence.
        It'll make your day.
        Don't get frustrated without it.
        Power tools for power losers.
        A software disaster of Biblical proportions.
        Never had it.  Never will.
        The software with no visible means of support.
        More than just a generation behind.

Hindenburg.  Titanic.  Edsel.
        X windows.
%
X windows:
        The ultimate bottleneck.
        Flawed beyond belief.
        The only thing you have to fear.
        Somewhere between chaos and insanity.
        On autopilot to oblivion.
        The joke that kills.
        A disgrace you can be proud of.
        A mistake carried out to perfection.
        Belongs more to the problem set than the solution set.
        To err is X windows.
        Ignorance is our most important resource.
        Complex nonsolutions to simple nonproblems.
        Built to fall apart.
        Nullifying centuries of progress.
        Falling to new depths of inefficiency.
        The last thing you need.
        The defacto substandard.

Elevating brain damage to an art form.
        X windows.
%
X windows:
        We will dump no core before its time.
        One good crash deserves another.
        A bad idea whose time has come.  And gone.
        We make excuses.
        It didn't even look good on paper.
        You laugh now, but you'll be laughing harder later!
        A new concept in abuser interfaces.
        How can something get so bad, so quickly?
        It could happen to you.
        The art of incompetence.
        You have nothing to lose but your lunch.
        When uselessness just isn't enough.
        More than a mere hindrance.  It's a whole new barrier!
        When you can't afford to be right.
        And you thought we couldn't make it worse.

If it works, it isn't X windows.
%
X windows:
        You'd better sit down.
        Don't laugh.  It could be YOUR thesis project.
        Why do it right when you can do it wrong?
        Live the nightmare.
        Our bugs run faster.
        When it absolutely, positively HAS to crash overnight.
        There ARE no rules.
        You'll wish we were kidding.
        Everything you never wanted in a window system.  And more.
        Dissatisfaction guaranteed.
        There's got to be a better way.
        The next best thing to keypunching.
        Leave the thrashing to us.
        We wrote the book on core dumps.
        Even your dog won't like it.
        More than enough rope.
        Garbage at your fingertips.

Incompatibility.  Shoddiness.  Uselessness.
        X windows.
%
 
Curious, what size drive are you installing it on and are you partitioning it yourself? I'm just trying to do the least amount of work possible and telling it to erase and use a whole 4TB drive.
Largest drive was a 2TB NVMe with the default partition scheme + disk encryption. Cleans up the drive and installs without a hitch, and I really can't see a bigger drive size alone being the issue. Very weird though, all 3 machines I've put Artix on (P70 & W541 ThinkPad, 320-ISK IdeaPad) have run it flawlessly both on SATA and NVMe SSDs.
 
I really can't see a bigger drive size alone being the issue.
"Over 2TB" is a boundary for edge cases here because MBR can only address up to 32-bits of 512-byte sectors, which is 2TB. Of course, y'all oughtta be using GPT partitions as it's 2025.
 
It's funny to read through the broader conversation. https://news.ycombinator.com/item?id=22491561 Orange Reddit's sentiment towards X has shifted so hard and so fast I'm surprised some of these twits don't get nosebleeds. Lots of folks there singing the praises of X. This was just 5 years ago.
The same sort of trendfagging that compels people to use MongoDB where completely unnecessary, then stick Mongoose on top of it to make MongoDB more like whatever SQL implementation should have been used in the first place
 
"Over 2TB" is a boundary for edge cases here because MBR can only address up to 32-bits of 512-byte sectors, which is 2TB. Of course, y'all oughtta be using GPT partitions as it's 2025.
It blows my mind MBR is default, and I can't believe they didn't consider a scenario of having a larger drive. It's even worse there isn't even an option to GPT.

I didn't take a look at the selection to doing my own partitioning though, maybe I could have selected GPT there. But Artix was going to just make a EFI partition and then the rest was whatever flavor (EXT4/btrfs/etc), and that's not how I was setting up my arch install (efi, boot, with root/home in lvm) so I wasn't even sure my usual set up would work.
 
It blows my mind MBR is default, and I can't believe they didn't consider a scenario of having a larger drive. It's even worse there isn't even an option to GPT.

I didn't take a look at the selection to doing my own partitioning though, maybe I could have selected GPT there. But Artix was going to just make a EFI partition and then the rest was whatever flavor (EXT4/btrfs/etc), and that's not how I was setting up my arch install (efi, boot, with root/home in lvm) so I wasn't even sure my usual set up would work.
I thought it probes how the install iso boots and goes from there. If you boot the installation drive in CSM/Legacy mode it'll format as MBR, and if you boot the installer as a UEFI drive it will format as GPT. That way you don't have a system that refuses to boot because it tried to install a GPT partition but the BIOS can't read GPT
 
I thought it probes how the install iso boots and goes from there. If you boot the installation drive in CSM/Legacy mode it'll format as MBR, and if you boot the installer as a UEFI drive it will format as GPT. That way you don't have a system that refuses to boot because it tried to install a GPT partition but the BIOS can't read GPT
I thought that was my mistake as well, so i double checked. I had disabled legacy boot and even when I re-enabled it my boot media bitched at me about not launching as UEFI. Also, Artix is the first time I've ever not had ISO mode work for writing an image. Rufus has to do it in dd for it to partition the USB correctly 🤔

all 3 machines I've put Artix on
Would you check if your drives are GPT just for the sake of my curiosity?
 
I thought it probes how the install iso boots and goes from there. If you boot the installation drive in CSM/Legacy mode it'll format as MBR, and if you boot the installer as a UEFI drive it will format as GPT. That way you don't have a system that refuses to boot because it tried to install a GPT partition but the BIOS can't read GPT
Yes, this is often how the logic works, how I understand it as well. Your boot mode determines the partitioning choices. My qemu artix instance uses EFI and installed on GPT. Probably ghostbro's issue. Still not helpful that it went MBR on 4TB. I wonder if that's a Calamares bug or an Artix bug, as the Artix installer is Calamares.
 
Yes, this is often how the logic works, how I understand it as well. Your boot mode determines the partitioning choices. My qemu artix instance uses EFI and installed on GPT. Probably ghostbro's issue. Still not helpful that it went MBR on 4TB. I wonder if that's a Calamares bug or an Artix bug, as the Artix installer is Calamares.
I think one of the main things is checking for the existence of efivars. I could be wrong though. It basically is checking the mode it was booted in by doing that. But I think there are edge cases where those aren't being set up by the bios for some reason, even though you are using uefi. So the it will act as if it was bios booted.
 
Still not helpful that it went MBR on 4TB. I wonder if that's a Calamares bug or an Artix bug, as the Artix installer is Calamares.
There are ways to address up to 16TB on MBR (512e) but I don't know what the state of support for that is on Linux and it would be weird for the installer to assume the hardware controller could even do that.

I'd report this bug to Artix. If they don't care submit it to Calamares.
 
Really starting to like ranger (tidying ~/Downloads here)
Screenshot 2025-08-31 16:51:21.webp
 
Really starting to like ranger (tidying ~/Downloads here)
I'd recommend lf over ranger because its basically the same and noticeable faster. At least for mounting large hard drives. Uses the same keybinds, and can be integrated with ranger's files (or shell scripts of your own) like rifle if you want to launch stuff. Or you can use xdg-utils or just a regular opener script.
 
Does anyone have a similiar tool to SDI tools/Snappy driver installer for Linux? Mint, specifically. I'm trying to get my network driver up so I can connect to my Wi-Fi and setup the rest of my drivers.
Mint has Driver Manager, but how old is your kernal? When I installed Mint it came with all the drivers I needed.
 
I'd recommend lf over ranger because its basically the same and noticeable faster. At least for mounting large hard drives. Uses the same keybinds, and can be integrated with ranger's files (or shell scripts of your own) like rifle if you want to launch stuff. Or you can use xdg-utils or just a regular opener script.
ChatGPT suggested that ranger may be a bit more "batteries included" than lf and I haven't noticed slow speed yet
 
Back
Top Bottom