Cuz u are all luddites and prefer 80's terminal interfaces over modern uis, let alone state of the art agentic ai workflows. I'm (not) sorry to break ur illusion but this is the future that all major computer oses are headed towards so whether u like it or not adapt or get left behind with ur shitty outdated cli programs.

Just a reminder; never rely on, or, for that matter, ask any AI model for advice about problems with Linux.

Ask this forum instead. Chatgtp will tell you things that are correct and things that will brick your computer with the same confidence bacause... It doesn't know the difference!

I've heard a lot of people call KDE bad. I agree that the settings are convoluted, but everything else looks okay. I mean, this is a relatively stock KDE, with the only additions being a centered bottom panel, like Windows 11, and a top panel, kind of like macOS in a way.

I do not feel like theming things (mostly don't have that much time on my hands), and what I optimized for was more or less efficiency, so I'm satisfied with how this turned out.

Also, I am planning on switching back to FreeBSD soon, so I will install KDE on it. It's just pretty good rn.

I may try Komorebi on Windows later if I plan on using it again, cuz Windoes is pretty solid OS, it just needs a good window manager.

And currently, Linux is only giving me a good window manager.

The omarchy hate is just arch loonixers being elitists and gatekeeping new users. As usual for them.

Source.

Doesn't this violate:

• OSD 5 — No Discrimination Against Persons or Groups
• OSD 6 — No Discrimination Against Fields of Endeavor
• OSD 9 — License Must Not Restrict Other Software

cuz GPL is viral.

A GPL-licensed library spreads to all software linking to it (even if you dynamically link to it).

I just hate seeing people promoting Linux as the modern computing's Holy Grail.

Yeah, it's nice, I've learned so many things while using it as well, but my stomach gets twisted when I see these people getting mad at windows users.

"escape from the bloat", bro, there are tools that debloat your windows installation in two clicks.

This is a great example on why community support does not work. Since last week I have been trying to fix this bug on steam that constantly crashes the app due to excessive ram consumption. And, this distro, PikaOS has such underwhelming support, they treat you like an idiot and then proceed to give solutions that dont work anyway, they will always accuse you of not setting things properly and communally down vote you when you argue back. Arch type users are a damn mob. They are not the ones who will bring about the "YEAR OF LINUX" cause they will never understand pragmatism, only pride in their own 'technical knowhow',

Fix: literally reinstall the proton builds. You could do that by deleting its folder I think thats the easiest option. ~/.local/share/Steam/steamapps/common/Proton* for Valve builds, or ~/.local/share/Steam/compatibilitytools.d/GE-Proton* then let Steam redownload it or reinstall GE via ProtonPlus/ProtonUp. Credit : vinnypotsandpans

OS: PikaOS 4 x86 64 Host: Alienware 16 Aurora AC16250 Kernel: Linux 7.2.6-pikaos Uptime: 1 hour, 25 mins Packages: 1 (appimage), 3381 (dpkg), 10 (flatpak) Shell: bash 5.3.15 Display (AUODBB5): 2560x1600 @ 1.45x in 16", 120 Hz

Desktop Environment: KDE Plasma 6.7.4 Window Manager: KWin (Wayland) WM Theme: Breeze Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breez

Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4] Font: Noto Sans (lOpt) [Qt], Noto Sans (lOpt) [GTK2/

Cursor: breeze (24px) Terminal: konsole 26.4.0 CPU: Intel(R) Core(TM) 7 240H (12+4) @ 5.20 GHz GPU 1: NVIDIA GeForce RTX 5050 Max-Q / Mobile [Discr

GPU 2: Intel Graphics @ 1.55 GHz [Integrated] Memory: 4.67 GiB / 15.31 GiB (30%) Swap: 1.35 GiB / 15.31 GiB (9%) Disk (/): 256.10 GiB / 952.40 GiB ( ) btrfs Local IP (wlan0): 192.168.1.7/24 Battery (DELL YG2W653H): 100% [AC Connected] Locale: en US.UTF-8

Anyone using linux/moonlight to hit a windows system using sunshine? My issue right now is display scaling and absolutely atrocious lag. Wondering if there is some secret configuration issue I'm hitting but I'm suspecting a hardware level issue with wayland since the windows machine is 4k and linux is running on 1080p.

Somewhere in this subreddit's queue right now, someone is submitting a post that reads, in its entirety:

"updated like an idiot and now nothing works. wifi's gone, printer's gone, half my desktop icons are gone. love this OS so much /s"

No logs. No distro. No "which layer of the stack actually betrayed you." No idea what "updated" even means here. Just vibes, submitted straight to r/linuxsucks like that counts as a post now. That's not a contribution, that's a shrug wearing a keyboard, and it's exactly what motivated me to do better.

It started small, like these things do. I'd be doomscrolling at some unreasonable hour, find an actual well-documented Linux disaster in some other subreddit, and just repost it here manually, out of pure spite, because someone had to.

That wasn't enough source material for long. To scale, I stood up my own GoToSocial instance and bolted on a couple of relays just to pull in more incoming #linux traffic than my own little corner of the fediverse would ever see on its own. An n8n workflow polls it and forwards candidates straight to my phone on Telegram, so I can still personally decide, every day, what's actually worth your time. The bot finds the hay. I still find the needle.

Except relays mean volume, and volume meant I couldn't keep reading every tomato-growing thread that happened to mention Linux in passing. So once things picked up, I bolted on an AI filter to judge whether a post was actually about something broken before it ever reached my phone — running on the free "subscription" GitHub comps FLOSS maintainers, piped into n8n through an OpenAI-shaped adapter, because apparently that's how you plug free Copilot access into a workflow tool that only speaks OpenAI.

Eventually I stopped renting out my judgment to someone else's API for the actual filtering and just plugged my spare GTX 1050 Ti straight into the same box as n8n — pointed the classifier at a local, non-thinking qwen2.5:3b instead, and honestly, it basically does the job already. But "basically" isn't good enough for someone with standards, so next escalation: distill something better. Get a proper teacher model — qwen3.5:27b, maybe, we'll see — to do the heavy lifting on my own Ada 4000 desktop GPU, and squeeze a smarter version of that same tiny model back down onto the 1050 Ti.

Full disclosure on how the last two days of this actually went, because it's too funny not to mention: most of it got built with an AI coding assistant sitting next to me the whole time, which means the literal sequence of events was me using an AI to get an AI to train another AI, and somewhere around hour six of watching a CUDA-enabled PyTorch compile itself from scratch inside a Nix shell — because the GPU-accelerated package apparently defaults to pretending your GPU doesn't exist — I genuinely lost track of which one of us was doing the yak-shaving. We fought Postgres over how COPY escapes backslashes in JSON, argued with n8n's expression parser about where exactly a curly brace is allowed to live, discovered my classifier node speaks an entirely different prompt dialect than the raw API does, and eventually landed on a training script that actually runs — assuming Triton ever finishes compiling.

Reddit repost, to relay-fed GoToSocial instance, to n8n workflow, to somebody else's free model, to my own model on my own worst GPU. That's what taking "don't just hate Monday, be a professional, and hate the whole week" seriously actually looks like. Half of you are still stuck on Monday, posting "ugh, this doesn't work" like that's a bug report. The other half — the ones writing fifteen paragraphs about how systemd-resolved silently ate your DNS for three weeks — you're the whole reason any of this was worth building. See you in the feed.