1
449
submitted 2 years ago* (last edited 2 years ago) by wfh@lemm.ee to c/linux@lemmy.ml

You're about to take your first steps in the wonderful world of Linux, but you're overwhelmed by the amount of choices? Welcome to this (I hope) very simple guide :)

The aim of this guide is to provide simple, clear information to ease your transition as a beginner. This is not a be-all-end-all guide nor an advanced guide. Because there is a lot of info and explanations everywhere, I will often (over-)simplify so as to keep the information accessible and digestible. Please refrain from asking to add your favorite distro/DE in the comments, I feel there is too much choice already ;)

Preamble

Make sure your hardware is compatible

Nowadays most relatively recent hardware works perfectly fine on Linux, but there are some edge cases still. If you don't use niche hardware and your wifi card is supported, chances are you're golden. Please note that nVidia is a bad faith player in the Linux world, so if you have a GeForce GPU, expect some trouble.

Make sure your favourite apps are either available or have a good replacement on Linux

If some proprietary app is essential to your workflow and is irreplaceable, consider running it in a VM, keeping a Windows partition for it or try and run it through Wine (this is advanced stuff though).

Be aware that Linux is not Windows/MacOS

Things work differently, and this is normal. You will probably struggle at the beginning while adjusting to a new paradigm. You may have to troubleshoot some things. You may break some things in the process. You will probably get frustrated at some point or another. It's okay. You're learning something new, and it can be hard to shed old habits forged by years on another system.

When in doubt, search for documentation

Arch Wiki is one of the greatest knowledge bases about Linux. Despite being heavily tied to Arch, most of its content is readily usable to troubleshoot most modern distros, as the building blocks (Kernel, systemd, core system apps, XOrg/Wayland, your DE of choice etc.) are the same. Most distros also maintain their own knowledge base.

Understanding the Linux world

What is Linux?

Linux, in the strictest definition, is the kernel, ie. the core component that, among other things, orchestrates and handles all interactions between hardware and software, of a large family of operating systems that, by metonymy, are called "Linux". In general understanding, Linux is any one of these operating systems, called distros.

What is a distro?

A distro, short for "Software Distribution", is a cohesive ensemble of software, providing a full operating system, maintained by a single team. Generally, all of them tend to provide almost the same software and work in a very similar way, but there are major philosophical differences that may influence your choice.

What are the main differences between distros?

As said above, there are a lot of philosophical differences between distros that lead to practical differences. There are a lot of very different ways the same software can be distributed.

  • "Point Release" (OpenSUSE Leap) vs. "Rolling Release" (OpenSUSE Tumbleweed): Point release distros are like traditional software. They have numbered releases, and between each one no feature updates take place, only security updates and bug fixes. Rolling Release distros package and distribute software as soon as it's available upstream (the software developer's repos), meaning that there are no versions and no specific schedule.
  • "Stable" (Debian Stable) vs. "Bleeding edge" (Arch): Stable distros are generally point release, and focus on fixing bugs and security flaws at the expense of new features. Each version goes through a lenghty period of feature freeze, testing and bug fixing before release. Stability here not only means trouble-free operation, but more importantly consistent behavior over time. Things won't evolve, but things won't break. At least until the next release. Bleeding edge distros, which often follow the rolling release model (there are outliers like Fedora which are mostly bleeding edge yet have point releases), on the other hand, are permanently evolving. By constantly pushing the latest version of each software package, new features, new bugs, bug fixes, security updates and sometimes breaking changes are released continuously. Note that this is not a binary, there is a very large continuum between the stablest and the most bleeding edge distro.
  • "Community" (Fedora) vs. "Commercial" (RHEL): Despite the name, Community distros are not only maintained by volunteers, but can also be developed by some company's employees and can be sponsored by commercial entities. However, the main difference with Commercial distros is that they're not a product destined to be sold. Commercial distros like Red Hat's RHEL, SuSE Linux Enterprise or Ubuntu Pro are (supposed to be) fully maintained by their company's employees and target businesses with paid support, maintenance, fixes, deployment, training etc.
  • "x package manager" vs. "y package manager", "x package format" vs. "y package format": It doesn't matter. Seriously. apt, dnf or pacman, to name a few, all have the exact same purpose: install and update software on your system and manage dependencies.
  • "general purpose" (Linux Mint) vs. "niche" (Kali Linux): General purpose distros are just that: distros that can do pretty much anything. Some are truly general purpose (like Debian), and have no bias towards any potential use, be it for a server, a desktop/laptop PC, some IOT or embedded devices, containers etc., some have various flavors depending on intended use (like Fedora Workstation for desktops and Fedora Server for, you guessed it, servers) but are still considered general purpose. They aim for maximum hardware compatibility and broad use cases. At the opposite end, niche distros are created for very specific and unique use cases, like pentesting (Kali), gaming (Nobara), music production (AV Linux) etc. They tend to have a lot of specific tools preinstalled, nonstandard defaults or modified kernels that may or may not work properly outside of their inteded use case.
  • "team" (Any major distro) vs. "single maintainer" (Nobara): Pretty self explanatory. Some distros are maintained by a single person or a very small group of people. These distros do not usually last very long.
  • "traditional" (Fedora Workstation) vs. "atomic" (Fedora Silverblue): In traditional distros, everything comes from a package. Every single component is individually installable, upgradeable, and deletable. Updating a package means deleting its previous version and replacing it with a new one. A power failure during an update lead to a partial upgrade and can make a system unbootable. Maybe a new package was bad and breaks something. Almost nothing prevents an unsuspecting user from destroying a core component. To mitigate risks and ensure a coherent system at each boot, atomic (also called transactional or immutable) distros, pioneered by Fedora Silverblue and Valve's SteamOS, were born. Like mobile phone OSes, the base system is a single image, that gets installed, alongside the current running version and without modifying it, and becomes active at the next reboot. As updates are isolated from one another, if the new version doesn't work the user can easily revert to a previous, functional version. Users are expected to install Flatpaks or use Distrobox, as installing (layering) packages is not as straightforward as with standard distros.
  • "OG" (Debian) vs. "derivative" (Ubuntu): Original distros are directly downstream of their components' source code repositories, and do most of the heavy lifting. Because of the tremendous amount of work it represents, only a few distros like Debian, Arch, Slackware or Fedora have the history, massive community and sometimes corporate financial backing to do this. Other distros reuse most packages from those original distros and add, replace or modify some of them for differenciation. For example, Debian is the parent of almost all deb-based distros like Ubuntu, which itself is the parent of distros like Mint or Pop!_OS.

What are the main components of a distro, ie. a Linux-based operating system?

All distros provide, install and maintain, among other things, the following components:

  • Boot and core system components (these are generally out-of-scope for beginners, unless you need to fix something, but you should at least know they exist):
    • A boot manager (GRUB, systemd_init, etc.): Boots the computer after the motherboard POSTs, lets you choose what to start
    • An init system (systemd, etc.): Starts everything needed to run the computer, including the kernel
    • A kernel (Linux): Has control over everything, main interface for software to discuss with hardware
  • Command-line environment, to interact with he computer in text mode:
    • A shell (bash, zsh, fish etc.): The main interface for command-line stuff
    • Command-line tools (GNU, etc.): Standard suite of command-line tools + default tools chosen by the distro maintainers
    • User-installable command-line tools and shells
  • Graphical stack for desktop/laptop computers:
    • Display servers (X11, Wayland compositors): Handle drawing stuff on screens
    • A Desktop environment (Plasma, Gnome, XFCE etc.): The main graphical interface you'll interact with everyday.
    • User-facing applications (browsers, text processors, drawing software etc.): Some are generally installed by default and/or are part of a desktop environment's suite of software, most are user-installable.
  • A package manager (apt, dnf, pacman, yast etc.): Installs, deletes, updates and manages dependencies of all software installed on the machine.

Which are the main Desktop Environments and which one should I choose?

