1
59

Original question by @POTOOOOOOOO@reddthat.com

2
24

3
18
submitted 23 hours ago by cm0002@infosec.pub to c/linux@programming.dev

We soon will have a /slop dir in distros.

A Fixes tag in a kernel patch points to the commit that introduced the bug, but the last commit to touch a buggy line may only have moved the code to a new file.

Sasha Levin, who co-maintains the stable and long-term support kernel trees, wants AI coding assistants to verify which commit introduced a bug before assigning it a Fixes: tag.

His two-patch series went to the workflows and ksummit mailing lists last week, where he has proposed a new agents directory in the kernel tree to hold the skill that does it.

The first patch adds an agents/ directory at the top of the kernel source tree for skills, prompts, and other resources meant for coding assistants. It also adds a MAINTAINERS entry covering the directory.

Each skill gets its own folder under agents/skills/, with a SKILL.md file as its entry point, written in the Agent Skills format.

Assistants are told to read a resource directly from its path in the repository, and links inside a skill are relative to that skill's folder. A new section in the kernel's coding assistants document is meant to describe this layout.

The find-fixes skill, which arrives with the second patch, would be the first one in the directory.

Why do Fixes tags go wrong?

Levin says the series traces back to a question from Ted Ts'o about incorrect tags in stable tree work. He pointed to LLM workflows that help find the right commit.

Ted later explained that the request came from a talk with Hannes Reinecke, who estimated that 15 to 20 percent of Fixes tags are wrong.

That matters beyond bookkeeping, since the tag is how stable maintainers and distributions work out which kernels need a given fix. A wrong one can send a fix to the wrong branches or leave a bug unpatched.

The new find-fixes skill reads Git history and returns a proposed tag with its evidence, while leaving the commit itself untouched.

The skill's guide.rst file says no single clue settles which commit a Fixes tag should name, not even an existing tag. The agent explains how the bug fails, traces candidate commits, and compares each against its parent.

It separates the commit that added the code, the one that made it defective, and any later change that only exposed the flaw.

For backported fixes, it checks whether the bug came from the original change or from how that change was adapted for an older kernel. Merges, reverts, and incomplete histories get their own handling.

When it cannot establish the origin, it returns no tag, lists the candidates and what is missing, and the fix stays a draft until someone resolves it.

Still a work in progress

The second patch would add a section to the kernel's coding assistants document saying an assistant must follow the guide before finalizing a bug fix or its commit message and when reviewing an existing tag.

The document's step for committing a fix would ask for a verified tag, where it now asks only for a Fixes tag. Keep in mind that the skill would not write commit messages, apply the tag, or decide whether a fix belongs in stable.

The series follows Levin's earlier push for the kernel's AI coding assistants policy, which we covered in April, and his proposal for a kernel killswitch.

Where the files should live is still open. The introductory patch message says he is unsure whether they belong under Documentation or in a separate agents directory at the root.

Greg Kroah-Hartman asked whether the series would fix tools skipping the kernel's guidance because an AGENTS.md file is missing. Sasha replied that this is a separate issue for the symlink patch.

4
72
submitted 1 day ago by cm0002@lemy.lol to c/linux@programming.dev
5
36
submitted 2 days ago by cm0002@toast.ooo to c/linux@programming.dev

Timestamps:

00:00 Intro

00:38 Sponsor: Internxt

02:12 Entire Adobe Suite supported with custom Wine now

03:53 Open source clean room implementations of the entire Adobe Suite

07:35 Flathub now accepts apps that used Al, with disclosure

10:18 Cosmic will reject LLM generated submissions

11:35 Steam Frame now has 200 verified games

13:03 More Kernel and AMD performance improvements

15:43 Digital Ocean stops hosting credits for FOSS as they donate to Omacom

17:50 Gentoo asking for help for hosting after sponsors dried up

19:14 Orion stops development of its Linux browser

20:45 EU Commission doesn't seem pleased with their Teams replacement

22:31 Googlebooks don't look like they'll help Linux much

24:23 Mesa looking at a more formal governance model

26:53 Sponsor: Tuxedo Computers

Links

Entire Adobe Suite supported with custom Wine now

https://neutronproject.org/

