Linux - Reddit – Telegram
Linux - Reddit
744 subscribers
4.15K photos
207 videos
39.7K links
Stay up-to-date with everything Linux!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
Fedora as Daily Driver for Academic Research
https://redd.it/1pvx24w
@r_linux
I built BrewHouse: A native GTK4 GUI for managing Homebrew on Linux

Hey Linux

First thing, I am not a developer. I managed development teams in the past for a large communications firm. This was written by claude, and tested by me.

I've been using Homebrew on my KDE Neon setup and got tired of managing packages via CLI, so I built BrewHouse \- a native GTK4 application for browsing, installing, and managing Homebrew packages. I saw Windows and macOS had GUI's and thought it would be better for managing brew in Linux. Basically, scratched my itch.

I think the searching function is my favorite, as I was always guessing what was available prior to this.

It is simple but effective for me. Written in Rust. Free, MIT license.

https://github.com/threeforksp/brewhouse

I've not addressed any security issues, welcome for input.

Open to suggestions, bug reports, and contributions!






https://redd.it/1pw7mkd
@r_linux
Thinkpad T14 gen 5 or gen 6? AMD or Intel?

I will be buying a new laptop, I have decided to go with the T14. I will be using it mainly to read and write docs/presentations, light coding. I would like 8+ hours battery life ideally, and am willing to sacrifice power and performance for that.

I will be using either debian or a fork of arch. Would like to be able to upgrade RAM and storage later on.

Given all that which option would suit me best?

https://redd.it/1pwmvh1
@r_linux
I reinvented htop in C because I hate myself
https://redd.it/1pwpv2i
@r_linux
Is there a Linux replacement for NAVE Gaming Center?

Hi everyone! I’d like to install Linux on my laptop to run some tests, but I have a question first: my laptop is a N.A.V.E model and on Windows I rely on the management software to switch between modes like performance/silent and also to change the keyboard RGB settings.

On Linux, is there any alternative (app, driver, kernel module, noscript, etc.) that can provide similar features? Especially performance profiles and keyboard lighting control?

https://redd.it/1pwzovg
@r_linux
Where to start with debugging/fixing a broken out of tree driver?

I have a Magewell video capture card and the (proprietary, source-available) driver broke between kernel 6.17 and 6.18. It builds and loads fine, but opening the device (/dev/video0) returns ENODEV, and some kind of call trace gets printed to the journal.

I'm happy to provide more details here, not seeking support, understand this is not the appropriate forum just looking for a primer on debugging this type of thing myself. I'm comfortable hacking and reading call traces in userspace, but kernel space is new to me.

https://redd.it/1px3npj
@r_linux
Happy Birthday, Linus Torvalds
https://redd.it/1pxbe8v
@r_linux
Wayland is flawed at its core and the community needs to talk about it

TL;DR: Wayland bakes a paranoid security model directly into its protocol instead of using a sane capability system, breaks tons of important software (RenderDoc, xkill, automation tools, etc), solves threats that basically dont exist in practice, and projects like COSMIC arent even bothering with X11 support anymore. If X11 dies completely, entire workflows and niches are going with it. We either need Wayland to change its philosophy or start from scratch with something new.


I've been daily driving Linux for about 5 years now. Not the longest time compared to some of you, but enough to understand why I'm here. I want to actually my computer. That's the whole reason. Windows kept doing stuff I didn't ask for, and Linux was the answer. So why does it feel like Wayland is trying to bring that same energy back?

My core issue with Wayland is that it confuses security philosophy with protocol design. The developers decided early on that applications should be completely isolated from each other. One window cannot know anything about another window. An application cannot grab pixels from another application. Programs cannot position other programs windows.

And before someone says "but security!", look: this isolation ISN'T a configurable security layer you can adjust based on your needs. Its THE fundamental architecture. When Wayland devs say "we dont support feature X because security", what they really mean is "we designed ourselves into a corner and now we literally cant add this without breaking everything."

You know how actual secure systems work? Capabilities. The Linux kernel does this with stuff like CAP_NET_ADMIN or CAP_SYS_PTRACE. SELinux does this. AppArmor does this. Even Android, which is paranoid as hell about security, has a granular permission system where you can say "yes this app can do this specific thing."

Wayland could have been designed like a microkernel approach. Minimal core protocol, well defined extension points, capability system where compositors grant specific permissions to specific apps. Want your automation tool to see window positions? Grant it that capability. Screenshot tool needs to capture specific windows? Theres a capability for that.

But no. Instead we got "nobody can do anything unless we specifically designed a portal for it, and even then your compositor might not implement that portal, so good luck lmao."

And I would shut up if that actually solved something, but it solves problems that dont really exist. Lets talk about what Wayland supposedly protects us from. The classic example is keyloggers: on X11, any application can read keystrokes from any other application. Sounds bad right?

But think about it for a second. If malicious software is running on your system with your user permissions, you already lost. That application can read your files. It can access your browser cookies. It can modify your bashrc to capture passwords. It can install itself as a systemd user service. It can do literally anything you can do.

The idea that preventing it from reading X11 events makes you meaningfully more secure is honestly a fantasy. The actual threat model where X11 isolation matters is basically nonexistent in the real world. Meanwhile, the restrictions that "protect" you from this theoretical threat break actual software that real people use every day. Not bad enough, there are a LOT of actual useful stuff that break down because of this. This is where I get actually frustrated. Here's software that just doesnt work properly under Wayland:

RenderDoc is probably the most important graphics debugging tool out there. If you do anything with Vulkan or OpenGL, you need this. It works by injecting into the target process and capturing API calls. Wayland's security model makes this a nightmare. If youre a graphics dev on Linux, this alone should concern you.

Theres no xkill equivalent. On X11, window freezes, you run xkill, click on it, its dead. Simple. Been working for decades. On Wayland you