As a new user, this is basically the only thing you should concern yourself about: choosing a first Desktop environment. After all, it will be your main interface for the weeks/years to come. It's almost as important as choosing your first distro. These are a few common choices that cater to different tastes:

  • Gnome: Full featured yet very minimalist, Gnome is a great DE that eschews the traditional Desktop metaphor. Like MacOS, out of the box, it provides its strongly opinionated developers' vision of a user experience. Fortunately, unlike MacOS, there are thousands of extensions to tweak and extend the looks and behaviour of the DE. Dash-to-dock or Dash-to-panel are great if you want a more MacOS-like or Windows-like experience, Blur My Shell is great if you love blurry transparent things, Appindicator is a must, and everything else is up to you. Gnome's development cycle is highly regular and all core components and apps follow the same release schedule, which explains why a lot of distros choose it as their default DE.
  • KDE Plasma: Full featured and maximalist, Plasma does not cater to a single design philosophy, is very flexible and can be tweaked almost ad infinitum. This may be an advantage for people who like to spend hours making the perfect environment, or a disadvantage as the possibilities can be overwhelming, and the added complexity may compromise stability, bugginess or completeness. There is not yet a single development cycle for core components and apps, which makes it a bit more difficult for distro maintainers and explains why there are so few distros with Plasma as the flagship DE. The KDE team is however evolving towards a more regular update cycle.
  • Cinnamon: Forked from Gnome 3 by the Linux Mint team who disliked the extreme change of user experience it introduced, Cinammon provides a very traditional, "windows-like", desktop-metaphor experience in a more modern software stack than the older DEs it takes inspiration from. Cinnamon still keeps a lot in common with Gnome by being simple and easy to use, yet heavily modifiable with themes, applets and extensions.
  • Lightweight DEs for old or underpowered machines: The likes of XFCE, LXDE, LXQt are great if you want to ressurect an old machine, but lack the bells and whistles of the aforementioned DEs. If your machine is super old, extremely underpowered and has less than a few Gb of RAM, don't expect miracles though. A single browser tab can easily dwarf the RAM usage and processing power of your entire system.

As for which one you should choose, this is entirely up to you, and depends on your preferences. FYI, you are not married to your distro's default desktop environment. It's just what comes preinstalled. You can install alternative DEs on any distro, no need to reinstall and/or distro-hop.

How do I install stuff on Linux?

Forget what you're used to do on Windows of MacOS: searching for your software in a seach engine, finding a big "Download" button on a random website and running an installer with administator privileges. Your package manager not only keeps you system up to date, but also lets you install any software that's available in your distro's repositories. You don't even need to know the command line, Gnome's Software or Plasma's Discover are nice graphical "App Stores" that let you find and install new software.

Flatpak are a great and more recent recent alternative to distro packages that's gaining a lot of traction, and is increasingly integrated by default to the aforementioned App Stores. It's basically a "universal" package manager system thet sits next to your system, that lets software developers directly distribute their own apps instead of offloading the packaging and distribution to distro maintainers.

Choosing a first distro

As discussed before, there is a metric fuckload (or 1.112 imperial fucktons) of distros out there. I advise you to keep it as mainstream as possible for your first steps. A distro with a large user base, backed by a decently large community of maintainers and contributors and aimed at being as fuss-free as possible is always better than a one-person effort tailored to a specific use-case. Choose a distro that implements well the DE of your choice.

What are great distros for beginners?

The following are great distros for beginners as well as more advanced users who just want to have a system that needs almost no configuration out of the box, just works and stays out of the way. Always read the installation documentation thoroughly before attempting anything, and follow any post-install requirements (for example, installing restricted-licence drivers on Fedora).

  • Fedora Workstation: Clean, sensible, modern and very up to date and should work out of the box for most hardware. Despite being sponsored by Red Hat (who are getting a lot of justified hate for moving RHEL away from open-source), this is a great community distro for both beginners and very advanced users (including the Linus Torvalds). Fedora is the flagship distro for the Gnome Desktop Environment, but also has a fantastic Plasma version. Keywords: Point Release, close to Bleeding Edge, Community, dnf/rpm, large maintainer team, traditional, original.
  • Linux Mint: Mint is an Ubuntu (or Debian for the LMDE variant) derivative for beginners and advanced users alike, that keeps Ubuntu's hardware support and ease of use while reverting its shenanigans and is Cinammon's flagship distro. Its main goal is to be a "just works" distro. Keywords: Point Release, halfway between Stable and Bleeding Edge, Community, apt/deb, smallish maintainer team but lots of contributors, traditional, derivative (Ubuntu or Debian).
  • Pop!_OS: Backed by hardware Linux vendor System76, this is another Ubuntu derivative that removes Snaps in favor or Flatpaks. Its heavily modified Gnome DE looks and feels nice. In a few months/years, it will be the flagship distro for the -promising but still in development- Cosmic DE. Keywords: Point Release, halfway between Stable and Bleeding Edge, commercially-backed Community, apt/deb, employee's maintainer team, traditional, derivative (Ubuntu).
  • If you want something (advertised as) zero-maintenance, why not go the Atomic way? They are still very new and there isn't a lot of support yet because they do things very differently than regular distros, but if they wort OOTB on your system, they should work reliably forever. Sensible choices are uBlue's Aurora (Plasma), Bluefin (Gnome) or Bazzite (gaming-ready), which are basically identical to Fedora's atomic variants but include (among other things) restricted-licence codecs and QOL improvements by default, or OpenSUSE's Aeon (Gnome). Keywords: Point Release, Bleeding Edge, Community, rpm-ostree, large maintainer team, Atomic, sub-project (Fedora/OpenSUSE).

Which power-user distros should I avoid as a beginner, unless I reaaaally need to understand everything instead of being productive day one?

These are amongst the very best but should not be installed as your first distro, unless you like extremely steep learning curves and being overwhelmed.

  • Debian Stable: as one of the oldest, still maintained distros and the granddaddy of probably half of the distros out there, Debian is built like a tank. A very stringent policy of focusing on bug and security fixes over new features makes Debian extremely stable and predictable, but it can also feel quite outdated. Still a rock-solid experience, with a lot to tinker with despite very sensible defaults. It is an incredible learning tool and is as "Standard Linux" as can be. Debian almost made the cut to "beginner" distros because of its incredible reliability and massive amount of documentation available, but it might be a bit too involved for an absolute beginner to configure to perfection. Keywords: Point Release, Stable as fuck, Community, apt/deb, large maintainer team, traditional, original.
  • Arch: The opposite of Debian in philosophy, packages often come to Arch almost as soon as the source code is released. Expect a lot of manual installation and configuration, daily updates, and regularly fixing stuff. An incredible learning tool too, that will make you intimate with the inner workings of Linux. The "Arch btw" meme of having to perform every single install step by hand has taken a hit since Arch has had a basic but functional installer for a few years now, which is honestly a good thing. I work in sofware. A software engineer who does every single tedious task manually instead of automating it is a shit software engineer. A software engineer who prides themself from doing every single tedious task manually should seriously reconsider their career choices. Arch's other main appeal is the Arch User Repository or AUR, a massive collection of user-created, automated install scripts for pretty much anything. Keywords: Rolling Release, Bleeding-edge, Community, pacman/pkg, large maintainer team, traditional, original.

