1
submitted 2 years ago* (last edited 2 years ago) by 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
 
 

Purism is crowdfunding a new version of its Librem 5 Linux smartphone, this one powered by RISC-V rather than Arm.

Librem 5 v2 will use an octa-core SpacemiT K1 RISC-V SoC, replacing the quad-core ARM64 NXP CPU This platform shift will provide much better performance and longer battery life than the existing Librem 5 – and not run as hot in use.

Memory is increased to 8 GB RAM, up from 3 GB in the first-generation handset, and storage leaps to 128 GB from 32 GB.

SD card reading speeds are boosted, and on-board hardware encoding means the Librem 5 v2 can take 13 megapixel photos with and shoot high-definition video for the first time.

The rest of the phone is familiar to the first. The same case design, 5.7-inch (720×1440) display, removable 4,500mAh battery, audio jack and physical kit switches. This is intentional as it will make repairs and upgrades between generations easier.

Wireless connectivity also stays modular, though the v2 handset will ship with an improved 4G modem. A 5G module is planned.

Librem 5 v2 will run PureOS, Purism’s Debian-based operating system using Phosh as its UI.

Librem 5 v2 costs from $1599

“RISC-V is the future, and Librem 5 v2 is the perfect product to bring it to a mainstream audience”, Jonathon Hall, CTO at Purism, says of the launch.

“Freeing us from the control of Big Tech starts with the foundation, and RISC-V’s foundation frees us from the oligarchy. The Librem 5 v2 puts you in control of your data, combining that with the ease of use we expect in the modern era”.

Given that general feedback to the first-gen Librem 5 – beset by delays, price rises and patchy build quality – was mixed best. But, to it credit, Purism is still out there making, selling and supporting the phones (and their other devices and services).

Transitioning to RISC-V for the follow-up won’t be trivial, mind. Graphics acceleration, new drivers and power management (which on a phone is rather critical) will be big undertakings.

And more work is needed to make the day-to-day software stack editable, like browser performance (sluggish on the newest and fastest RISC-V chips) and providing an Arm64 app compatibility layer to run software not made for RISC-V. Available to back until February 2027

If you’ve got at least $1599 burning a hole in your pocket and you don’t need anything to show for it before 2028, you can go pledge to the campaign. It runs until February 2027, so don’t feel pressured to decide just yet.

3
 
 

Some neighbor not being happy with Microslop.

4
 
 

KDE developers are preparing an important change for the upcoming Plasma 6.9 desktop environment, scheduled for release in late February. According to the latest update, XWayland, the compatibility layer that allows X11 applications to run in Wayland sessions, will now start only when needed instead of running continuously in the background.

Until now, Plasma kept XWayland active even when no X11 applications ran. The change means that Plasma’s Wayland session will no longer need to keep XWayland running simply to support applications that users may never launch.

Apart from this improvement, Plasma 6.9 is receiving a redesigned Task Switching page in System Settings. The page was ported to QML, with a refreshed interface that also includes configuration options for the Overview effect.

The Date & Time settings page is also undergoing a similar transition. Its new QML-based interface consolidates controls into a single page, making it quicker to change the system’s time zone.

KDE is also refining desktop customization. The wallpaper configuration page will have more room for browsing images after the desktop layout selector moved to a separate page. Moreover, desktop icons and the Folder View widget will gain additional size options, filling a noticeable gap between the two largest existing sizes.

Regarding performance improvements, Spectacle, KDE’s screenshot utility, will launch faster thanks to optimizations and parallelization. The Add Widgets sidebar has also been optimized to open substantially faster, with smoother animations.

On top of that, the Task Manager will handle window previews more efficiently by avoiding unnecessary thumbnail regeneration when the pointer leaves and returns to a preview, thus eliminating a minor flickering issue. Additionally, when a grouped application requests attention, opening its group popup will now identify the specific window responsible.

On the network management side, users will be able to forget saved connections directly from the Networks widget without opening System Settings. The network share configuration wizard will also automatically recognize more information from pasted URLs, including the protocol and whether encryption is required.

For system monitoring, Plasma 6.9 adds a sensor showing the number of physical CPU cores, available in both the System Monitor application and its widgets.

Other desktop refinements include named presets for the Wobbly Windows effect, fade animations for Spectacle’s screen capture overlay, and more convenient duration editing in the Timer widget. The Keyboard settings page will make it clearer when the system-wide keyboard layout is used rather than a custom configuration.

Finally, if the login via Plasma Login Manager fails, it will provide a basic terminal fallback instead of leaving users with a black screen, allowing them to access the system for troubleshooting.

For more information about the upcoming changes, see KDE’s “This Week in Plasma” blog post.

5
 
 

What happened?