Open source clean room implementations of the entire Adobe Suite

https://github.com/storytold/photocraft

Flathub now accepts apps that used Al, with disclosure

https://linuxiac.com/flathub-reverses-ai-generated-app-ban-now-requires-disclosure/

Cosmic will reject LLM generated submissions

https://linuxiac.com/cosmic-stops-accepting-Ilm-generated-content-in-pull-requests/

https://github.com/pop-os/cosmic-epoch/blob/master/.github/PULL_REQUEST_TEMPLATE.md

Steam Frame now has 200 verified games

https://store.steampowered.com/greatonframe?tab=1

https://www.gamingonlinux.com/2026/10/theres-now-over-200-steam-frame-verified-games/

More Kernel and AMD performance improvements

https://www.phoronix.com/news/Linux-Better-Zswap-Performance

https://www.phoronix.com/news/Boost-Recently-Busy-CPUs

Digital Ocean stops hosting credits for FOSS as they donate to Omacom

https://itsfoss.com/news/digitalocean-open-source-credits-end/

Gentoo asking for help for hosting after sponsors dried up

https://itsfoss.com/news/gentoo-infrastructure-sponsors-call/

Orion stops development of its Linux browser

https://blog.kagi.com/update-orion-linux-windows

EU Commission doesn't seem pleased with their Teams replacement

https://www.politico.eu/article/eu-microsoft-teams-alternative-bad-reviews-element-pro/

Googlebooks don't look like they'll help Linux much

https://www.androidauthority.com/linux-apps-on-googlebook-3719936/

Mesa looking at a more formal governance model

https://www.phoronix.com/news/Mesa-Governance-Model

6
56
7
114

RyanL Bitwarden Employee

Hello everyone!

Starting in the next release, the Bitwarden apps published to the various stores will be the commercially licensed builds. No action is needed, and the apps will work exactly as they do today.

Bitwarden remains committed to open source security and transparency
The GPLv3 OSS licensed version continues to be updated and published on GitHub
All current features are available in both versions
License details are on GitHub
Bitwarden remains committed to a robust, free forever plan for everyone

If you have any questions, please ask them in this thread. Thanks all!

EDIT:

Bitwarden is not going closed-source
You can still fork Bitwarden
No change to self-hosting, the licensing change affects those who are repackaging and reselling Bitwarden
The free plan is here to stay permanently
8
45
9
27
submitted 3 days ago by cm0002@toast.ooo to c/linux@programming.dev
10
22
submitted 3 days ago* (last edited 3 days ago) by Die4Ever@retrolemmy.com to c/linux@programming.dev

this should be a controversial post lol

11
14
12
39

Since the last post about zswap sparked so much discussion lol

13
35
submitted 3 days ago by cm0002@toast.ooo to c/linux@programming.dev

Flathub has replaced its blanket ban on AI-generated applications with a disclosure requirement. Reviewers can still reject submissions, and manifests remain off-limits for AI-generated content.

14
28
submitted 3 days ago by cm0002@toast.ooo to c/linux@programming.dev

Ubuntu maker Canonical announced today the general availability of Ubuntu Desktop images for the RISC-V architecture, along with unofficial and unsupported Xubuntu Minimal images for RISC-V.

As I reported back in June, when the first daily build images for Ubuntu 26.10 were made available to download, there was a new RISC-V desktop image available too, but now Canonical is making everything official: Ubuntu 26.10 (Stonking Stingray) brings desktop images to RISC-V computers.

That’s right, if you have a RISC-V computer and want to use Ubuntu on it, you will be able to do so with the upcoming Ubuntu 26.10 release, due out next week on October 15th, 2026. Even better, it looks like there will also be a RISC-V image for the Xubuntu flavor featuring the lightweight Xfce desktop environment.

“The Xubuntu variant exists for a practical reason: the Xfce-based minimal image is far more manageable under emulation,” said Canonical. “The images are experimental: they carry no official support yet, and there are still known issues that we are addressing for the release. Bug reports on Launchpad are very welcome.”

Canonical recommends testing the Ubuntu Desktop RISC-V images on SpacemiT K3 hardware since official support for this platform is coming with Ubuntu 26.10, and they even have a guide on how to install Ubuntu on the SpacemiT K3 Pico-ITX. On the other hand, the Xubuntu Minimal images are recommended for testing in virtual machines.