Which distro should I avoid, period?

  • Ubuntu: despite having a huge mind-share as the beginner distro, Ubuntu suffers from it's parent company's policy to make Ubuntu kinda-Linux-but-not-really and a second-rate citizen compared to their Ubuntu Pro commercial product. Some of the worst takes in recent years have been pushing Snaps super agressively in order to get some "vendor-lock-in", proprietary walled-garden ecosystem with exclusive commercial apps, forcibly installing snaps even when explicitely asking for a .deb package through apt, baking ads and nags into major software or only delivering critical security patches to Pro customers. Fortunately, there are some great derivatives like Mint or Pop!_OS cited above that work equally well but revert some of the most controversial decisions made by Canonical.
  • Manjaro: Manjaro might seem appealing as a "user-friendlier" Arch derivative and some of its tools are fantastic to remove some configuration burden, but ongoing mismanagement issues and the fact that it needs Arch-style regular maintenance as updates often break stuff prevent it from being a truly beginner distro. Manjaro also has a highly irregular update schedule that's weeks behind Arch, making using the AUR extremely dangerous, as it always expects a fully up-to-date Arch system.
  • Any single-maintainer or tiny team distros like Nobara or CachyOS. They might be fantastic distros made by exceptional people (I have mad respect for Nobara's maintainer Glorious Eggroll and his work on Proton-GE), they are most often derivatives so the heavy lifting is already done by their parent distro's maitainers, but there is too much risk involved. Sometimes life happens, sometimes people move on to other projects, and dozens of small distros get abandonned every year, leaving their users dead in the water. Trusting larger teams is a much safer bet in the long term.
  • Anything that refuse to use standards for ideological reasons like Alpine Linux, Devuan or Artix. Don't get me wrong, not using any GNU tools or systemd is a cool technological feat and developing alternatives to the current consensus is how things evolve. However, these standard tools have a long history, hundreds if not thousands of maintainers and are used by millions, meaning there's a huge chance your specific issue is already solved. Refusing to use them should be reserved to very advanced users who perfectly understand what they're gaining and losing. As a beginner to intermediate level, it will at best make most of the documentation out there irrelevant, at worst make your life a miserable hell if you need to troubleshoot anything.

Philosophical questions, or "I've seen people arguing over the Internet and now I'm scared"

You've done your research, you're almost ready to take the plunge, you even read a lot of stuff on this very community or on the other website that starts with a "R", but people seem very passionately for or against stuff. What should you do?

Shoud I learn the command line?

Yes, eventually. To be honest, nowadays a lot of things can be configured on the fly graphically, through your DE's settings. But sometimes, it's much more efficient to work on the command line, and sometimes it's the only way to fix something. It's not that difficult, and you can be reasonably productive by understanding just about a dozen very simple commands.

I have a very old laptop/desktop, should I use a distro from its era?

Noooo!. Contrary to Windows and MacOS which only work correctly on period-correct computers, Linux runs perfectly well on any hardware from the last 20 to 30 years. You will not gain performance by using an old distro, but you will gain hundreds of critical security flaws that have been since corrected. If you need to squeeze performance out of an old computer, use a lightweight graphical environment or repurpose it as a headless home server. If it's possible, one of the best ways to breathe new life into an old machine is to add some RAM, as even lightweight modern sofware will struggle with less than a few Gb.

Should I be concerned about systemd?

No. In short, systemd is fine and all major distros have switched to systemd years ago. Even the extremely cautious people behind Debian have used systemd as default since 2015. Not wanting to use systemd is a niche more rooted in philosophical and ideological rather than practical or technical reasons, and leads to much deeper issues than you should concern yourself with as a beginner.

Should I be concerned about XOrg/Wayland?

Yes and No, but mostly No. First off, most distros install both Wayland and XOrg by default, so if one is not satisfying to you, try the other. Remember in the preamble when I said nVidia was a bad actor? Well, most of people's complaints about Wayland are because of nVidia and their shitty drivers, so GTX/RTX users should stay on XOrg for now. But like it or not, XOrg is dead and unmaintained, and Wayland is the present and future. XOrg did too many things, carried too many features from the 80's and 90's and its codebase is a barely maintainable mess. X11 was born in a time when mainframes did most of the heavy lifting and windows were forwarded over a local network to dumb clients. X11 predates the Internet and has basically no security model. Wayland solves that by being a much simpler display protocol with a much smaller feature set adapted to modern computing and security. The only downside is that some very specific functionalities based on decades of X11 hacking and absolute lack of security can be lost.

I want to play some games, should I look for a gaming distro?

No. General purpose distros are perfectly fine for gaming. You can install Steam, Lutris, Heroic, Itch etc. and use Proton just fine on almost anything. Even Debian. In short, yes, you can game on Linux, there are great tutorials on the internet.

Should I be concerned about Flatpaks and/or Snaps vs. native packages?

Not really. Flatpaks are great, and more and more developers package their apps directly in Flatpak format. As a rule of thumb, for user facing applications, if your app store gives you the choice between Flatpak and your native package manager version, choose the most recent stable version and/or the one packaged by the developer themselves (which should often be the Flatpak anyway). Snaps however are kinda bad. They are a Canonical/Ubuntu thing, so as long as you avoid Ubuntu, its spins and its derivatives that still include Snaps, you should be fine. They tend to take a lot longer to startup than regular apps or Flatpaks, the snap store is proprietary, centralized and Canonical controls every part of it. Also, Canonical is very aggressive in pushing snaps to their users, even forcing them even when they want to install an apt package. If you don't care, have fun.

I need/want program "x", but it is only available on distro "y" and not on mine. I've been told to ditch my beloved distro and install the other one, should I?

No. Generally, most software is intallable from your distro's package manager and/or Flatpak. But sometimes, your distro doesn't package this program you need, or an inconsiderate developer only distributes a random .deb on their Github release page. Enter Distrobox. It is a very simple, easy to use command line tool that automates the creation of other Linux distros containers using Docker or Podman (basically, tiny, semi-independant Linuxes that live inside your regular Linux), and lets you "export" programs installed inside these containers to you main system so you can run them as easily and with almost the same performance as native programs. Some atomic distros like uBlue's variants even include it by default. That .deb we've talked about before? Spin a Debian container and dpkg install the shit out of it. Absolutely need the AUR? Spin an Arch container and go to town.

Acknowledgements

Thanks to everyone who helped improve this guide: @GravitySpoiled@lemmy.ml, @tkn@startrek.website, @throwaway2@lemmy.today, @cerement@slrpnk.net, @kzhe@lemm.ee, @freijon@feddit.ch, @aarroyoc@lemuria.es, @SexualPolytope@lemmy.sdf.org, @Plopp@lemmy.world, @bsergay@discuss.online ...and many others who chimed in in the comments <3

Link to version 1: https://lemm.ee/post/15895051

2
33
submitted 8 hours ago by liberatedGuy@lemmy.ml to c/linux@lemmy.ml

I am using KDE Plasma on Debian Sid. I tried to edit the desktop background to add some widgets. However, it doesn't seem to work as no widgets are showing up in the list. I restarted the machine and yet the problem persists. I am attaching a screenshot. Any idea as to how I can deal with this?

It's not that the widgets are not there. If I click somewhere in the widgets list, then they appear on the desktop. It's just that they don't show up.

3
28
submitted 10 hours ago by achille225@jlai.lu to c/linux@lemmy.ml

Hello everyone,

I have an issue with my desktop, which I really don't understand.

It is a desktop PC, with a Nvidia GPU, which I use for development (of AI, but like the image analysis part, not the slop part). I usually let it always run, and my previous machine was working fine like this.

However, on this machine, I get crashes after either a few days or a few weeks.

These "crashes" are weird : the machine is still up (and I can ping it), however I can't ssh into it, I can't connect to cockpit either, and can't login physically on it (the display is frozen).

The only way to get it back up is to forcefully shut it down, wait a little and then powr it back up; but this isn't ideal, since it interrupts computations etc

The only crashes shown in journalctl are related to irrelevant (I believe) programs : KDEConnect, DrKronqi, etc; nothing right before the crash.

Do you have any idea what could cause this ?

I tried logging temperatures, but nothing abnormal showed up. I ran memtest86+, nothing showed up either. Smart tells me everything is alright for my drives as well.

Right now I'm thinking about changing the alimentation or the motherboard, but frankly I don't know what's going on and it's really puzzling me.

4
155
submitted 1 day ago* (last edited 1 day ago) by SocialistVibes01@lemmy.ml to c/linux@lemmy.ml

Before we dive into the matter, you first have to understand what DisplayLink is. It is a proprietary graphics transport technology that lets computers connect to one or more external displays over USB, using docks or adapters built around DisplayLink chips.

It works by compressing display data on the host computer and sending it to a chip in the connected device. The chip then decodes it for output to monitors through interfaces such as HDMI or DisplayPort.

On Linux, this support can rub some people the wrong way due to its closed-source nature. That is where Mike Lothian's (FireBurn) Vino comes in as an open alternative.

Unfortunately, Synaptics owns DisplayLink and has sent Mike cease-and-desist letters alleging that he infringed its DisplayLink patents with his project.

What's Vino?

Vino is a driver that lets the Linux kernel talk to DisplayLink docks directly. It is meant to replace DisplayLink's closed-source software and the open source EVDI kernel module that sits beside it.

Mike wrote it with help from Claude Code, and the first version reached the kernel mailing list in June, unfinished. He had faced a communication issue between the dock and the driver and asked other developers for help.

In early July (courtesy of LWN.net), he emailed a Synaptics employee for guidance and mentioned his Rust rewrite of EVDI. About two weeks later, a different employee replied.

That reply said his Rust rewrite of EVDI was not a thing of concern. Rather, the concern was the DisplayLink protocol and codec, which Synaptics believes are covered by its patents. Lawyers get involved

A cease-and-desist letter followed on August 17. It told Mike to stop development and withdraw anything he had submitted to maintainers and hosting sites, with a signed confirmation due by August 28.

An appendix listed over 125 patents without saying which applied. Mike posted a working version 3 of Vino on August 26 and asked Synaptics the next day which claims they had in mind.

The answer came in October as claim charts. They map one claim from each of two patents, GB2484736 and GB2485613, to his source code.

The October 5 letter said Synaptics would seek $25,000 for the cost of preparing those charts if Mike missed an October 11 deadline, with the figure rising by at least $25,000 each week.

Mike replied on October 6 (message 8) with an offer to pause public work on the encoding code the charts point to if Synaptics paused the deadline and the weekly charge. He also asked about licensing that code for non-commercial use.

On October 7, Synaptics said it would grant no patent license or promise not to sue and set October 18 as a final deadline.

 What I can see so far is a very aggressive patent infringement witch hunt against a lone open source developer who was quite open to communication.

 Synaptics took about three weeks to answer his request for specifics, then followed with a potentially life-ruining $25,000 demand that compounds weekly.

Clean room design quirks

Mike describes Vino as a clean-room driver and says he reverse engineered it from captured USB traffic and vendor programs.

If you didn't know, in a clean-room recreation, one party studies the original implementation, then writes a description, and a separate party builds the new code from that description alone.

It is meant to act as a defense against copyright claims because it shows nothing was copied. Synaptics’ July reply argues that clean-room or independently written code can still infringe a patent.

The timing

Vino also lands in a busy stretch for AI-assisted reverse engineering, from smart TV cleanups to office suite clones. Legal pressure has reached other AI-built projects too.

Mike has already taken down the Vino repository in response to the demands, and Synaptics has not made a public statement so far.

Only time will tell what happens to the work, and I hope someone forked it before it went offline, as that would give others a good starting point to build on.

5
190

cross-posted from: https://reddthat.com/post/76421889

Linux doesn't deserve this

Imagine taking the lightweight, privacy-focused appeal of Linux and completely ruining it by hardwiring AI models straight into the OS. Nobody is switching from Windows for more forced AI features.

6
14

Exfatprogs (exFAT Progs) 1.4.4, exFAT filesystem userspace utilities for Linux, has been released today with several improvements, a new feature, and multiple bug fixes.

Exfatprogs 1.4.4 is the fourth minor update in the Exfatprogs 1.4 series, coming three months after Exfatprogs 1.4.3. This release introduces a new feature to the exfatprogs command, namely optional I/O statistics collection for profiling read, write, discard, zero-out, and sync operations.

This release also updates mkfs.exfat to increase full-format speed by using BLKZEROOUT when supported, selecting larger zeroing batches, and improving quiet and trace progress output, and reducing page-cache pollution during full formatting on systems that support POSIX_FADV_NOREUSE.

Several bugs were fixed in Exfatprogs 1.4.4 for the mkfs.exfat command, avoiding memory-reservation failures when creating very large allocation bitmaps, and marking the percentage of used clusters as unknown until it is calculated.

The fsck.exfat command received the most attention, with fixes to prevent arithmetic overflows and out-of-bounds reads by rejecting malformed boot sector geometry, avoid printing version information during automatic repair with the “-p” or “-a” arguments, and missing line breaks in error messages.

In addition, the fsck.exfat command now stops immediately on I/O errors instead of treating them as file system inconsistencies. The dump.exfat command was updated to print complete file timestamps in raw and ISO formats, while the exfat2img command now keeps metadata image output on stdout free of status messages.

Last but not least, the exfatprogs command received fixes for parsing kernel versions and boolean environment variables, and showing the correct usage text for overwrite and read-back verification options.

Check out the release notes on the project’s GitHub page for more details about the changes included in exFAT Progs 1.4.4, from where you can download the source tarball if you want to compile it on your Linux distro. However, it is recommended to install Exfatprogs from your distro’s stable repositories.

Exfatprogs was designed as official userspace utilities that contain all of the standard utilities for creating, fixing, and debugging exFAT filesystems in Linux distributions. The goal of the exfatprogs project is to provide Linux users with the same high performance and quality as the exFAT utilities in Windows.

7
21
submitted 1 day ago* (last edited 10 hours ago) by banazir@lemmy.ml to c/linux@lemmy.ml

Hello. This is a long shot, but I installed openSUSE Slowroll over Tumbleweed yesterday and everything went great. However, now I'm no longer able to create new bottles with Bottles. Bottles is installed from Flathub. Any way I try to create a new bottle it immediately fails with:

(ERROR) Failed to initialize the Wine prefix. Command exited with status 1.

I tried downgrading Bottles and the results were much the same with the versions I tried, except the error message was:

(ERROR) Wine prefix initialization failed.

This is frustrating because there's not much to go on. The process does create some folders on the SSD I'm using for my bottles, so I don't think it's a permission issue. I have used Flatseal to give proper access. The default bottle folder has the same result anyway. I never had this issue on my previous installation and Bottles worked fine.

Bottles issue tracker has the bug #4919 which I assume is the same problem I have, except I'm completely unable to create a bottle no matter which settings I try.

If anyone has any ideas I could try it would be welcome. I'd prefer using Bottles for my Wine needs.

EDIT: I have solved this issue for now. The problem is apparently related to SELinux on openSUSE. Installing selinux-policy-targeted-gaming with zypper lets me at least create bottles. Thanks for your comments!

8
15
submitted 1 day ago by yuman@programming.dev to c/linux@lemmy.ml

so I create a combined sink from two audio devices, my HDMI (DP actually) monitor with OK speakers and the analog stereo audio out, which got a subwoofer attached, without satellites. pactl load-module module-combine-sink, this works swimmingly, sound is awesome, I can set exact audio levels for each output, no notes.

problem is, I'm listening to an internet audio stream via Rhythmbox (tried mp3s off a network share, same deal) and when there's heavy CPU activity, the sound slows down, goes oooOOooOooOOoo like if you remember audio tapes from the olden days that got stretched/deformed. this only happens with the combined sink, if it's just HDMI audio, no issues.

used to happen infrequently, only when launching games or android studio doing compiling but nowadays with every other site having some cloudflare/anubis-like CPU torture, it's getting really tired, really fast.

tried looking at htop, pw-top, following the journal but nothing of substance is observable; possibly because this lasts for a second or so and those tools ain't exactly real-time.

maybe the issue is the devices being 48 KHz whilst the stream is 44.1 and there's some resampling happening? tried looking at pipewire/wireplumber documentation but that stuff is way above my head; "quantums", wtf?!

so is there some priority I can elevate or something so that this audio stack doesn't get compromised? I don't wanna give up the setup nor Rhythmbox.

Fedora, Plasma, Wayland, i5-4670, RX 580.

9
309

Linux memory management expert Lorenzo Stoakes at Arm who has been contributing to the kernel since 2014 is stepping away from some reviewership roles within the Linux kernel due to all of the noise from the flood of kernel patches resulting fro AI/LLMs.

Lorenzo announced today he is stepping away as a reviewer for the memory management (MM), core, misc, and Rust areas due to all the noise caused by AI. Lorenzo will continue serving as maintainer for areas of the kernel he oversees but is looking to lighten his load due to the increased patch burden in 2026.

Lorenzo commented in the patch series removing himself as reviewer for those areas of the kernel:

"Given the current throughput in the kernel resulting from AI-generated series, I unfortunately lack the bandwidth to generally be able to offer review except in those areas I maintain.

I have separated the patches into areas maintained by David, Andrew, and Alice + Danilo, so each can take the patches relevant to the subsystems, for convenience.

Apologies for doing this, but given the current trends I'd like to do something to make my inbox a little more manageable :)"

Lorenzo has been a longtime contributor to the Linux memory management code and also author of the book The Linux Memory Manager.

10
50

Linux Mint is an Ubuntu-based distribution equipped with its own desktop environment and a set of XApp tools that make it a truly unique package that caters to both beginners and power users alike.

For years it followed a familiar rhythm of new releases roughly every six months, with girls' names being used in alphabetical order from Ada in 2006 to Zena in 22.3 for naming individual releases.

That flow has since shifted as the developers settle on a longer development cycle, which sees them move to one major release per year with no point releases in between.

Version numbering and naming also change with this, as the number now points to the year ahead, taking users from 27 to 28 to 29, and boys' names take over from the girls' names.

Linux Mint 27 "Adrien" is the first release under this new strategy. It is planned for Christmas, builds on Ubuntu 26.04 LTS and comes with a five-year support period.

So, with this feature rundown, we are following the monthly news posts since January and are sticking to changes that are new in Linux Mint 27.

Everything below is a preview of the anticipated changes. These can still shift before the stable release.

  1. Wayland is Here

Cinnamon's Wayland session is no longer experimental. Both X11 and Wayland are fully supported in the next Cinnamon release, with Wayland nearly level with X11. This makes the flagship experience of Linux Mint Wayland-ready, bringing it up to the level of other mainstream distros like Fedora and Ubuntu.

Much of the groundwork revolves around everyday interactions. Windows and menus map properly, focus stealing is prevented, and crashes across Cinnamon, Muffin, cinnamon-session, and Xwayland are fixed.

Multi-monitor setups and KVM switches are covered too.

Graphics get attention as well. Hardware acceleration is supported, including GBM over EGL for NVIDIA cards, while HiDPI scaling reaches cursors and Chromium-based apps such as Slack and VS Code.

The final gap in ensuring Wayland support was the screensaver.

The new one is rendered by the compositor and handled by Cinnamon itself in place of a separate cinnamon-screensaver process, and it works on both Wayland and X11. The old screensaver stays as a fallback for one release before it goes away.

  1. Desktop Upgrades

Nemo Changes

The default file manager, Nemo, gets a preview pane that can be opened with F7 or from the status bar. It handles audio files, pictures, and videos and can show metadata details such as the capture date and the camera used.

Similarly, Interactive Search, the feature that kicks in when you open a folder and start typing, becomes a filtered view that narrows the list as you type, in place of jumping to the first match and leaving you to navigate through the rest.

Screenshot Tool

A dedicated screenshot tool arrives for Cinnamon. It can capture a window with or without its shadow, and it can capture all monitors or just one.

You can also crop a shot before copying or saving it, and the tool deals with shadows differently for windows that draw their own titlebars and windows that rely on the system's.

Library Redesign

The Library is how the XApp app Thingy appears on the desktop, and it gets a redesign that groups recent documents by type instead of by the application that opened them.

A sidebar holds predefined groups that you can show, hide, and reorder. You can also add custom groups based on file type and limit them to a single directory if you like. Single items can be removed, and the whole recent documents list can be cleared at once.

  1. System and Installer Changes

A Common Installer

Linux Mint switches to the live installer that Linux Mint Debian Edition (LMDE) already uses, replacing Ubiquity. The new installer handles OEM installs, BIOS and EFI systems, Secure Boot, and LVM and LUKS setups.

Hibernation Returns

After Ubuntu dropped it, hibernation has made a comeback in Linux Mint 27 through a new "Sleep Modes" page in the System Administration tool that makes it easy to set up again.

Though it still needs a large swap to work.

That page also adds two more options. Hybrid Sleep suspends the machine while also writing the session to disk, and Suspend-then-Hibernate starts out as a normal suspend before it hibernates once the battery reaches a critical level.

Kernel Management

This has moved out of the Update Manager and into the System Administration tool on both Mint and LMDE, and it is built around kernel series.

You track a series, choose how many older kernels to keep, and let a weekly cleanup remove the rest, or run a manual cleanup whenever you like, while a History page keeps a record of what happened.

Custom, OEM, and Real-Time are some of the kernel series' that can be marked as tracked, while untracked series are removed at the next cleanup round unless their kernels are exempted.

User Settings

Account settings also move into the System Administration tool, with it taking over the handling of users and their account details. That includes home directory encryption at account creation, webcam selfies with a mirror option, and HiDPI avatars.

  1. Core App Additions

Superlight

Superlight is the new system monitor. Its graphs track CPU load, memory and swap use, GPU, network traffic, disk activity, temperatures, and fan speed, while a dedicated "Battery" page shows status and charge history.

An app page and a process list sit alongside them. Columns are configurable and sortable, and the choices are carried across sessions. The "Storage" page shows a usage breakdown and gives quick access to options like emptying the trash, clearing the cache, and accessing the file system.

Velocitty

The new default terminal for Linux Mint, called Velocitty, offers a tab overview in the style of Ghostty and Ptyxis, color palettes, and tabs that can be reordered, moved, and detached.

Paths can be shortened, and tab colors can flag root sessions, remote sessions, and running processes. Custom tabs can also be assigned a name, color, or command.

Xepub

If you prefer reading EPUB books, then you will love this one. Linux Mint 27 offers a dedicated app called Xepub that supports chapter navigation, search, bookmarks, and zoom.

You also get a choice of fonts, and it remembers where you stopped reading.

Selecting a word opens a menu that can be used to search the dictionary, Wikipedia, or a translator, and the search engine to be used is configurable.

Calendar and Clocks

Calendar is a new app from the Clockenstein project, and it connects to local calendars, Google Calendar, and CalDAV servers like Nextcloud. You can use it to create and edit events, and any sync errors on remote calendars are shown, with unreachable ones turning read-only.

Reminders can be dismissed or snoozed, and a separate daemon and notification agent deliver them while the app is not running, with the Cinnamon clock applet being compatible with those to keep events visible in the panel.

Clocks is the part that was still under development when we last heard about it. The September update previews it as an Android-inspired alarm app from the same project, with recurring alarms and custom sounds.

Unfold

Handling archives gets simpler with Unfold, a very portable archive manager that lets you view, create, and extract archives while using 7zip and 7zip-RAR to do the actual work behind the scenes.

Encrypted and password-protected archives are supported as well, and the app is released under GPLv3+.

  1. Misc Changes

Before we wrap up, here are a few smaller changes that could be of interest to you:

WPA3 and OWE support in Cinnamon.

Fingerprint login in Slick Greeter without needing to press Enter.

A new "Sensors" page in System Reports with fan speeds and temperatures that refresh automatically.

A Mint-Y refresh with better dark colors and contrast, plus rounded frames, scrolled areas, treeviews, and listviews.

Can't Wait to Get Started?

Well, you will have to wait, oops. Linux Mint 27 is supposed to drop sometime around December 24 on Christmas Eve and will be offered in three officially supported variants:

Cinnamon (the flagship)

MATE

Xfce

Seeing that this article has gone live before the release is available, the download portal linked above only features the earlier releases of Linux Mint. Though, if you have the skills, you could build the release from source.

11
34
submitted 2 days ago* (last edited 2 days ago) by Orwi@programming.dev to c/linux@lemmy.ml
12
407

Well, well, well...

Asahi Linux is the reason you can run Linux on an Apple Silicon Mac today. For years, the project put most of its own code under the MIT license so that anyone, including the BSDs, could reuse it as needed.

That is changing because Asahi Linux is tired of code laundering. They have announced that Asahi is moving all of its repositories to the GNU General Public License version 2 or later. Going forward, all Asahi Linux code will be under strong copyleft licenses only.

This is because people were taking in-development code straight out of their personal forks, publishing it without credit, or rewriting it with AI to hide its origin for "replacing the project and aggressively monetising Linux on Apple Silicon."

What is code laundering?

Code laundering (also called license laundering) is the practice of taking someone else's code and passing it through a process that hides where it came from, so you can use it without honoring the original license or crediting the author.

Before AI, this usually meant manually rewriting code line by line, renaming variables and stuff, and shuffling functions around until it no longer looked like the original.

LLMs made it much more easy and cheaper of course.

The MIT license only asks you to keep the original copyright notice. It doesn't require you to share your changes or keep your version open. That's what makes it popular, and it's also what made things problematic for Asahi here.

Learning from history

The move has come after the Asahi team was made aware "some time ago" of multiple attempts to exploit its permissive licensing to hijack its work.

In the most extreme cases, feature code that was still under development was lifted from developers' personal forks before it was even publicly released. The report points out that the MIT license "explicitly allows this, and has no carveouts to protect against bad faith actors."

Asahi didn't name anyone in the report. It also didn't spell out how existing contributions will be relicensed or whether every past contributor agreed to it.

Asahi draws parallels with WINE's situation two decades ago. WINE, the compatibility layer that lets you run Windows apps on Linux, was originally MIT-licensed too. But in the late 90s and early 2000s, companies took the code, built proprietary forks on top of it, and sold them commercially. So, in 2002, the WINE team relicensed to the LGPL to discourage proprietary forks and push companies to contribute upstream.

Those who do not learn from history are doomed to repeat it

Asahi has been upset lately

Asahi didn't name anyone so we are left with guesswork on who they are targeting with this license move.

There have been at least two public forks of Asahi's work in recent months, both tied to AI-assisted development. In case you did not know, Asahi Linux forbids AI generated code contribution.

The first is Aurora Silicon and its Vulkan driver, Borealis. Borealis is a fork of Asahi's HoneyKrisp, the Vulkan driver for Apple GPUs. Aurora Silicon submitted a pull request to register its own Vulkan driver ID with Khronos (VK_DRIVER_ID_AURORA_BOREALIS), says the driver runs on M1 to M5 and the A18 Pro, and keeps it in its own Mesa fork rather than upstream.

The second is Gravity Linux, a Fedora-based distro for Apple Silicon. It was forked from Asahi over the disagreement about LLM use.

To be fair to Gravity, it is open source, it isn't selling anything, and it credits its AI use openly. It even says it plans to sunset the distro once its driver work lands upstream.

It isn't the kind of bad actor the progress report describes. But it does represent the "permissive fork that embraces AI" approach that Asahi has consistently pushed back against.

For clarification, Asahi's progress report does not mention Aurora Silicon or Gravity Linux by name. I have provided their conflict with Asahi as context.

Why this license change matters

As far as I can tell, this is the first time a major open source project has moved to copyleft specifically because of AI-assisted code laundering. Projects have relicensed before, but usually to stop cloud providers from reselling their work as a service. This one is specifically about AI.

I wouldn't be surprised if more hardware enablement and reverse-engineering projects follow. Making the first changes takes a lot of time and effort but they are easier to "rewrite" once someone has done the hard part.

Will the GPL actually help?

If the problem is people who already ignore the MIT license, why would they respect the GPL? After all, GPL cannot stop a determined bad actor. Nothing does, actually.

Stripping attribution from MIT code already breaks the MIT license, since keeping the copyright notice is its one real condition.

What the GPL changes is the commercial benefit. Under MIT, someone can take Asahi's code, close it up, and sell a product, and that's perfectly legal as long as the notice stays in.

Under the GPL, anyone who distributes a modified version has to release the source under the same license. You can't legally build a closed, paid Apple Silicon distro on top of GPL code. And if a product's source has to be public, the copying is easier to spot. Not everyone is happy

The move has drawn criticism, particularly from the BSD side, which was one of the main reasons Asahi chose MIT in the first place. OpenBSD's Apple Silicon support relies on Asahi's m1n1 bootloader.

OpenBSD developer Bryan Steele wrote on X:

"Sad to see Asahi out there burning bridges for no reason.. relicensing m1n1 and drivers under GPL2-or-later, seemingly without the consent of all prior contributors, under the guise of "defending against AI bad actors", seems entirely disingenuous and misguided."

Wrapping up

Asahi is betting that copyleft license provides a better defense in this changed world where anyone can launder code with a prompt.

It may not stop the bad actors from rewriting its code, but at least it reduces the chances of a closed commercial fork.

It would be interesting to see whether the BSD community finds a way to keep working with Asahi under the new terms.

13
79

Hackers are actively exploiting a recently discovered critical vulnerability that allows them to log in to privileged accounts on many Linux systems, multiple researchers are reporting.

The vulnerability, tracked under the name *sshole, arises from the interaction between OpenSSH and a code library known as musl. Linux systems that use both of these packages and meet certain other requirements can be hacked to give unauthenticated access to high-privilege accounts in a matter of seconds. *sshole became publicly known last Thursday and quickly stoked concerns it could lead to widespread compromise of Linux machines. Four days later, the prediction shows signs of becoming real. Attackers conducting “mature intrusions”

Security firm Greynoise said Monday that honeypots it maintains in Southeast Asia have come under attack by a group it’s tracking as GT10. The group conducted “mature intrusions” into the systems, which Greynoise uses to detect attempted or successful attacks in real time. Greynoise subsequently gained access to a GT10 server that revealed potential other victims and some of the tools used in the campaign. A backdoor the group is using in the attacks contains Chinese language comments and appears to be generated with the use of AI.

Greynoise said that GT10 is also installing the Python3 release on machines that don’t already have it because the package is required to run the hacker’s backdoor, which is tracked under the name TAC Agent. TAC Agent supports a wide range of functions, including shell commands, system reconnaissance, and persistence. OpenSSH has released a fix that prevents attacks from working.

Researchers at security firm watchTowr said Friday that they, too, were seeing exploitation activity, which was related to botnets and cryptocurrency. Security firm Previdian has also reported similar activity. It said its company’s sensors have seen 20 exploitation attempts from 13 unique attacker IP addresses geolocated to nine countries.

The vulnerability, tracked as CVE-2026-123158, resides in OpenSSH, when it runs alongside musl, a Linux alternative to the widely used libc code library. Further, OpenSSH must not use PAM (pluggable authentication modules), a framework that handles user authentication and account access checks. Additionally, SSH configurations must (1) have at least one account that’s accessible using a password that is hashed using the SHA256 or SHA512 function and (2) also be set to use passwordless accounts by way of specifying a “*” in the password field in the /etc/shadow file. Passwordless configurations are standard for certain types of accounts.

Exploits are triggered when an attacker enters passwords with more than 256 characters for a passwordless account. This step occurs when the OpenSSH server hashes the supplied password and checks it against the hash stored in /etc/shadow. The oversized password produces an error that causes musl’s password hashing function to return “*”. The attacks exploit the “misinterpretation of whether a string is intended to be a password hash,” Red Hat said.

Despite the multiple conditions necessary, CVE-2026-123158 poses a serious threat to a large base of machines, most notably those running Alpine, a lightweight distribution of Linux. The ease of exploitation allows hackers to direct malicious commands to any of the millions of SSH servers exposed to the Internet and identify potentially vulnerable ones in seconds. Anyone using OpenSSH should install the update promptly. Those using musl should investigate further.

14
15
submitted 2 days ago by sandayle@lemmy.ml to c/linux@lemmy.ml

I use Arch Linux. When I connect an external monitor to my ThinkPad, the cursor moves erratically on the touchpad. It moves slowly, stutters, doesn’t go where I want it to, or goes past the target. There’s no problem with the mouse. The touchpad doesn’t always cause problems—it happens sometimes, and it’s very frustrating.

15
328
submitted 3 days ago by 1121219165@lemmy.zip to c/linux@lemmy.ml

I’ve been doing the OverTheWire Bandit over the past couple of days and have become stuck on the earlier levels. I deem this very embarrassing as this is supposed to be an “easy” and “recommended for beginners” type of puzzle that requires hands on understanding of the Linux terminal. But I have been using Linux for 9 months now, I wouldn’t do the most complicated things (other than break my whole os) only the things required to make my overall user experience somewhat enjoyable. Now this makes me very sad to come to the conclusions that I may be below the average Linux beginner which I didn’t know was possible according to my knowledge. I am only asking of tips and tricks to these puzzles and maybe to positive reinforcement to make feel better about myself. Now I will not tolerate spoilers as in the official rules of OverTheWire clearly states, and I hope you will follow this rule for the better sake of my learning and understanding of the Linux terminal ( and for the sake of the game itself)

16
-4

The Deepin team has just released Deepin 25.3, the latest version of their China-developed, immutable Debian-based Linux distro. One of the most useful changes is a new freeze-protection mechanism that keeps core desktop components accessible if the system becomes extremely unresponsive.

In other words, under heavy load, you should still be able to get to the taskbar, the app launcher, and the System Monitor to see what’s going on and kill off the offending processes.

The devs have also been working on application startup performance, particularly the Control Center and the various office apps. System logs are now capped at 5GB by default and will automatically stop logging when disk space falls below 5% to prevent them from getting out of hand.

On the kernel side, Deepin 25.3 upgrades the default Linux kernel to 6.6.159, with fixes for several security vulnerabilities and boot issues on certain devices. For users with more modern hardware, 6.18.56 is available via Kernel Manager.

UOS AI, Deepin’s own AI assistant, can now create reminders, scheduled tasks, and recurring tasks from natural language. Moreover, it now has a whole-disk knowledge base so you can search the contents of authorized local files. There’s also a unified interface that brings MCP, Skills, and the various AI agents together.

Regarding system recovery, the immutable system in Deepin now allows snapshots to be stored on local disk, USB stick, and external HDD, with the ability to restore directly from a snapshot stored at a given location. The backup and rollback process has also been tweaked to reduce the amount of additional disk space consumed during an upgrade.

For the desktop, the update brings several fixes to Treeland (Deepin’s Wayland compositor), including Xwayland compatibility issues, incorrect window rendering when maximizing or going into fullscreen, and input method issues. The login screen has also been tweaked to ensure the controls are readable on light wallpapers.

On the Graphics support side, the NVIDIA Container Toolkit is now preinstalled to enable GPU acceleration for Linyaps containerized applications. The installer will also be able to automatically pick an appropriate NVIDIA driver version based on the graphics hardware that it detects.

Several bundled apps have received improvements as well. Image Viewer now supports cropping, rotation, annotations, mosaics, and blurring all within the viewer itself. Document Viewer now remembers your last position and layout, and Text Editor now has Markdown support.

On top of that, File Manager has an expandable directory tree in the sidebar, Calendar now supports third-party schedules, and App Store has proxy configuration options as well as more accessible installation error information.

Finally, Deepin 25.3 fixes several security issues in various components (Qt, curl, FFmpeg, glibc, OpenVPN, BlueZ, Xorg, and nginx), and the team has addressed some command injection, permission validation, and information disclosure issues in various system utilities.

For more details, see the release announcement.

17
81

Say the name "Chromium" out loud in Linux circles, and you will soon see what a mob looks like. Many people don't like how much of the web rests on one engine led by Google, and they prefer to keep it away from their systems.

Now we have Domicile, a new Rust-based Wayland compositor that uses a patched build of Chromium to draw the entire desktop as a web page.

Apps still run natively, and each Wayland window goes straight into Chromium's rendering system and shows up inside that page as an element. A window and a website can then sit side by side and be arranged the same way.

Domicile: Overview

Domicile is not a drop-in desktop like GNOME or KDE Plasma. It leaves the bar, the window layout, and the look to a shell, and that shell itself is a web page you have to write yourself.

Native app windows and websites both sit on that page, and because CSS decides where each one goes, layouts like tiling or floating take only a few lines of styling.

You can even swap the shell without closing a single window because loading a new one resets only the state held in the shell's own page. A single page can span every monitor, and shells are built from packages that anyone can publish on npm, whether it is a whole desktop, a bar, or a launcher.

The compositor still handles the lock screen, tray icons, notifications, and screen sharing, while the shell decides how they look. The built-in browser runs Manifest V3 Chrome extensions, but some of them behave differently than they do in Chrome.

Apps need Wayland support to run. Electron, SDL, and Qt apps start in Wayland mode, but X11-only ones will not run. Xwayland, the compatibility layer that lets X11 apps work on Wayland desktops, is something Domicile does not include.

The project is provided under the MIT license, and the Chromium files it modifies stick to Chromium's licenses. One more thing, and this could be a dealbreaker for some of you, the project is AI-assisted.

Manganese, the element?

Not quite. Manganese is the ready-made shell that comes with Domicile, and it works as a complete tiling desktop out of the box. Its keybindings follow Sway's on the Super key, and you get ten workspaces along with tabs, stacks, splits, floating windows, and a scratchpad.

Websites open as windows too, sitting next to native apps in the same layout, while extensions from the Chrome Web Store show up as buttons in the top bar.

It comes with a Settings app, clipboard history, launcher, screenshots tool, notifications, and a lock screen. Since every part of it is its own package, you can add a new item to the bar or replace the launcher while the rest stays as it is.

Getting started

Packages exist for Fedora, openSUSE, Debian, Ubuntu, and Arch Linux, plus an AUR package for Arch users. For NixOS, or Nix on any distro, you can use the project's flake.

It runs only on x86_64, and the project has no ARM builds.

A monolithic package carries Manganese, the login session, the domicile command, and the React packages that shells build against. After installing, you point a config file at the shell you want, then log out and pick "Domicile" on the login screen.

18
-8

Kirt McMaster founded Playtron in 2022, and the company went on to build GameOS, a Linux-based operating system for gaming PCs. It now goes by KORA Systems Inc. and is launching a new AI-focused desktop operating system.

The OS shares the KORA name, with GameOS living inside it as GameFrame, a dedicated mode for turning the system into a game console. We received a press release regarding this weeks before the launch, so this write-up might be missing some updates.

 A major component of this OS is not open source.

KORA, explained

KORA is a desktop OS developed on a Linux base, with AI models and agents built right into the system. Don't think that it is an app or a layer over another one; it's a standalone offering.

The company says AI workloads on macOS and Windows stay boxed into a single app or tab, with those having no view of the hardware underneath. KORA is built on the idea that AI belongs inside the OS.

The desktop is organized around neural workspaces, where each one keeps a project or client apart from the rest, and the AI only sees the workspace that is open. Files in it also keep their own version history.

Each workspace doubles as a sandbox too. The user sets what files, devices, AI tools, and online services every app and agent can access, while AppArmor enforces it all.

Search in the neural file system works on meaning, so a person or an agent can find a file by what it contains.

Its memory system builds context from the email, contacts, calendar, and cloud files the user connects. Local models run that analysis on the device, and data goes to the cloud only with the user's approval.

How open is it?

Cortex is the engine behind the models, and it spreads AI work over the CPU, GPU, and NPU, then passes some of it to other computers on the network.

Local models run by default, and cloud ones only join when a task needs them. KORA speculates that local models will handle roughly seven in ten of the calls it manages in 2027.

They also say that models from any outside lab can be integrated, and a chat can move from its own agent to Codex or Claude Code with its context intact. A planned SDK would also let third-party apps and agents tap into projects, memory, search, and email.

Sadly, Cortex is not open source. :(

Still, the wider ecosystem is open, and developers will get the same building blocks KORA's own apps use, such as workspaces, file versioning, and collaboration.

You mentioned Qualcomm?

Yes! Qualcomm engineers worked alongside KORA for nearly a year to bring a Linux desktop to the Snapdragon X2 Elite platform.

Though Qualcomm's wider Linux effort for X2 laptops is still early. Its own developer preview targets kernel developers and not end users, and the drivers meant to open the NPU to local AI are still being pushed upstream.

Even so, KORA says the PCs can run a language model with 26 billion parameters locally, with HUMAIN, the Saudi AI company, working with KORA on an enterprise version.

That version is called HUMAIN OS, with the first OEM PCs expected to arrive preloaded with it in 2027, while KORA itself follows later that year.

So, yes, for now, there is no ISO to download in case you got too excited.

Some thoughts

If you look closely, they are going at it differently than Omarchy, which began in June 2025 as a ready-made setup of Arch Linux and Hyprland that has since landed millions in backing for its foundation.

Omarchy's Quattro release lets users pick from several third-party agents, while KORA builds its own agent into the system and lets others plug in their models. They are basically taking different routes to chase the same bet.

Both seem convinced that AI agents are where the desktop market is headed.

19
19
submitted 3 days ago by Well1@lemmy.world to c/linux@lemmy.ml

After evaluating every comment you left me in the last post and testing every OS via virtual machines, I've decided that my first option when dual booting will be CachyOS, leaving Fedora KDE and endeavourOS as the runner ups. Now I'm at the point where I have to actually do the dual boot. I've found some videos and posts where they show how to do it but I haven't managed to find any case like mine, since I want to go from Linux Mint Debian Edition single boot, to LMDE + CachyOS/Fedora/endeavour. I'm doing this post to ask some questions:

  • Being my case pretty specific, is it the process any different than some other builds like Arch + Cachy, Ubuntu + endeavour, etc., or everytime it's the same process whatever are the OS's I install? Do I have to have in mind anything in particular in my case? Any extra tips?
  • Can I dual boot without having to make a total reset of my actual OS to install it again altogether with the secondary OS? Is it less, equally or more safe/efficient?
  • Do you have any guide in general that you find to be good/useful in this matter therefore I can take advantage of?

Please have in mind I'm a total beginner on these things and they still feel pretty overwhelming to me. So, sorry if I ask something dumb and thank you very much in advance!!

20
36

Linus Torvalds just released the second weekly release candidate of Linux 7.4 with some notable bug fixes and other changes routed in past the merge window. It's another big one in the AI era.

This week brought some adjustments to the AMD PerfOpt feature for helping Radeon iGPU performance, fixing faulty BHI mitigation selection for some kernel configurations, a big improvement for FAT32 especially with synchronous mounts, AMDGPU driver fixes for HDMI 2.2 FRL, and numerous fixes for "nasty long standing bugs" in the core memory management code. Plus the usual assortment of bug fixes as well as the seemingly never-ending flow of AI/LLM generated patches and bug reports.

Linux 7.4-rc2 Git tag

Linux creator Linus Torvalds wrote in the 7.4-rc2 announcement:

"Ok, a big -rc2 to go with the largest ever -rc1. But the diffstat looks fairly benign, and is dominated by some automated coccinelle updates that I got for the merge window but left for rc2 because I didn't want to deal with them when I was on the road (and had a hard time finding the motivation to deal with them afterwards too, to be honest).

That said, the scripted updates are largely just one- and two-liners, and they [really] are very straightforward so they "dominate" the diffstat only in the sense that they are very spread out and do add a lot of noise.

When masking that noise out from the diffstat, the shape of it changes - not spread out over thousands of files any more. But it does not look unusual: a third is drivers (gpu, networking and sound account for most of it, but there's a bit of everything), another third is networking and bpf, and the final third is "the rest" (mostly filesystems, mm, arch updates).

And yes, much of this was driven by various AI fixes. I think I'll stop repeating that, and we can just take it for granted. But this time around Alexei claims that on the bpf side at least the fixes are now coming in faster than the new reports, and that sounds lovely if true.

I think most other areas haven't reached that point yet, but it's at least a sign that we _may_ be starting to see the tide starting to turn.

Don't hold your breath, but maybe cross your fingers we'll be getting there in the not entirely distant future.

In the meantime, please keep testing,"

See our Linux 7.4 feature overview for a look at all the changes coming to this kernel aiming for a stable release around the end of December.

21
59
submitted 3 days ago* (last edited 3 days ago) by muusemuuse@sh.itjust.works to c/linux@lemmy.ml

me and fedora have been boxing for a while now and I’m thinking I want to try something else after I finish designing my next home server case for it.

I’m considering NASty https://github.com/nasty-project/nasty as it’s doing pretty much everything out of box I want to do with this next one already, and even though it’s young, it’s build on nixOS, which I consider mature at this point.

But I have no experience with nixOS. It sounds like it’s a less obnoxious form of fedora coreOS. Any opinions?

22
29

The aerynOS team has published its latest unstable stream update, introducing Linux kernel 7.2.15, which marks the final release in the 7.2 series. The team is preparing to move to version 7.3, expected to arrive in the volatile repository soon.

The update also includes Linux LTS 6.18.62, along with newer versions of several system components, including systemd 261.5, LLVM 23.1.5, and glibc 2.44 development snapshots.

On the package management side, Moss now displays help when users enter the older moss install and moss remove commands or their aliases. Boulder and Ent have also been updated to use a new versioning format for packages built from Git commits.

Desktop updates include KDE Gear 26.08.3, Hyprland 0.57.1, Dux suite 2.1 (formerly Dank Material Shell), Waybar 0.16, and Mir 2.31, accompanied by a rebuild of Miracle WM.

KWin receives a fix for crashes involving DisplayLink docking stations when running fullscreen applications. Additional upstream NVIDIA fixes address graphical glitches, flickering, and buffer allocation problems.

COSMIC Player receives missing GStreamer dependencies, restoring audio and video playback. Meanwhile, both Ghostty and Kitty have fixes for Bash shell startup integration.

Other notable package updates include GStreamer 1.28.9, Poppler 26.11, Zed 1.27, Signal Desktop 8.34, and PowerStation 0.9. The Poppler update includes printing fixes, while additional character maps required by Ghostscript have been added.

Moreover, Rsync now includes daemon service units and the rrsync restricted helper. Zulip Desktop also gets a fix for flashing when using dark mode, along with a new application theme selector.

Finally, several new packages have been added to the repositories, including the terminal-based bandwidth monitor bandwhich, the disk usage utility duf, Gitea’s official command-line client, GNU Stow, and openfortivpn.

KDE’s KeepSecret password manager and the JetBrains Mono typeface are also newly available.

For more information, see the announcement.

23
16

Slax developer Tomas Matejicek has announced Slax 2026.11, a new version of the lightweight, portable Linux distribution designed to run from a USB drive. Based on Debian 13 and powered by the Linux kernel 6.12, the release features a redesigned desktop, a built-in AI assistant, Secure Boot support, and a graphical installer, all packed into a 512 MiB ISO image.

The desktop has been overhauled with Alt+Tab window previews, live taskbar thumbnails, and four virtual workspaces. Users can view all workspaces simultaneously with Alt+F3 or switch between them using Ctrl+F1 through F4.

The desktop also supports files and folders, and the taskbar includes keyboard layout switching and volume controls. Application interfaces have been adjusted for a more consistent appearance across older and newer programs.

The application launcher has been improved as well. Optional applications are marked with a download icon, letting users install and launch them from the menu. Traditional package management through APT remains available.

One of the most notable additions is the Slax AI Assistant, which allows users to troubleshoot problems, inspect their systems, and execute commands using natural-language instructions. It helps identify disk space usage, investigate system issues, and perform administrative tasks. The assistant requires an internet connection and user sign-in.

Slax 2026.11 also includes a graphical installer for Windows and Linux. Users can create bootable USB drives or install Slax alongside an existing operating system on supported configurations. Additionally, UEFI Secure Boot is now supported through a signed bootloader and kernel, eliminating the need to disable Secure Boot on compatible machines.

Another improvement concerns persistent sessions. A single USB drive can store multiple named sessions, each retaining its own applications, files, and settings. Users can select a session at startup, duplicate it using F4, or rename it with F6, as these sessions can be carried between computers.

For disk maintenance and recovery, Slax includes a graphical partition manager that supports creating, resizing, and formatting partitions. Additional utilities support LVM, LUKS encryption, and filesystems such as XFS. VirtualBox, VMware, and SPICE integration is also included for virtual machine environments.

However, users depending on Slax’s modular system should note an important change. The distribution now uses OverlayFS instead of AUFS, so the slax activate and slax deactivate commands can no longer dynamically load or unload .sb modules during a running session.

Modules can still be included before boot, while installing software through APT and preserving changes in persistent sessions remain supported.

For more information, see the announcement.

24
13

Even before the Linux v7.4 merge window was over, there were already two pull requests of drm-misc-next material targeting for what will be Linux 7.5. This week already saw the third drm-misc-next pull request of more feature patches targeting this next kernel version.

This week's drm-misc-next pull brings Rockchip RK3568 support to the Rockchip DRM display driver. The RK3568 is a quad-core Arm Cortex-A55 SoC with a Mali-G52 2EE GPU and a small NPU and VPU too. The RK3568 is found in some industrial/embedded PCs, some NAS devices, and single board computers. Nice seeing the continued work on improving mainline kernel support for Rockchip SoCs.

Separately there are also a number of additional display panels now supported by the mainline kernel including the DCLTek 300249 5.5", DLCTek 300248 10.5", Novetake NT37705, xiaomi-lavender, Tianma TL063FVMC43-02, Tianma TL063FVMCA01-00, Tianma TL060FVXS16-00, TXD TXDI600YANPA-43V3, AUO B101UAN01, Truly NT36850 WQHD, Novatek NT36850, Samsung AMS644VK04, Hitachi TX10D07VM0BAA, LG LH400WV3-SD04, and Mingjun MJ070BI30IA2.

AMD Ryzen AI

The AMDXDNA accelerator driver for Ryzen AI NPus meanwhile saw support added for a new 6.0 firmware release, adding NPU3 classic device support, get/set power mode handling for new AIE4 hardware, and other AIE4 enabling like suspend and resume, clock / DPM frequency / resource information queries, AIE4 command submission, and other important additions. Over the course of this year and the past few kernel versions there's been a lot of enablement work around the AIE4 hardware that presumably is the next-gen Ryzen AI NPU to be found with the upcoming Zen 6 based client platforms launching in the new year. Hopefully with Linux 7.5 the AIE4 hardware support will be in good standing.

The full list of drm-misc-next feature patches for the week via this pull request.

25
57
submitted 4 days ago by MonaySimpson@lemmy.ml to c/linux@lemmy.ml

Currently running mint on a 15+ year old HP laptop but I want to update to a 'modern' second hand Thinkpad. The second hand market is just full of different model numbers and I'm not sure how to filter to what I'm after.

I get most tech basics (ram, ssh) but I'm not sure what all the models numbers, generations or processors mean.

Looking for something with a memory card spot, HDMI output and ideally touchscreen.

I don't use it for gaming but have an ultra wide screen high res monitor (possibly 2k cant quite remember) that I'd like to take advantage of.

Larger SSD and 16gb ram wouldn't hurt too but I assume I can upgrade them.

I don't need the Yoga tablet style folding.

view more: next ›

Linux

68712 readers
542 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago
MODERATORS