So 2 days ago I was getting back on my family desktop, but I noticed that Windows was slow, like VERY slow. I hear the hardware making decently loud noises all the time

Ok, then it's a great opportunity to switch to Linux!

No! You see, it's a family desktop and it's been there for 10+ years, which means if I install another operating system, 10 years of familiarity will be vanished! Even if I choose a distro with a Windows-like UI, the apps supported there aren't garenteed to be recognized by my parents! Maybe they could tolerate Firefox and mayyyybe Ungoogled Chromium, but that's about it

Ok, did you asked your parents?

I told them I thought about it. My mom doesn't use it for personal stuff at all and my dsd uses it for YouTube, word, excel, etc, so nothing too crazy. OnlyOffice (and LibreOffice from what I heard of) does support Microsoft's file types. I asked them if they could toleratebthe alternative software. My dad said he would think about it. Currently, he said that we don't have a USB with big enough storage space to fit all the data in to backup and restore on the new OS. But my parents are surprisngly open when it comes to my personal discsions. So, hope isn't yet lost

Conclusion and solutions

It's a gray area for now. Idk if my parents could tolerate Linux Mint, but if they could, that's a massive win. If I could figure out how to dual-boot, then it's a possible middle ground. Another possible middle ground is running Windows within Virtual Box for my parents. Best case scenario: The open-source alternatives are good enough for my parents' use cases

Lemmy know about your opinions down in the comments

6
submitted 1 day ago* (last edited 9 hours ago) by to c/linux@lemmy.ml
 
 

I have attempted to install Mint 22.3 on my old laptop (Lenovo Yoga C930) which was previously running Windows 11 and seem to have no operating system present on the laptop now and can not boot from my USB drive.

I started by downloading Mint 22.3 "Zena" on to a USB drive via Rufus, booted into Mint via the BiOS, and attempted to "Erase Disk and Install Linux Mint" by following the prompts. The install process gave some error messages as it proceeded and took significantly longer than the help videos I had watched beforehand suggested. I left it running over night and came back to it still attempting to install in the morning.

I pressed the power button on the laptop to stop it and when I turned it back on was met with a message along the lines of "remove bootable drive". The next message I got was "Default Boot Device Missing or Boot Failed", I hit OK and now there appears to be no OS on the Boot Manager.

When I put the bootable USB back in, the boot manager finds it but when I select it I receive: Failed to open \EFI\BOOT\mmx64.efi - Not Found Failed to load image (blank square): Not Found Failed to start MokManager: Not Found Something has gone seriously wrong: import_mok_state() failed: Not Found

This is my first time attempting to install an operating system so I really am not sure what went wrong or where to go from here, any help would be greatly appreciated.

Edit: successful install! Thank you very much to everyone who took the time to help me out with this :)

7
 
 

Timestamps:

00:00 Intro

01:12 Darling project says they'll use Al to bring mac apps to Linux

04:20 Proton posts article about their security and Al use

06:56 Steam updates brings 64bit and better remote play

08:49 Valve adds framerate data as public info for Deck users

11:21 MATE gets its Wayland compositor

12:55 Long time Linux maintainer steps back due to Al generated patches

14:13 Asahi to switch licenses, and progress report

16:02 Nexus Mods hiring a Linux dev

18:03 Nvidia CEO resigns

19:13 Tuxedo OS nears final beta

21:05 Dolphin gets columns view, again

22:41 GoogleBook OS doesn't seem great

25:32 Sponsor: Tuxedo Computers

Links:

Darling project says they'll use Al to bring mac apps to Linux

https://blog.darlinghq.org/2026/11/08/development-update-q4-2026/

Proton posts article about their security and Al use

https://proton.me/blog/how-proton-keeps-your-data-secure

Steam updates brings 64bit and better remote play

https://store.steampowered.com/news/app/593110/view/678515036155543747

Valve adds framerate data as public info for Deck users

https://store.steampowered.com/news/app/593110/view/685269801333948419

MATE gets its Wayland compositor

https://discourse.ubuntu.com/t/introducing-polo-a-mate-wayland-compositor/91698

Long time Linux maintainer steps back due to Al generated patches

https://www.phoronix.com/news/Lorenzo-Stoakes-AI-Flood

Asahi to switch licences, and progress report

https://asahilinux.org/2026/11/progress-report-7-3/

Nexus Mods hiring a Linux dev

https://www.gamingonlinux.com/2026/11/nexus-mods-hiring-for-a-linux-gaming-specialist-to-work-on-their-vortex-app/

Nvidia CEO resigns

https://nvidianews.nvidia.com/news/nvidia-announces-ceo-transition

Tuxedo OS nears final beta

https://linuxiac.com/tuxedo-os-enters-final-beta-testing-ahead-of-debian-based-release/

Dolphin gets columns view, again