Testing the Ubuntu 26.10 RISC-V desktop images will require you to copy your own first-stage bootloader, such as U-boot, as well as the relevant Device Tree Blobs (DTBs), onto the ISO before booting it on real hardware like the SiFive HiFive Unmatched, which is supported by Canonical.

Canonical promises to deliver a complete desktop experience on RISC-V computers with the Stonking Stingray release, especially on RVA23-compliant hardware like Milk-V Jupiter 2 Mini-ITX, DeepComputing DC-ROMA, and SpacemiT K3 Pico-ITX.

Ubuntu 26.10 is expected to ship with the upcoming GNOME 51 desktop environment by default, which will be released on September 16th, 2026, and the soon-to-be-released Linux 7.3 kernel series, which should be out later this month. I’m hoping that more Ubuntu flavors will pick up RISC-V support in the long run.

Without further ado, you can download the latest Ubuntu 26.10 RISC-V desktop images from here and the Xubuntu Minimal RISC-V image from here. Once again, please keep in mind that these images are considered experimental, so don’t use them for any production work.

15
132
submitted 5 days ago by cm0002@toast.ooo to c/linux@programming.dev
16
111
submitted 5 days ago by cm0002@toast.ooo to c/linux@programming.dev
17
68
submitted 5 days ago by cm0002@toast.ooo to c/linux@programming.dev

Plenty of open source projects keep going on goodwill alone, with contributors putting in the hours and expecting nothing back. While others lean on outside support like cash, donated hardware, or someone else covering the hosting bill.

This kind of support rarely gets much attention, but these needs are some of the most foundational aspects of any project that's serious about growing.

Gentoo falls in the second group. The source-based Linux distribution, built around the Portage package manager, runs largely on sponsored infrastructure, as it can only manage to maintain a few vital machines.

Sadly, many sponsors that had backed Gentoo all these years have decided to stop making contributions. The project is now looking for replacements and has put out a call for infrastructure sponsors.

Currently, its sponsors page lists names such as Oregon State University's Open Source Lab, CDN77, HP, and Hetzner, but it may not yet reflect the dropouts.

There are five ways to help, as laid out on the sponsorship page of Gentoo's wiki, with preference being given to supporters who share the project's vision of software that respects choice and stays open to user-driven changes.

The first way is to accept donated machines for the project's hosting locations in the US. They are not asking for much; anything good enough to handle server-focused tasks in today's time is a good offering for them to use.

Next is Colocation, a type of physical hosting. The sponsor would provide rack space, power, and connectivity, while Gentoo finds the hardware to put in it. Capacity outside the US is their most urgent need at the moment, though offers from the US are welcome too.

Third are virtual machines, with a minimum of 2 vCPUs, 4GB of RAM, and 25GB of storage. The project says that it is leaning more on the cloud wherever it can, but many of its services are monolithic, and that Kubernetes would suit them poorly.

The fourth way is full-package hosted physical servers. The wiki gives two examples: a root server like the ones Hetzner offers, or a sponsor's older or unused servers with Gentoo getting full remote access.

In that second case, the sponsor would still own and manage the hardware, whereas Gentoo would take care of the operating system and remote management, only asking for advance notice before any migration events.

The last is plain old money. Any donated funds would go toward paying for colocation and hosting.

A call to act

Gentoo is far from the only project that needs this kind of backing.

Take LVFS, the firmware update service for Linux. It leaned heavily on the Linux Foundation and Red Hat, with Framework and the Open Source Firmware Foundation pitching in $10,000 a year.

Then Lenovo and Dell joined at the Premier tier, at $100,000 a year each, along with HP and NVIDIA, who followed soon after. I would call that a win for LVFS and a sign that sponsors are out there for projects that go looking.

Maybe your organization has spare rack space, or you have money lying around and want it to do some good. Either way, someone has to host the servers behind projects like this, and Gentoo's infrastructure team is available at infra@gentoo.org for any infrastructure sponsorship-related queries.

18
57
submitted 4 days ago by cm0002@toast.ooo to c/linux@programming.dev

