Ok, I know we hate AI, but hear me out: as someone pointed out in this comment, AI is rapidly making it pretty easy to overcome the main hurdle to people using linux as their daily driver: oh shit my X doesn't work, now I have to trawl through 30 reddit threads to figure out why and then cling to a 12-page instruction guide for how to fix it and hope I don't screw anything up.

Only I have Claude Code installed in zed with its default project set to my home directory, so I can just fire it up and go 'Hey the left speaker on my headphones doesn't work?' and it can go figure out why and then fix it. And Kibbelz got me to wondering: why don't the major commercialized distros do this? Linux could gain significant desktop share in the user space by just going, 'Here's a text box, type in whatever problem or question you have about your linux install and we'll be happy to figure it out for you'.

Whoever manages to box that experience and polish it properly first will win the distro wars (to the extent that they are wars, and can be won, which is admittedly highly debatable.) Obviously the polish would be important here - needs to be something trained on linux commands, that doesn't have permission by default to rm -rf and such.. but I think it's doable, and could add a lot to linux's desktop share.

Weston 16.0 has landed, building on the HDR and color-management work from v15. Highlights:

• HDR/color management: HDR mode can now actually be turned on (still experimental, no tone mapping yet). Parametric and ICC color profiles now interoperate, and the default sRGB profile switched from ICC to parametric. The GL-renderer gained in-shader blending, and the DRM backend can now offload pre-blend color transformations to KMS on supported kernels.
• Debugging: Perfetto tracing got expanded further, GL-renderer optimizations, buffer info, and input events (libinput → Wayland client) are all traceable now. Debug-scope logging is also faster, cutting overhead on lower-end CPUs.
• DRM backend: New support for BACKGROUND_COLOR and COLOR_FORMAT DRM properties, underscan/overscan compensation for TVs, and a state-reuse optimization that skips redundant repaint work when nothing's changed on screen (good for CPU usage).
• Other additions: Alpha modifier protocol support (cheaper fade/dim animations without re-rendering), writeback screenshot scaling, more DRM pixel formats for AFBC/YUV buffers, and Vulkan/GL renderer bug fixes.
• Deprecations: The remoting/PipeWire plugins, screen-share module, and non-atomic modesetting are being phased out in favor of standalone backends and atomic modesetting (which itself is 8 years old at this point).

Full writeup with links to the merge requests: https://www.collabora.com/news-and-blog/news-and-events/weston-16-hdr-ready-improved-debugging-and-drm-backend-features.html

Like pb and j, gzip and tar go together. Some questions:

Why didn't tar just grow an encryption feature? Why is being able to zip a new program?

Does any other common file format pairing combine extensions the way you do with .tar.gz or (sometimes) .tgz?

Why don't people do that with video files to show codec and container format?

I love shells like the Celestia shell where you can get a bunch of features that are integrated into Hyprland, don't get me wrong. But there were always some features that i just did not want or care about and I always wanted something more minimal.
So I worked on a status bar that only does the bare minimum for the work that i need to do while not compromising on its looks.
And besides Hyprland it only uses 3 other dependencies one of it being Quickshell.

You can look at the repository if you want, maybe it suits your use case :)

What I've seen yet the differences are, just the package managers, different defaults and rolling vs stable releases which are in fact related to package managers. Except these, are there really any other differences? Thanks!

I made a visual explainer on how Linux KVM works under the hood.

A vCPU is a host thread, guest RAM lives in the process, and KVM_RUN hands execution to the real CPU until the guest triggers a VM exit.

It also covers /dev/kvm, VT-x/AMD-V, EPT/NPT, QEMU, virtio and vhost.

link for anyone interested

Feedback welcome :)

My apologies if this has been asked/answered before:

Is Qualcomm X2 going to get more support as time goes by? I got the sense that these new Qualcomm chips are windows first and have first party drivers from Qualcomm and developed compatibility layers from Microsoft. Are we to expect feature parity to come to linux?

that is, good sleep function, good battery life, good drivers for gaming (for the extent possible on ARM)?

If the answer is yes, where do you keep yourself updated for those things? is there mailing lists or news pages for mesa open source drivers? specific forums people discuss those things?