https://blogs.kde.org/2026/11/08/dolphin-gets-a-columns-view-again/

GoogleBook OS doesn't seem great

https://www.androidcentral.com/chromebooks-laptops/lenovo-googlebook-15-review-google-botched-it-yet-again

8
 
 

cross-posted from: https://lemmy.world/post/54392985

I figure this could also be a place for discussing what are some things you'd like to see in Plasma Mobile? Frankly, hoping to organize ideas to formulate possible work items or goals to suggest to KDE.

9
A joke... (lemmy.ca)
submitted 1 day ago* by to c/linux@lemmy.ml
 
 

When I feel like scrapping the whole project and starting over:

Me: (in the project dir) sudo rm -rf /*
Me: (after waiting a while) Something feels off… Why is it taking so long to delete everything?
Me: (suddenly realizing) ^C ^C ^C
System: Press any key to continue...

当我想把整个项目推倒重做时:
我:(在项目目录)sudo rm -rf /*
我:(等了一会儿)有点不对劲。。。怎么删了这么长时间还没删完
我:(恍然大悟)^C ^C ^C
系统: Press any key to continue...

10
11
 
 

I'm noob at Linux (it just works), so I have no idea how to start troubleshooting this weird issue, any help appreciated!

The setup: stock EndeavourOS, ProtonVPN, qBitTorrent bound to the VPN interface (and Transmission);

the issue: if qBit is running, no matter the load or the server (I have access to P2P-enabled servers), it kills my VPN connection in a matter of minutes, Transmission does not. It is reproducible, launching qBit means getting disconnected, without fail;

the timeline: no issues since I installed EndeavourOS (a year and a half or so), it started happening five to seven days ago, though since a few months ago I would get the same disconnection while qBitting, but only once a day and only while I was away and the system was locked, after I came back to it and reconnect, stable until shutdown. In the months between I haven't made any changes to my system, just got a new GPU a year ago;

what I tried: I initially though it was a VPN app problem, so I tried reinstalling it, both native and flatpak, after deleting all of its data of course.

Transmission works but I prefer qBit so I'd love to go back to using it.

Where do I start troubleshooting?

I currently can't be at my PC, so I can't troubleshoot "live", but I figured posting this early means more people seeing it and getting more input.

Thanks in advance!

ip link (VPN, no qBit): https://pastebin.com/RtwDqiEN

ip link (VPN, qBit): same identical output (verified with Kate, EndeavourOS text file reader)

journalctl qbit: https://pastebin.com/e2XCgGKy

journalctl PVPN: https://pastebin.com/DiPBvP5W

dmesg: empty for both "torrent" and "proton"

sudo dmesg -l err: virt/tdx: TDX not supported by the host platform

FINGERS CROSSED but it seems that lowering max connections DID fix it, though I'm currently on 20/10/5/4 and it's limiting. I'll try upping and see where it lands on, and hopefully that'll be it.

As per this comment

https://leminal.space/post/41934365/26536143

Proton must have changed something on their end since I used to run qBit with 500 max connections up until the problem started

12
 
 

From 10 November, you can enable the free VPN in Firefox and browse as much as you like, for as long as you like, without needing to worry about reaching the fixed monthly limit.

‘Whether you’re heading home to see family this winter or taking a well-earned break before the year wraps up, we want you to browse with a little more peace of mind’, Mozilla’s LLM-aided blog screed insincerely enthuses.

Mozilla ran a similar promotion in June (when it also temporarily bumped the number of server locations to proxy browsing traffic through to a generous 28). On 1 February 2027, Firefox VPN snaps back to a 50GB monthly data limit.

Making use of the free VPN does require that you sign in with a Mozilla account (that only costs the price of an email address). Per-site exceptions can be set, so that visiting certain websites won’t use a VPN. It also works in private mode.

But Firefox VPN is not a regular VPN. It only masks your activity inside of the browser. To obscure connections from other apps, desktop services, and so on you need a proper VPN – Mozilla happens to sell one, Mozilla VPN.

Unlimited data means you can flip the VPN on for one of the available locations and not worry too much about what you get up to on data-heavy sites like YouTube – set and forget, ahoy (well, until you’re bored of search results in German).

13
 
 

Libreboot, the free and open-source boot firmware project that replaces proprietary BIOS and UEFI firmware on supported hardware, has released version 26.11, transitioning to full UEFI support through the MrChromebox EDK2 payload, which also makes it compatible with Microsoft Windows.

With this release, nearly all supported boards now ship exclusively with EDK2 firmware. The project removed GRUB as a coreboot payload, along with the previously included MemTest86plus and CSMWrap payloads, simplifying firmware configuration and reducing maintenance.

However, this change comes with an important warning for existing users. Systems configured to boot in legacy BIOS mode must be migrated to UEFI, including setting up a proper EFI System Partition, before installing the new firmware. Otherwise, existing operating system installations may no longer boot.

Legacy booting is still possible, but users must add the required components themselves when compiling Libreboot. The build system now supports inserting GRUB EFI, MemTest86plus, and ReBIOS through its efi/ directory.

On the hardware side, Libreboot 26.11 enables TPM 2.0 by default on several systems, including the ThinkPad X270, X280, T480, T480s, and T580, along with the Supermicro X11SSH-F and Topton X2E N150. TPM support was previously disabled due to problems with SeaBIOS, which no longer occur with EDK2.

Dell Latitude laptops also receive fixes for fan control, battery status reporting, and lid-switch handling during suspend. These improvements use an updated ACPI implementation replacing older SMM-based patches. Furthermore, SD card reader functionality has been restored on the ThinkPad W541 and Dell Latitude E7240 through an EDK2 patch.

For Chromebook users, the release restores configurations matching upstream MrChromebox after changes in Libreboot 26.10 caused boot failures on some systems. The Dell OptiPlex 780 also switches to EDK2, while the OptiPlex 5050 SFF gains SATA hotplug support and a fix for PCIe error reporting related to certain wireless cards.

A security-related EDK2 fix addresses an ICMP packet bounds-checking vulnerability in its PXE implementation. According to the developers, Libreboot was not affected because its configurations use iPXE instead, but the patch has been incorporated into the distributed source code.

Finally, the release simplifies several aspects of Libreboot’s build system, including firmware payload configuration, source handling, and ROM naming. Custom firmware images now use clearer BIOS and UEFI prefixes. Improvements to the lbmk build utility make it easier to insert additional EFI payloads and work with older firmware images.

For more information, see the release announcement.

14
 
 

Agent Name Service (ANS) now has a home at the Linux Foundation. The launch happened at KubeCon North America in Salt Lake City, and you might remember that the foundation first announced its plans for the project way back in June.

GoDaddy, Cloudflare, Salesforce, and DigiCert are among the organizations now involved with ANS, bringing the total number up to eleven.

One of the early deployments of ANS has been in AGNTCY, another project under the foundation, where its directory of AI agents can now check an agent’s ANS identity.

Announcing the move, Jim Zemlin, CEO of the Linux Foundation, had this to share:

Autonomous AI agents are transacting and operating across global systems, but they can't succeed without verifiable identity.

Under the neutral governance of the Linux Foundation, ANS provides a common foundation for trust that the entire industry can adopt, implement and improve together.

An explainer

Platforms identify AI agents in their own ways, and a service that receives a request from one has no standardized way to confirm who the agent represents.

ANS tackles this by linking each agent to a domain name its operator owns, the same way a website is tied to its domain. Each version of an agent gets its own name, such as ans://v1.4.2.travel.example.com.

To register an agent, the operator first has to prove it controls that domain. Certificates are then issued for the agent, and every registration goes into a public log that anyone can read.

ANS also publishes details about each agent in DNS, the internet's address book, and other systems can then look them up with tools they already use.

The main DNS records use a format from a separate project called DNS-AID. ANS adds one record of its own that points to the agent's entry in the public log.

When an agent sends a request, the receiving system can check that its registration exists, that it has not been revoked, and that the agent really holds the key tied to it.

ANS only covers who the agent is. Deciding what it can do is left to the receiving system, and platforms have to add the check themselves.

The setup behind ANS

A technical steering committee now oversees the project. It starts with five seats, held by three people from GoDaddy, Ken Huang of DistributedApps.ai, and Michael Kantor of Hashgraph Online (HOL).

That lineup is only a starting point. The first election has to be held within 12 months, and after it, the charter prevents any one company from holding half or more of the seats (to ensure vendor neutrality, I assume).

The charter also mentions that meetings are meant to be open to the public and that discussions and decisions should be visible to everyone.

As for all the code in the project, the Go, Rust, and Java libraries currently use the MIT license, but new code contributed from now on has to use the Apache 2.0 license.

Some lore info

ANS began in 2025 as a draft sent to the IETF, the internet standards body, and a follow-up came in October. Drafts like these have no formal standing at the IETF and are not endorsed by it.

At present, the Linux Foundation calls the specification formalized. The reference code and a local demo are on the project's GitHub page, and the specifications are on ansinfo.ai.

15
 
 

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.

A screenshot of plasma desktop with no widgets appearing in the list
16
 
 

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.

17
 
 

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.

18
 
 

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.

19
 
 

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.

20
submitted 4 days ago* (last edited 3 days ago) by 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!

21
 
 

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.

22
 
 

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.

23
 
 

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.

24
 
 

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)

25
 
 

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.

view more: next ›