The EXT4 file-system today deprecated its journaled mode of the "data=journal" mount option. Following its deprecation, this mode is planned for removal in the year 2028.

The data=journal mode for EXT4 is where all file data and metadata is written to the file-system's journal before being committed to the main file-system. In the event of a crash or power loss, the journal can then be replayed to recover the data.

The EXT4 data=journal mode is great for those very concerned about data integrity and safety but comes with significant hits to the write performance compared to the default ordered (data=ordered) mode or data=writeback. Using the journaled mode also disables delayed allocation and Direct I/O support.

EXT4 journal deprecated

Per today's Git merge for Linux 7.3, the EXT4 data=journal feature is deprecated and support for it will be removed in early 2028 following the 2027 Linux LTS kernel version.

19
47
submitted 5 days ago by cm0002@toast.ooo to c/linux@programming.dev

Klassik brings the KDE 3 desktop to Plasma 6: reimplemented panel applets, the KDE 2/3 application style, ports of the KWin window decorations, and the original color schemes and wallpapers, with Wayland support.

20
39
submitted 4 days ago by cm0002@toast.ooo to c/linux@programming.dev

Linux developers are once again considering the removal of the Linux x32 ABI.

Not to be confused with the i386 ABI, the Linux x32 ABI is the little adopted model of using 32-bit integers, long, and pointers on Intel/AMD CPUs but making use of the larger set of CPU registers and other benefits of x86_64. Linux x32 came too late and hasn't seen much industry interest or adoption. With Linux x86_64 going comfortably, Linux kernel developers have been retiring the x32 ABI.

Sebastian Andrzej Siewior has been leading the efforts this year for proposing the x32 ABI retirement. With the end of 2026 approaching and Linux 7.3 or 7.4 being this year's LTS kernel version, the topic of retiring x32 has once again reignited on the Linux kernel mailing list.

start removing x32

The Linutronix engineer sent out a new set of patches today to begin removing the x32 ABI. Sebastian argued in the patch to initially block x32 behind the "BROKEN" Kconfig option:

"The x32 ABI was introduced in v3.4 to leverage the additional registers which were available on x86_64 but not on i386 while keeping the smaller 32bit pointers.

This did not take off. The memory usage usually knows no limit and the better performance did not reach a point where certain workloads widely move to x32 and use it exclusively. In the meantime Debian introduced a patch to disable x32 by default (so it has to be enabled at boot time on the command line) because they are afraid of the increased attack surface. Fedora as far as I tell has X32 disabled (looking at 7.0-rc5 rpm in rawhide).