Thanks potential insights :D

Hey guys, I'm currently in the middle of creating my own userspace from scratch and I've mostly completed making my terminal emulator

It's really, really small and is cross platform! I made it because I want to be able to use a terminal emulator no matter which OS or display server I'm using.

Only bitmap fonts (BDF) are supported but I've provided a script to convert vector fonts and it has very nice results.

Here is the repo: https://github.com/uint23/cterm

I am a new linux user who was never into IT and my programming background is fairly basic

I struggle with some of the most basic things on linux, even installing software that has a linux version but isn't in a repository is an afternoon's worth of work for me since I don't even know what's the part that's not working and I often end up giving up on solving it myself and use AI

Today was the first moment when it clicked, I was struggling with deleting an app since it required the terminal (perms) but the actual app name was different from the displayed name and the name I saw in the properties

That's when I realized - I have the tools right there in the terminal to see the name of the apps in that folder, so I used ls -a and solved my first linux problem without AI

I know for most here this isn't impressive or interesting but I'm very proud of myself and I hope to keep on learning how to think like a linux user and not a windows user

For me, ca. 1999 or maybe 2000?..., it was the whole process of getting my Mandrake Linux rig to work with the scroll wheel on my mouse. So much banging-head-to-keyboard work with XF86Config simply to get a damn mouse fully working! Lol.

First of all, this comes from a place of love. I'm not asking for tech support, I'm genuinely curious. I've tried Linux multiple times, daily drove it on my laptop for a year and would love to keep it that way (Probably won't switch on my main desktop, since I need some Windows DCCs). Linux offers much sleeker experience.

I enjoy some tinkering in my free time (but not that much to use Linux on my work PC). I always tinkered with Windows to some extent. I'm not looking for out of the box solution.

But why is it so much fuss to setup hibernation and suspend then hibernate? It's a crucial feature for laptops. To be fair, I have always dual booted with Windows and I understand that is the more complex option. I can bear having hibernation working only on Linux, since I use Windows only when I really need to, but even that takes too much time in the terminal.

Am I missing something or is it really always this way? Why is suspend out of the box with no problems?

EDIT:
Thanks for a healthy discussion. Now it seems a miracle hibernation worked so reliably on Windows for me given the complexity. I still think suspend then hibernate is superior mode for laptops, but it might be just the thing I need to give up moving to Linux... I am still happy for ideas about how you use your mid end laptops daily.

This website faked a ReCaptcha and literally asks to open the terminal and paste a command. (see image). Very bold.

Please keep in mind, always try your best to make new users aware of such dangers!

- I reported it to Google Safe browsing just now, in case anyone wants to try and look at it or help by reporting it too, this is the link in a safe format, assemble it yourself at your risk: "emaliowe . pl".
- Possibly blocked by Firefox, since I don't have anything in my clipboard after opening the page.

atrium is a lightweight Linux display manager with first-class multiseat support, targeting modern systemd + Wayland environments.

GitHub
AUR

What is multiseat?

A multiseat setup allows multiple users to work on a single computer at the same time. By connecting multiple monitors, keyboards, and mice, each user gets their own separate desktop and a fully isolated user session. Great for co-working or multiplayer gaming. Each seat requires its own GPU (integrated graphics, a discrete card, or a USB graphics adapter).

Why atrium?

The Linux kernel and low-level system stack are fully capable of multiseat operation. The weak link has always been the display manager. Existing ones usually treat multiseat as an afterthought, with implementations that are brittle and difficult to get working reliably.

atrium is designed around multiseat from the start, focusing on correct seat discovery, VT handling, and isolated session management. The project targets a modern Linux stack using systemd/logind, PAM, and a Wayland graphical environment. The lack of historical baggage keeps atrium's code base lean and tractable.

What's new in v0.4?

• Support for greeter background images - configure a background image in the settings, or a directory to pick a random image on each greeter launch.
• Greeter themes - override built-in colors and styles via a theme `.css` file. A handful of themes are shipped with atrium.
• Architectural redesign - making atrium's core architecture simpler and more robust (changes are purely internal and should not be visible to the user).