The syscall range >512 used by x32 can not be reused because on earlier kernels (before v5.4 with x32 enabled, see commit 6365b842aae4 ("x86/syscalls: Split the x32 syscalls into their own table") it is not obvious if the syscall is for x86-64 and not implemented or meant for x32.

What can be removed are the special compat cases due to different alignment.

Since there is practically no real use for x32, start removing it by marking the symbol as BROKEN so it is not possible to enable by default. It will remain around in the last LTS kernel of this year and then it will be removed."

We'll see if the patches begin to land initially marking x32 as "BROKEN" and then eventual removal, following the declaration of the Linux 2026 LTS kernel version.

21
30
22
20
submitted 4 days ago by cm0002@toast.ooo to c/linux@programming.dev

Linux hardware vendor System76 released COSMIC 1.10 today as the latest stable version of this Rust-based desktop environment for modern GNU/Linux distributions.

COSMIC 1.10 comes two weeks after COSMIC 1.9 with support for mapping drawing tablets to specific displays, support for setting environment variables in ~/.config/environment.d, support for using custom SSH agents, and support for remembering sort options in file open/save dialogs.

The COSMIC Term terminal emulator received keyboard shortcuts for moving tabs left (Ctrl+Shift+Left) and right (Ctrl+Shift+Right), COSMIC Store now adds a gallery mode after clicking screenshots and caches screenshots locally, and the cosmic-settings-daemon is now in charge of setting the interface font when syncing font settings with GTK/GNOME.

COSMIC Player has been updated as well with support for keeping the controls visible when hovered, COSMIC OSD no longer shows volume OSD when started, COSMIC Monitor now features separate app and process searches, and COSMIC Launcher now uses WGPU for rendering in order to improve performance.

COSMIC Greeter display manager was improved as well in this release with kmscon support to systemd service on Fedora Linux, a fix for a panic when the keyboard layouts are empty, and support for cancelling the PAM session when the wrong password is used to ensure that pam_faillock remains functional.

On top of that, COSMIC Compositor received fixes for issues with window context menu items being selected when clicking outside the menu, focusing windows on touchscreen events, screen capture using an inefficient pixel format, resizing not working in some cases while tiling, and focus not being removed from unfocused windows.

Last but not least, COSMIC Files now ellipsizes the full path in search results to keep it from being truncated and includes trailing ... to menu items that open a context drawer, cosmic-idle can now handle system suspending on AC correctly, and COSMIC Initial Setup now only shows the Wi-Fi page if a Wi-Fi device exists.

Various smaller issues were fixed as well, so check out the release notes on the project’s GitHub page for more details. Meanwhile, keep an eye on the stable software repositories of your favorite Linux distro for the COSMIC 1.10 update and install it as soon as possible for a more reliable, stable, and bug-free COSMIC desktop experience

23
31
submitted 5 days ago by cm0002@toast.ooo to c/linux@programming.dev
24
114
submitted 6 days ago* (last edited 6 days ago) by Die4Ever@retrolemmy.com to c/linux@programming.dev

The graph is on a logarithmic scale btw

Configuration Before series (ms) With series (ms)
1 vCPU 22.3 (21.6-22.6) 0.97 (0.72-1.4)
8 vCPUs 314 (97-2542) 7.0 (5.0-98)
25
13
submitted 5 days ago by cm0002@toast.ooo to c/linux@programming.dev

The Q4OS team announced today the release and general availability of Q4OS 6.10 as the tenth update to the Q4OS 6 “Andromeda” series of this Debian-based Linux distro featuring KDE Plasma and Trinity Desktop Environment.

Based on Debian 13.7 “Trixie” and powered by Linux kernel 6.12.111 LTS, Q4OS 6.10 ships with the KDE Plasma 6.3.6 desktop environment for the flagship edition, which is accompanied by the KDE Gear 25.04.3 and KDE Frameworks 6.13 software suites, all compiled against Qt 6.8.2, as well as the Trinity Desktop Environment (TDE) 14.1.5 desktop environment on the TDE edition.

Q4OS 6.10 updates the KDE Plasma edition to no longer include any packages from the Trinity Desktop Environment by default on the live media or when installing the distribution, as the Q4OS tools now come with their own Qt 5 frontends. Of course, the Trinity Desktop Environment remains installable side by side.

The live Q4OS media now comes with the basic desktop profile and the live-session extras, which include the installer, web browser, Q4OS Imager, CJK fonts, VirtualBox guest additions, and language packs. The devs removed the old KDE Frameworks libraries on the TDE edition, as well as the QtCurve and old window styles.

Q4OS 6.10 introduces a new Q4OS Wi-Fi connect tool that will be displayed during the first login on both KDE Plasma and TDE editions, replacing the old Trinity-only dialog, to make connecting to a Wi-Fi network easier. Also, NumLock is now enabled at first boot on desktops and laptops with a numeric keypad, while it stays disabled on laptops without a numeric keypad.

On top of that, this release splits the Q4OS Setup application installer into a Trinity and a Qt 5 frontends, so each Q4OS edition gets the native one, and the fail-safe entry of the live boot menu now starts the graphics in nomodeset mode for machines whose graphics driver fails to start.

Among other noteworthy changes, the Q4OS Software Centre no longer offers the Mozilla Firefox web browser on 32-bit (i386) systems, since it’s no longer supported upstream, while Q4OS 5 i386 users are offered Debian’s Firefox ESR instead. Check out the release announcement for more details.

Q4OS 6.10 is available for download as KDE Plasma and TDE (Trinity Desktop Environment) editions for 64-bit systems from the official website. Existing Q4OS users can update their installations by running the sudo apt update && sudo apt full-upgrade commands in a terminal emulator

view more: next ›

Linux

15192 readers
190 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS