#linux

posts tagged #linux

0

Two Independent Projects Want to Bring MATE to Wayland, Each in its Own Way

It's FOSS Two Independent Projects Want to Bring MATE to Wayland, Each in its Own Way itsfoss.com
preview

The big Linux desktop environments have largely made up their minds about Wayland.

GNOME finished removing X11 from its login manager in March, and last month, KDE Plasma retired support for starting X11 sessions. Cinnamon is a step behind, but Linux Mint 27, due around Christmas, is set to ship a Wayland session that is no longer experimental. Though X11 stays the default.

Smaller desktops are at different points on the same journey.

LXQt dropped the experimental label from its Wayland session in v2.3.0, and Budgie in the Ubuntu Budgie 26.04 release went Wayland-only with labwc.

MATE, on the other hand, has moved in bits and pieces. Since MATE 1.26, apps like Atril, System Monitor, Pluma, and Terminal can run on Wayland, while the official mate-wayland-session is a simple, experimental setup that relies on Wayfire.

What’s still missing is a Wayland-native window manager for MATE. Its own, Marco, has no Wayland mode, and the following two projects, Polo and MATE Wayland Desktop, now aim to replace it in different ways.

Polo

Polo comes from developer Kerem Söke, and it is a compositor, window manager, and session manager for people who want MATE to look and behave on Wayland the way it does today.

It is written in Vala and C on top of libweston 16, follows Marco’s window management rules, and retains the settings, themes, and keybindings MATE users already have. Apps that still need X11 get a window manager of their own under XWayland.

Polo handles the session too, using the D-Bus interface of mate-session-manager, and the panel, Caja, and the screensaver can talk to it as they would on X11.

It’s first stable release was published on 12 November with support for tiling, workspaces, screen sharing through xdg-desktop-portal, and layer shell compatibility for mate-panel.

A DRM backend is responsible for handling multiple monitors and remembering screen layouts. Effects like wobbly windows and a desktop cube are also included (fans of Compiz, rejoice!).

You can build Polo from source on Fedora 44 or 45, Debian 14, or Ubuntu 26.04 or 26.10. Once installed, a “MATE (Polo)” entry should show up in LightDM.

Kerem has also said that he may host his own .deb repository if the Debian and Ubuntu MATE teams do not ship Wayland-enabled packages.

MATE Wayland Desktop

MATE Wayland Desktop uses an existing compositor instead of writing one. It swaps Marco for labwc and ships as an installable ISO built on Ubuntu 26.04 LTS, with Linux 7.0 and MATE 1.29 components as the foundations.

Eight of those MATE packages are rebuilt from newer upstream code, and one of them is mate-panel 1.29.2 with Wayland support turned on. Apps that only speak X11 run through XWayland.

Installation is handled by Calamares, and it offers optional LUKS2 full-disk encryption.

The project is also clear about the rough edges in it.

The keyboard, mouse, and keyboard shortcuts panels in Control Center crash when running natively, so MATE Wayland Desktop opens them through XWayland instead.

MATE’s own Displays dialog does not work on Wayland either. The “Displays” entry in the launcher opens wdisplays instead.

During installation and usage, Secure Boot has to be off, and the ISO boots up with the open source Nouveau GPU driver. NVIDIA’s own driver can be installed afterward with ubuntu-drivers.

Seeing that this is a new offering, I highly recommend you test it on a spare machine before going for a full installation.

You can get started with its ISO on x86_64 systems by heading over to the official download portal.

The big Linux desktop environments have largely made up their minds about Wayland.

GNOME finished removing X11 from its login manager in March, and last month, KDE Plasma retired support for starting X11 sessions. Cinnamon is a step behind, but Linux Mint 27, due around Christmas, is set to ship a Wayland session that is no longer experimental. Though X11 stays the default.

Smaller desktops are at different points on the same journey.

LXQt dropped the experimental label from its Wayland session in v2.3.0, and Budgie in the Ubuntu Budgie 26.04 release went Wayland-only with labwc.

MATE, on the other hand, has moved in bits and pieces. Since MATE 1.26, apps like Atril, System Monitor, Pluma, and Terminal can run on Wayland, while the official mate-wayland-session is a simple, experimental setup that relies on Wayfire.

What’s still missing is a Wayland-native window manager for MATE. Its own, Marco, has no Wayland mode, and the following two projects, Polo and MATE Wayland Desktop, now aim to replace it in different ways.

Polo

Polo comes from developer Kerem Söke, and it is a compositor, window manager, and session manager for people who want MATE to look and behave on Wayland the way it does today.

It is written in Vala and C on top of libweston 16, follows Marco’s window management rules, and retains the settings, themes, and keybindings MATE users already have. Apps that still need X11 get a window manager of their own under XWayland.

Polo handles the session too, using the D-Bus interface of mate-session-manager, and the panel, Caja, and the screensaver can talk to it as they would on X11.

It’s first stable release was published on 12 November with support for tiling, workspaces, screen sharing through xdg-desktop-portal, and layer shell compatibility for mate-panel.

A DRM backend is responsible for handling multiple monitors and remembering screen layouts. Effects like wobbly windows and a desktop cube are also included (fans of Compiz, rejoice!).

You can build Polo from source on Fedora 44 or 45, Debian 14, or Ubuntu 26.04 or 26.10. Once installed, a “MATE (Polo)” entry should show up in LightDM.

Kerem has also said that he may host his own .deb repository if the Debian and Ubuntu MATE teams do not ship Wayland-enabled packages.

MATE Wayland Desktop

MATE Wayland Desktop uses an existing compositor instead of writing one. It swaps Marco for labwc and ships as an installable ISO built on Ubuntu 26.04 LTS, with Linux 7.0 and MATE 1.29 components as the foundations.

Eight of those MATE packages are rebuilt from newer upstream code, and one of them is mate-panel 1.29.2 with Wayland support turned on. Apps that only speak X11 run through XWayland.

Installation is handled by Calamares, and it offers optional LUKS2 full-disk encryption.

The project is also clear about the rough edges in it.

The keyboard, mouse, and keyboard shortcuts panels in Control Center crash when running natively, so MATE Wayland Desktop opens them through XWayland instead.

MATE’s own Displays dialog does not work on Wayland either. The “Displays” entry in the launcher opens wdisplays instead.

During installation and usage, Secure Boot has to be off, and the ISO boots up with the open source Nouveau GPU driver. NVIDIA’s own driver can be installed afterward with ubuntu-drivers.

Seeing that this is a new offering, I highly recommend you test it on a spare machine before going for a full installation.

You can get started with its ISO on x86_64 systems by heading over to the official download portal.

0

Canonical is Now Shipping AI-Written Security Patches to Ubuntu Pro Users

It's FOSS Canonical is Now Shipping AI-Written Security Patches to Ubuntu Pro Users itsfoss.com
preview

If you’ve followed security news this year, you know the number of reported vulnerabilities has gone up sharply. AI-assisted bug hunting means flaws are being found faster than maintainers can patch them, and every distro is feeling the pressure.

Canonical’s answer is to fight fire with fire. They are going to use AI to fix what AI is finding. At the recently concluded Ubuntu Summit 26.10, Canonical introduced Surge, a multi-agent AI system that triages vulnerabilities and writes backported fixes for Ubuntu packages.

Don’t worry. None of this goes into your regular Ubuntu security updates automatically. Surge’s fixes go to a new opt-in repository called the Edge archive, and only reach the normal updates after human-led testing.

The CVE problem Canonical is trying to solve

The announcement came in the security segment of the Summit’s opening remarks, presented by Pierre Guillemin, VP Engineering.

He started with numbers. According to the slides, the “fix velocity” in Ubuntu increased by 119% in one year. The “fix volume by quarter” chart shows roughly 1,400 fixes in early 2025 and about 3,100 a quarter by mid-2026.

That’s not it. Canonical says October 2026 alone had almost as many CVEs as all of 2025. October 2026 had almost as many CVEs as all of 2025

And Canonical doesn’t expect this to slow down. Guillemin said the company expects 2027 to bring “another order of magnitude growth” in CVEs.

How do you keep up with this pace while sticking to the review and testing standards that stable Ubuntu releases are known for? Hiring and working harder cannot practically compete with this pace.

Meet Surge

Surge is “a multi-agent orchestration framework for remediating vulnerabilities in Ubuntu.”

In simpler words, it’s a pipeline where several specialised AI agents handle different steps of fixing a CVE, from finding out whether Ubuntu is affected to producing a patch. Surge is a multi-agent orchestration framework

Guillemin says it builds on Canonical’s 20+ years of Ubuntu security work. The stated goal is to absorb a big influx of CVEs without creating backlogs. Or, as he put it, “fight AI with AI.”

Surge only covers Ubuntu userspace packages, meaning the applications and libraries in the archive. Kernel CVEs are not part of it, as kernel fixes need a different backporting approach and follow their own release cycle. How does Surge work?

The pipeline has six stages, and the interesting part is that it doesn’t trust a single AI model. Surge pipeline slide at Ubuntu Summit 26.10

It starts with intake and sourcing, which takes in vulnerability reports, maps them to packages, and checks whether the affected package is in Ubuntu at all. Then code forensics fetches the upstream patch, analyses the source, and tries to reproduce the vulnerability to confirm Ubuntu’s version is actually affected.

In the backporting engine, instead of one model writing the patch, several competing models each produce a candidate fix.

These candidates then go to consensus judging, where a separate panel of “judge” models evaluates them and has to agree on the right patch. If confidence is low or the judges deadlock, the case goes to human escalation, where Ubuntu security engineers review it manually.

Finally, the patch goes through the same build, verify and publish process as any other Ubuntu package, including deterministic tests, before it is published.

The Edge archive: AI fixes, but only if you ask for them

Surge-generated fixes are not pushed to your system through the usual security updates. Instead, Canonical is launching the Edge archive, an opt-in preview of fixes that are still in development.

Edge gives you machine-generated patches before they’ve gone through Canonical’s full qualification for general availability (GA). So you get fixes at “machine speed,” but with the compromise on the fact they haven’t had the full testing yet.

Canonical stresses that this is not a change in its security policy. It “will not automatically upload Surge-generated fixes to our stable releases.” Your regular security updates stay human-validated and keep coming through the usual channels.

Will you opt-in?

If you’re a regular Ubuntu desktop or server user, nothing changes unless you choose to. Your security updates continue to arrive the way they always have.

If you want to try it, Edge is available through Ubuntu Pro, which remains free for personal use. Canonical has published a guide on how to enable the Edge archive.

I wouldn’t put Edge on a production server, yet. But on a regular desktop machine or a homelab, it’s a good way to help Canonical find problems early.

To be honest, the idea of AI writing security patches will make some of you uneasy, and that’s fair. But we have to “fight AI with AI” because CVEs are not going to stop or reduced. Am I right?

If you’ve followed security news this year, you know the number of reported vulnerabilities has gone up sharply. AI-assisted bug hunting means flaws are being found faster than maintainers can patch them, and every distro is feeling the pressure.

Canonical’s answer is to fight fire with fire. They are going to use AI to fix what AI is finding. At the recently concluded Ubuntu Summit 26.10, Canonical introduced Surge, a multi-agent AI system that triages vulnerabilities and writes backported fixes for Ubuntu packages.

Don’t worry. None of this goes into your regular Ubuntu security updates automatically. Surge’s fixes go to a new opt-in repository called the Edge archive, and only reach the normal updates after human-led testing.

The CVE problem Canonical is trying to solve

The announcement came in the security segment of the Summit’s opening remarks, presented by Pierre Guillemin, VP Engineering.

He started with numbers. According to the slides, the “fix velocity” in Ubuntu increased by 119% in one year. The “fix volume by quarter” chart shows roughly 1,400 fixes in early 2025 and about 3,100 a quarter by mid-2026.

That’s not it. Canonical says October 2026 alone had almost as many CVEs as all of 2025. October 2026 had almost as many CVEs as all of 2025

And Canonical doesn’t expect this to slow down. Guillemin said the company expects 2027 to bring “another order of magnitude growth” in CVEs.

How do you keep up with this pace while sticking to the review and testing standards that stable Ubuntu releases are known for? Hiring and working harder cannot practically compete with this pace.

Meet Surge

Surge is “a multi-agent orchestration framework for remediating vulnerabilities in Ubuntu.”

In simpler words, it’s a pipeline where several specialised AI agents handle different steps of fixing a CVE, from finding out whether Ubuntu is affected to producing a patch. Surge is a multi-agent orchestration framework

Guillemin says it builds on Canonical’s 20+ years of Ubuntu security work. The stated goal is to absorb a big influx of CVEs without creating backlogs. Or, as he put it, “fight AI with AI.”

Surge only covers Ubuntu userspace packages, meaning the applications and libraries in the archive. Kernel CVEs are not part of it, as kernel fixes need a different backporting approach and follow their own release cycle. How does Surge work?

The pipeline has six stages, and the interesting part is that it doesn’t trust a single AI model. Surge pipeline slide at Ubuntu Summit 26.10

It starts with intake and sourcing, which takes in vulnerability reports, maps them to packages, and checks whether the affected package is in Ubuntu at all. Then code forensics fetches the upstream patch, analyses the source, and tries to reproduce the vulnerability to confirm Ubuntu’s version is actually affected.

In the backporting engine, instead of one model writing the patch, several competing models each produce a candidate fix.

These candidates then go to consensus judging, where a separate panel of “judge” models evaluates them and has to agree on the right patch. If confidence is low or the judges deadlock, the case goes to human escalation, where Ubuntu security engineers review it manually.

Finally, the patch goes through the same build, verify and publish process as any other Ubuntu package, including deterministic tests, before it is published.

The Edge archive: AI fixes, but only if you ask for them

Surge-generated fixes are not pushed to your system through the usual security updates. Instead, Canonical is launching the Edge archive, an opt-in preview of fixes that are still in development.

Edge gives you machine-generated patches before they’ve gone through Canonical’s full qualification for general availability (GA). So you get fixes at “machine speed,” but with the compromise on the fact they haven’t had the full testing yet.

Canonical stresses that this is not a change in its security policy. It “will not automatically upload Surge-generated fixes to our stable releases.” Your regular security updates stay human-validated and keep coming through the usual channels.

Will you opt-in?

If you’re a regular Ubuntu desktop or server user, nothing changes unless you choose to. Your security updates continue to arrive the way they always have.

If you want to try it, Edge is available through Ubuntu Pro, which remains free for personal use. Canonical has published a guide on how to enable the Edge archive.

I wouldn’t put Edge on a production server, yet. But on a regular desktop machine or a homelab, it’s a good way to help Canonical find problems early.

To be honest, the idea of AI writing security patches will make some of you uneasy, and that’s fair. But we have to “fight AI with AI” because CVEs are not going to stop or reduced. Am I right?

0

AV Linux 25.3 for Content Creators Returns to Xfce by Default

Linuxiac AV Linux 25.3 for Content Creators Returns to Xfce by Default linuxiac.com
preview

AV Linux 25.3, a Debian-based Linux distro for multimedia content creators, has been released, marking the return of Xfce as a fully integrated desktop environment alongside Enlightenment. AV Linux now boots into Xfce by default, but users can switch to Enlightenment from the LightDM login screen.

According to developer Glen MacArthur, the decision to bring back Xfce was driven by user feedback. Some users were reluctant to adopt Enlightenment after the distribution’s earlier desktop transition, and the new release offers both environments without abandoning the existing Enlightenment integration.

The two desktops share ConnMan for network connectivity, the Xfce application menu, similar panel layouts, and matching keyboard shortcuts. Moreover, a new Mosaic theme provides a consistent appearance across both environments.

Another change is the introduction of a dedicated package repository, replacing the previous web-based package archive. It is divided into three components: Desktop Enlightenment for AV Linux themes and configurations, Desktop Moksha for MX Moksha-specific packages, and Main for multimedia applications and plugins shared by both distributions.

The release also introduces in-house packaging of the Enlightenment stack, including EFL 1.29.0, Enlightenment 0.28, and associated applications and modules. Updated applications include the Evisum system monitor, Elaro IRC client, Eclair music player, and Equation calculator. MX Moksha, meanwhile, receives Moksha 4.2, along with fixes for suspend and hibernate functionality.

Under the hood, AV Linux 25.3 ships with the Liquorix kernel 7.3.4. The updated multimedia software selection includes Ardour 9.10, REAPER 7.85 as a demo, Audacity 4.0.2, and Cinelerra-GG. New audio plugins, including Pitchnet, are also available through the repository.

Several refinements have been made to the distribution’s file actions, including crop and preview functionality for the video upscaler. A new MX Linux utility for verifying ISO signatures is included as well.

One important consideration for existing users is that the extensive package restructuring requires a fresh installation to obtain the complete AV Linux 25.3 experience, including the new desktop configurations and repository integration.

However, users running AV Linux or MX Moksha 25 through 25.2 can enable the new Main repository without reinstalling. This provides access to updated multimedia applications, plugins, and file actions, although the new themes and desktop configurations will not be included.

Finally, the developer has discontinued XLibre ISO builds, citing the additional maintenance requirements and limited VPS storage capacity. Future package updates will also be distributed through the new repository rather than the old web archive.

For more information, see the announcement.

AV Linux 25.3, a Debian-based Linux distro for multimedia content creators, has been released, marking the return of Xfce as a fully integrated desktop environment alongside Enlightenment. AV Linux now boots into Xfce by default, but users can switch to Enlightenment from the LightDM login screen.

According to developer Glen MacArthur, the decision to bring back Xfce was driven by user feedback. Some users were reluctant to adopt Enlightenment after the distribution’s earlier desktop transition, and the new release offers both environments without abandoning the existing Enlightenment integration.

The two desktops share ConnMan for network connectivity, the Xfce application menu, similar panel layouts, and matching keyboard shortcuts. Moreover, a new Mosaic theme provides a consistent appearance across both environments.

Another change is the introduction of a dedicated package repository, replacing the previous web-based package archive. It is divided into three components: Desktop Enlightenment for AV Linux themes and configurations, Desktop Moksha for MX Moksha-specific packages, and Main for multimedia applications and plugins shared by both distributions.

The release also introduces in-house packaging of the Enlightenment stack, including EFL 1.29.0, Enlightenment 0.28, and associated applications and modules. Updated applications include the Evisum system monitor, Elaro IRC client, Eclair music player, and Equation calculator. MX Moksha, meanwhile, receives Moksha 4.2, along with fixes for suspend and hibernate functionality.

Under the hood, AV Linux 25.3 ships with the Liquorix kernel 7.3.4. The updated multimedia software selection includes Ardour 9.10, REAPER 7.85 as a demo, Audacity 4.0.2, and Cinelerra-GG. New audio plugins, including Pitchnet, are also available through the repository.

Several refinements have been made to the distribution’s file actions, including crop and preview functionality for the video upscaler. A new MX Linux utility for verifying ISO signatures is included as well.

One important consideration for existing users is that the extensive package restructuring requires a fresh installation to obtain the complete AV Linux 25.3 experience, including the new desktop configurations and repository integration.

However, users running AV Linux or MX Moksha 25 through 25.2 can enable the new Main repository without reinstalling. This provides access to updated multimedia applications, plugins, and file actions, although the new themes and desktop configurations will not be included.

Finally, the developer has discontinued XLibre ISO builds, citing the additional maintenance requirements and limited VPS storage capacity. Future package updates will also be distributed through the new repository rather than the old web archive.

For more information, see the announcement.

0

Rocky Linux 10.3 Released with Kernel 6.12, GCC 16, and Security Updates

Linuxiac Rocky Linux 10.3 Released with Kernel 6.12, GCC 16, and Security Updates linuxiac.com
preview

Rocky Linux 10.3 (Red Quartz) has been officially released following the Red Hat Enterprise Linux 10.3 release on November 11. The new version arrives alongside AlmaLinux 10.3, also released today, giving users two updated free RHEL-compatible options.

As expected, Rocky Linux 10.3 is built around Linux kernel 6.12, specifically version 6.12.0-264.16.1. Several kernel components have been updated beyond that baseline. The eBPF subsystem and perf tools are rebased to Linux 6.19, while memory management improvements include newer CXL support and changes to compressed swap handling.

Hardware support has also been improved, particularly for Intel platforms, while AMD’s amdxdna driver for Neural Processing Units (NPUs) is now available as a Technology Preview.

On the development side, Rocky Linux 10.3 introduces GCC Toolset 16, featuring GCC 16.2 and Binutils 2.46, alongside LLVM 22.1.8. The update also includes Rust 1.97, Go 1.27.3, and GDB 17.2, giving developers access to newer language features, debugging capabilities, and compiler improvements.

Regarding security, Libreswan 5.4 introduces post-quantum key exchange support through ML-KEM-768 and ML-KEM-1024, while SSH connections operating in FIPS mode now support and prefer hybrid post-quantum key exchange algorithms.

Other security-related updates include Keylime 7.14.3, which improves remote attestation capabilities, and fapolicyd 2.0.1, which introduces parallel policy processing and transactional updates. OpenSC 0.27.1 adds PKCS #11 3.2 support, while the updated Audit 4.2.1 provides additional capabilities for secure remote logging.

System monitoring also receives updates, with Grafana 12.4.3 introducing a redesigned dashboard architecture and improvements to unified alerting. Performance Co-Pilot 7.1.5 adds automatic archive repair and additional performance metrics.

For administrators working with system images, the image-builder command-line interface is now generally available. The web-based image builder can generate bootc-compatible images from locally available base images, while Kickstart gains additional certificate-handling capabilities during installation.

There are several compatibility changes worth mentioning. WEP wireless security support has been removed, along with the ZBUD compressed page allocator. Grafana also drops legacy alerting and AngularJS plugin support, which could affect existing monitoring configurations.

Regarding supported architectures, Rocky Linux 10.3 is available for x86-64-v3, ARM64, RISC-V, POWER10 and newer (ppc64le), and IBM z15 and newer. As with previous Rocky Linux 10 releases, older x86-64-v2 processors are not supported.

Existing Rocky Linux 10 users can upgrade to version 10.3 using the standard sudo dnf -y upgrade command or graphical update tools. However, upgrades from Rocky Linux 8 or 9 to version 10 are not officially supported, with a fresh installation recommended instead.

Installation ISOs, container images, cloud images, and live images are available from the Rocky Linux downloads page. For more information, see the official announcement.

Rocky Linux 10.3 (Red Quartz) has been officially released following the Red Hat Enterprise Linux 10.3 release on November 11. The new version arrives alongside AlmaLinux 10.3, also released today, giving users two updated free RHEL-compatible options.

As expected, Rocky Linux 10.3 is built around Linux kernel 6.12, specifically version 6.12.0-264.16.1. Several kernel components have been updated beyond that baseline. The eBPF subsystem and perf tools are rebased to Linux 6.19, while memory management improvements include newer CXL support and changes to compressed swap handling.

Hardware support has also been improved, particularly for Intel platforms, while AMD’s amdxdna driver for Neural Processing Units (NPUs) is now available as a Technology Preview.

On the development side, Rocky Linux 10.3 introduces GCC Toolset 16, featuring GCC 16.2 and Binutils 2.46, alongside LLVM 22.1.8. The update also includes Rust 1.97, Go 1.27.3, and GDB 17.2, giving developers access to newer language features, debugging capabilities, and compiler improvements.

Regarding security, Libreswan 5.4 introduces post-quantum key exchange support through ML-KEM-768 and ML-KEM-1024, while SSH connections operating in FIPS mode now support and prefer hybrid post-quantum key exchange algorithms.

Other security-related updates include Keylime 7.14.3, which improves remote attestation capabilities, and fapolicyd 2.0.1, which introduces parallel policy processing and transactional updates. OpenSC 0.27.1 adds PKCS #11 3.2 support, while the updated Audit 4.2.1 provides additional capabilities for secure remote logging.

System monitoring also receives updates, with Grafana 12.4.3 introducing a redesigned dashboard architecture and improvements to unified alerting. Performance Co-Pilot 7.1.5 adds automatic archive repair and additional performance metrics.

For administrators working with system images, the image-builder command-line interface is now generally available. The web-based image builder can generate bootc-compatible images from locally available base images, while Kickstart gains additional certificate-handling capabilities during installation.

There are several compatibility changes worth mentioning. WEP wireless security support has been removed, along with the ZBUD compressed page allocator. Grafana also drops legacy alerting and AngularJS plugin support, which could affect existing monitoring configurations.

Regarding supported architectures, Rocky Linux 10.3 is available for x86-64-v3, ARM64, RISC-V, POWER10 and newer (ppc64le), and IBM z15 and newer. As with previous Rocky Linux 10 releases, older x86-64-v2 processors are not supported.

Existing Rocky Linux 10 users can upgrade to version 10.3 using the standard sudo dnf -y upgrade command or graphical update tools. However, upgrades from Rocky Linux 8 or 9 to version 10 are not officially supported, with a fresh installation recommended instead.

Installation ISOs, container images, cloud images, and live images are available from the Rocky Linux downloads page. For more information, see the official announcement.

0

(ignore skirt and socks) Mobian running natively on Pixel 3 with NuraOS kernel+Mobian

preview

1196411963 Not usable, it can detect modem and sim card but can’t pick up service, all sensors are not working touch stop responding if left in lock screen for 2h or more also no cameras (front work in NuraOS), GPU, speakers, buttons are working fine

OC by @ColdWater@lemmy.ca

1196411963 Not usable, it can detect modem and sim card but can’t pick up service, all sensors are not working touch stop responding if left in lock screen for 2h or more also no cameras (front work in NuraOS), GPU, speakers, buttons are working fine

OC by @ColdWater@lemmy.ca

0

(ignore skirt and socks) Mobian running natively on Pixel 3 with NuraOS kernel+Mobian

preview

1196411963 Not usable, it can detect modem and sim card but can’t pick up service, all sensors are not working touch stop responding if left in lock screen for 2h or more also no cameras (front work in NuraOS), GPU, speakers, buttons are working fine

1196411963 Not usable, it can detect modem and sim card but can’t pick up service, all sensors are not working touch stop responding if left in lock screen for 2h or more also no cameras (front work in NuraOS), GPU, speakers, buttons are working fine

0

AV Linux 25.3 for Content Creators Returns to Xfce by Default

Linuxiac AV Linux 25.3 for Content Creators Returns to Xfce by Default linuxiac.com
preview

AV Linux 25.3, a Debian-based Linux distro for multimedia content creators, has been released, marking the return of Xfce as a fully integrated desktop environment alongside Enlightenment. AV Linux now boots into Xfce by default, but users can switch to Enlightenment from the LightDM login screen.

According to developer Glen MacArthur, the decision to bring back Xfce was driven by user feedback. Some users were reluctant to adopt Enlightenment after the distribution’s earlier desktop transition, and the new release offers both environments without abandoning the existing Enlightenment integration.

The two desktops share ConnMan for network connectivity, the Xfce application menu, similar panel layouts, and matching keyboard shortcuts. Moreover, a new Mosaic theme provides a consistent appearance across both environments.

Another change is the introduction of a dedicated package repository, replacing the previous web-based package archive. It is divided into three components: Desktop Enlightenment for AV Linux themes and configurations, Desktop Moksha for MX Moksha-specific packages, and Main for multimedia applications and plugins shared by both distributions.

The release also introduces in-house packaging of the Enlightenment stack, including EFL 1.29.0, Enlightenment 0.28, and associated applications and modules. Updated applications include the Evisum system monitor, Elaro IRC client, Eclair music player, and Equation calculator. MX Moksha, meanwhile, receives Moksha 4.2, along with fixes for suspend and hibernate functionality.

Under the hood, AV Linux 25.3 ships with the Liquorix kernel 7.3.4. The updated multimedia software selection includes Ardour 9.10, REAPER 7.85 as a demo, Audacity 4.0.2, and Cinelerra-GG. New audio plugins, including Pitchnet, are also available through the repository.

Several refinements have been made to the distribution’s file actions, including crop and preview functionality for the video upscaler. A new MX Linux utility for verifying ISO signatures is included as well.

One important consideration for existing users is that the extensive package restructuring requires a fresh installation to obtain the complete AV Linux 25.3 experience, including the new desktop configurations and repository integration.

However, users running AV Linux or MX Moksha 25 through 25.2 can enable the new Main repository without reinstalling. This provides access to updated multimedia applications, plugins, and file actions, although the new themes and desktop configurations will not be included.

Finally, the developer has discontinued XLibre ISO builds, citing the additional maintenance requirements and limited VPS storage capacity. Future package updates will also be distributed through the new repository rather than the old web archive.

For more information, see the announcement.

AV Linux 25.3, a Debian-based Linux distro for multimedia content creators, has been released, marking the return of Xfce as a fully integrated desktop environment alongside Enlightenment. AV Linux now boots into Xfce by default, but users can switch to Enlightenment from the LightDM login screen.

According to developer Glen MacArthur, the decision to bring back Xfce was driven by user feedback. Some users were reluctant to adopt Enlightenment after the distribution’s earlier desktop transition, and the new release offers both environments without abandoning the existing Enlightenment integration.

The two desktops share ConnMan for network connectivity, the Xfce application menu, similar panel layouts, and matching keyboard shortcuts. Moreover, a new Mosaic theme provides a consistent appearance across both environments.

Another change is the introduction of a dedicated package repository, replacing the previous web-based package archive. It is divided into three components: Desktop Enlightenment for AV Linux themes and configurations, Desktop Moksha for MX Moksha-specific packages, and Main for multimedia applications and plugins shared by both distributions.

The release also introduces in-house packaging of the Enlightenment stack, including EFL 1.29.0, Enlightenment 0.28, and associated applications and modules. Updated applications include the Evisum system monitor, Elaro IRC client, Eclair music player, and Equation calculator. MX Moksha, meanwhile, receives Moksha 4.2, along with fixes for suspend and hibernate functionality.

Under the hood, AV Linux 25.3 ships with the Liquorix kernel 7.3.4. The updated multimedia software selection includes Ardour 9.10, REAPER 7.85 as a demo, Audacity 4.0.2, and Cinelerra-GG. New audio plugins, including Pitchnet, are also available through the repository.

Several refinements have been made to the distribution’s file actions, including crop and preview functionality for the video upscaler. A new MX Linux utility for verifying ISO signatures is included as well.

One important consideration for existing users is that the extensive package restructuring requires a fresh installation to obtain the complete AV Linux 25.3 experience, including the new desktop configurations and repository integration.

However, users running AV Linux or MX Moksha 25 through 25.2 can enable the new Main repository without reinstalling. This provides access to updated multimedia applications, plugins, and file actions, although the new themes and desktop configurations will not be included.

Finally, the developer has discontinued XLibre ISO builds, citing the additional maintenance requirements and limited VPS storage capacity. Future package updates will also be distributed through the new repository rather than the old web archive.

For more information, see the announcement.

0

Rocky Linux 10.3 Released with Kernel 6.12, GCC 16, and Security Updates

Linuxiac Rocky Linux 10.3 Released with Kernel 6.12, GCC 16, and Security Updates linuxiac.com
preview

Rocky Linux 10.3 (Red Quartz) has been officially released following the Red Hat Enterprise Linux 10.3 release on November 11. The new version arrives alongside AlmaLinux 10.3, also released today, giving users two updated free RHEL-compatible options.

As expected, Rocky Linux 10.3 is built around Linux kernel 6.12, specifically version 6.12.0-264.16.1. Several kernel components have been updated beyond that baseline. The eBPF subsystem and perf tools are rebased to Linux 6.19, while memory management improvements include newer CXL support and changes to compressed swap handling.

Hardware support has also been improved, particularly for Intel platforms, while AMD’s amdxdna driver for Neural Processing Units (NPUs) is now available as a Technology Preview.

On the development side, Rocky Linux 10.3 introduces GCC Toolset 16, featuring GCC 16.2 and Binutils 2.46, alongside LLVM 22.1.8. The update also includes Rust 1.97, Go 1.27.3, and GDB 17.2, giving developers access to newer language features, debugging capabilities, and compiler improvements.

Regarding security, Libreswan 5.4 introduces post-quantum key exchange support through ML-KEM-768 and ML-KEM-1024, while SSH connections operating in FIPS mode now support and prefer hybrid post-quantum key exchange algorithms.

Other security-related updates include Keylime 7.14.3, which improves remote attestation capabilities, and fapolicyd 2.0.1, which introduces parallel policy processing and transactional updates. OpenSC 0.27.1 adds PKCS #11 3.2 support, while the updated Audit 4.2.1 provides additional capabilities for secure remote logging.

System monitoring also receives updates, with Grafana 12.4.3 introducing a redesigned dashboard architecture and improvements to unified alerting. Performance Co-Pilot 7.1.5 adds automatic archive repair and additional performance metrics.

For administrators working with system images, the image-builder command-line interface is now generally available. The web-based image builder can generate bootc-compatible images from locally available base images, while Kickstart gains additional certificate-handling capabilities during installation.

There are several compatibility changes worth mentioning. WEP wireless security support has been removed, along with the ZBUD compressed page allocator. Grafana also drops legacy alerting and AngularJS plugin support, which could affect existing monitoring configurations.

Regarding supported architectures, Rocky Linux 10.3 is available for x86-64-v3, ARM64, RISC-V, POWER10 and newer (ppc64le), and IBM z15 and newer. As with previous Rocky Linux 10 releases, older x86-64-v2 processors are not supported.

Existing Rocky Linux 10 users can upgrade to version 10.3 using the standard sudo dnf -y upgrade command or graphical update tools. However, upgrades from Rocky Linux 8 or 9 to version 10 are not officially supported, with a fresh installation recommended instead.

Installation ISOs, container images, cloud images, and live images are available from the Rocky Linux downloads page. For more information, see the official announcement.

Rocky Linux 10.3 (Red Quartz) has been officially released following the Red Hat Enterprise Linux 10.3 release on November 11. The new version arrives alongside AlmaLinux 10.3, also released today, giving users two updated free RHEL-compatible options.

As expected, Rocky Linux 10.3 is built around Linux kernel 6.12, specifically version 6.12.0-264.16.1. Several kernel components have been updated beyond that baseline. The eBPF subsystem and perf tools are rebased to Linux 6.19, while memory management improvements include newer CXL support and changes to compressed swap handling.

Hardware support has also been improved, particularly for Intel platforms, while AMD’s amdxdna driver for Neural Processing Units (NPUs) is now available as a Technology Preview.

On the development side, Rocky Linux 10.3 introduces GCC Toolset 16, featuring GCC 16.2 and Binutils 2.46, alongside LLVM 22.1.8. The update also includes Rust 1.97, Go 1.27.3, and GDB 17.2, giving developers access to newer language features, debugging capabilities, and compiler improvements.

Regarding security, Libreswan 5.4 introduces post-quantum key exchange support through ML-KEM-768 and ML-KEM-1024, while SSH connections operating in FIPS mode now support and prefer hybrid post-quantum key exchange algorithms.

Other security-related updates include Keylime 7.14.3, which improves remote attestation capabilities, and fapolicyd 2.0.1, which introduces parallel policy processing and transactional updates. OpenSC 0.27.1 adds PKCS #11 3.2 support, while the updated Audit 4.2.1 provides additional capabilities for secure remote logging.

System monitoring also receives updates, with Grafana 12.4.3 introducing a redesigned dashboard architecture and improvements to unified alerting. Performance Co-Pilot 7.1.5 adds automatic archive repair and additional performance metrics.

For administrators working with system images, the image-builder command-line interface is now generally available. The web-based image builder can generate bootc-compatible images from locally available base images, while Kickstart gains additional certificate-handling capabilities during installation.

There are several compatibility changes worth mentioning. WEP wireless security support has been removed, along with the ZBUD compressed page allocator. Grafana also drops legacy alerting and AngularJS plugin support, which could affect existing monitoring configurations.

Regarding supported architectures, Rocky Linux 10.3 is available for x86-64-v3, ARM64, RISC-V, POWER10 and newer (ppc64le), and IBM z15 and newer. As with previous Rocky Linux 10 releases, older x86-64-v2 processors are not supported.

Existing Rocky Linux 10 users can upgrade to version 10.3 using the standard sudo dnf -y upgrade command or graphical update tools. However, upgrades from Rocky Linux 8 or 9 to version 10 are not officially supported, with a fresh installation recommended instead.

Installation ISOs, container images, cloud images, and live images are available from the Rocky Linux downloads page. For more information, see the official announcement.

0

Print settings vs print dialogues

preview

I feel like I’m missing something, and possibly have been gaslighting myself for a while.

I just got a Brother mono printer and logged into its web config to set it for double sided printing and a few other things. I always thought this was better than using the os printer config gui to set defaults.

When I went to print from LibreWriter (from mint) I needed single sided instead. Oddly the print dialogue said single sided. So I hit print expecting single sided, but it came out double sided.

There were similar issues with the old printer i.e. things not coming out as sent from whatever application.

How do I make sure that what I’m seeing in a print dialogue (from any given application) is what will come out.

I feel like I’m missing something, and possibly have been gaslighting myself for a while.

I just got a Brother mono printer and logged into its web config to set it for double sided printing and a few other things. I always thought this was better than using the os printer config gui to set defaults.

When I went to print from LibreWriter (from mint) I needed single sided instead. Oddly the print dialogue said single sided. So I hit print expecting single sided, but it came out double sided.

There were similar issues with the old printer i.e. things not coming out as sent from whatever application.

How do I make sure that what I’m seeing in a print dialogue (from any given application) is what will come out.

0

AlmaLinux OS 10.3 Released as Free Alternative to Red Hat Enterprise Linux 10.3

9to5Linux AlmaLinux OS 10.3 Released as Free Alternative to Red Hat Enterprise Linux 10.3 - 9to5Linux 9to5linux.com
preview

The AlmaLinux OS Foundation announced today the release and general availability of AlmaLinux OS 10.3 (codename Mauve Lion) as the second point release of the latest AlmaLinux OS 10 series, based on Red Hat Enterprise Linux 10.3.

Coming five and a half months after AlmaLinux OS 10.2, the AlmaLinux OS 10.3 release is based on Red Hat Enterprise Linux 10.3 and brings back the ModSecurity web application firewall and the OWASP Core Rule Set (CRS). ModSecurity 2.9.14 with CRS 4.22 is included in the release.

According to the devs, CRS 4 reorganized the rule set, so if you’re bringing rules or tuning over from an AlmaLinux 9 server, plan to review them before you put AlmaLinux OS 10 in front of production traffic.

AlmaLinux OS 10.3 also ships with the Podman 6 container tool, which moves the vendor default configuration from /etc/containers to /usr/share/containers. Moreover, rootful and rootless storage settings now live in separate drop-in directories.

This release also introduces performance enhancements, updated development tools, and improved security. The toolchain has been updated as well to GCC 16, LLVM 22, Rust 1.97, Go 1.27, GDB 17.2, and Node.js 26. Security updates include fapolicyd 2.0, Keylime 7.14, audit 4.2, and libreswan 5.4.

You can download the AlmaLinux OS 10.3 release right now from the official website as installation ISO images for 64-bit (x86_64 and x86_64_v2), AArch64 (ARM64), PowerPC 64-bit Little Endian (ppc64le), and IBM System Z (s390x) architectures. Live and cloud images will be available as well, along with containers.

As expected, this release targets new users and those who want to perform a fresh installation. Existing AlmaLinux OS users can upgrade their installations to the new version by running the sudo dnf update command in a terminal emulator or virtual console.

Also today, the AlmaLinux OS Foundation released AlmaLinux OS 9.9 “Chartreuse Bobcat” as a free alternative to Red Hat Enterprise Linux 9.9, which keeps the ALESCo-approved kernel fix shipped in AlmaLinux OS 9.8, which stops systemd and ps from using excessive CPU during task cleanup. Check out the release notes for more details.

The AlmaLinux OS Foundation announced today the release and general availability of AlmaLinux OS 10.3 (codename Mauve Lion) as the second point release of the latest AlmaLinux OS 10 series, based on Red Hat Enterprise Linux 10.3.

Coming five and a half months after AlmaLinux OS 10.2, the AlmaLinux OS 10.3 release is based on Red Hat Enterprise Linux 10.3 and brings back the ModSecurity web application firewall and the OWASP Core Rule Set (CRS). ModSecurity 2.9.14 with CRS 4.22 is included in the release.

According to the devs, CRS 4 reorganized the rule set, so if you’re bringing rules or tuning over from an AlmaLinux 9 server, plan to review them before you put AlmaLinux OS 10 in front of production traffic.

AlmaLinux OS 10.3 also ships with the Podman 6 container tool, which moves the vendor default configuration from /etc/containers to /usr/share/containers. Moreover, rootful and rootless storage settings now live in separate drop-in directories.

This release also introduces performance enhancements, updated development tools, and improved security. The toolchain has been updated as well to GCC 16, LLVM 22, Rust 1.97, Go 1.27, GDB 17.2, and Node.js 26. Security updates include fapolicyd 2.0, Keylime 7.14, audit 4.2, and libreswan 5.4.

You can download the AlmaLinux OS 10.3 release right now from the official website as installation ISO images for 64-bit (x86_64 and x86_64_v2), AArch64 (ARM64), PowerPC 64-bit Little Endian (ppc64le), and IBM System Z (s390x) architectures. Live and cloud images will be available as well, along with containers.

As expected, this release targets new users and those who want to perform a fresh installation. Existing AlmaLinux OS users can upgrade their installations to the new version by running the sudo dnf update command in a terminal emulator or virtual console.

Also today, the AlmaLinux OS Foundation released AlmaLinux OS 9.9 “Chartreuse Bobcat” as a free alternative to Red Hat Enterprise Linux 9.9, which keeps the ALESCo-approved kernel fix shipped in AlmaLinux OS 9.8, which stops systemd and ps from using excessive CPU during task cleanup. Check out the release notes for more details.

0

Manjaro Linux Has a Non-Profit Now

It's FOSS Manjaro Linux Has a Non-Profit Now itsfoss.com
preview

The Manjaro team has registered its own non-profit in Germany. Called Manjaro Project e.V., it has seven founding members and is independent of the commercial-oriented Manjaro GmbH & Co. KG entity.

You might remember earlier this year, in March, a group of team members published a manifesto calling for the project to be split from the company, with a strike following soon after.

While this was announced on the Manjaro Linux forum and not on the main project webpage, the registration is already visible in the German register portal, under the Berlin court.

An e.V.?

An e.V. (eingetragener Verein) is a registered association under German law. It is entered in a register kept by the local court, and its purpose cannot be running a commercial business. Registering gives it its own legal identity, separate from the people in it.

That identity matters to the developers because it lets them hold things as a group.

The manifesto asked for equal ownership among members and open voting on big decisions instead of everything being centered on one person. It now means there’s a body that could own the assets if they’re handed over.

Manjaro GmbH & Co. KG is a different kind of body. A GmbH & Co. KG is a limited partnership where a GmbH takes on the personal liability, with the GmbH’s managing directors handling the running of the business.

Stating the obvious, Manjaro now has two separate bodies behind it, and it’s interesting to see how the project ended up in such a situation.

How Manjaro got here

Manjaro has been a German company since 2019. Way back in April 2024, that company announced a management change when Bernhard Landauer stepped away from the company to focus on other work and a new CTO joined to replace him.

Then came the Manjaro 2.0 Manifesto in March, where signatories said the leadership’s priorities didn’t line up with what the developers and community wanted.

Project lead Philip Müller replied, saying he had no personal objection to an association but wouldn’t help set it up and that any asset transfer would have to be discussed closely with the company.

The team has since managed to push out the most recent Testing and Stable updates without Müller being involved.

What now?

The manifesto suggested handing over assets like the manjaro.org domain, the forum, and community donations. According to the team, no transfer of company assets has happened yet.

Before that, the e.V. has some groundwork to do, such as tidying up its statutes, bringing in more members, and opening its own bank account. Talks with the company come after.

For end users, I don’t expect them to be affected in any major way. This kind of feels like a takeover, but a gentle one so far. The situation for donors who had set up recurring payments is a bit hazy.

You see, donations still go to accounts under the company’s control, possibly Müller’s too, and the e.V. hasn’t settled on whether to start fresh accounts or take over the current ones.

Basically, there’s no new recipient to switch to yet, and the team hasn’t said when that gets decided. A second announcement confirming that assets have moved is what I’d watch for, since that’s when the split becomes more than a register entry.

Then there’s the Orange Pi Neo, a handheld Orange Pi built with Manjaro that was put on hold in March because of skyrocketing memory and SSD prices. The announcement doesn’t say who handles partner projects like it, so that’s an open question.

The Manjaro team has registered its own non-profit in Germany. Called Manjaro Project e.V., it has seven founding members and is independent of the commercial-oriented Manjaro GmbH & Co. KG entity.

You might remember earlier this year, in March, a group of team members published a manifesto calling for the project to be split from the company, with a strike following soon after.

While this was announced on the Manjaro Linux forum and not on the main project webpage, the registration is already visible in the German register portal, under the Berlin court.

An e.V.?

An e.V. (eingetragener Verein) is a registered association under German law. It is entered in a register kept by the local court, and its purpose cannot be running a commercial business. Registering gives it its own legal identity, separate from the people in it.

That identity matters to the developers because it lets them hold things as a group.

The manifesto asked for equal ownership among members and open voting on big decisions instead of everything being centered on one person. It now means there’s a body that could own the assets if they’re handed over.

Manjaro GmbH & Co. KG is a different kind of body. A GmbH & Co. KG is a limited partnership where a GmbH takes on the personal liability, with the GmbH’s managing directors handling the running of the business.

Stating the obvious, Manjaro now has two separate bodies behind it, and it’s interesting to see how the project ended up in such a situation.

How Manjaro got here

Manjaro has been a German company since 2019. Way back in April 2024, that company announced a management change when Bernhard Landauer stepped away from the company to focus on other work and a new CTO joined to replace him.

Then came the Manjaro 2.0 Manifesto in March, where signatories said the leadership’s priorities didn’t line up with what the developers and community wanted.

Project lead Philip Müller replied, saying he had no personal objection to an association but wouldn’t help set it up and that any asset transfer would have to be discussed closely with the company.

The team has since managed to push out the most recent Testing and Stable updates without Müller being involved.

What now?

The manifesto suggested handing over assets like the manjaro.org domain, the forum, and community donations. According to the team, no transfer of company assets has happened yet.

Before that, the e.V. has some groundwork to do, such as tidying up its statutes, bringing in more members, and opening its own bank account. Talks with the company come after.

For end users, I don’t expect them to be affected in any major way. This kind of feels like a takeover, but a gentle one so far. The situation for donors who had set up recurring payments is a bit hazy.

You see, donations still go to accounts under the company’s control, possibly Müller’s too, and the e.V. hasn’t settled on whether to start fresh accounts or take over the current ones.

Basically, there’s no new recipient to switch to yet, and the team hasn’t said when that gets decided. A second announcement confirming that assets have moved is what I’d watch for, since that’s when the split becomes more than a register entry.

Then there’s the Orange Pi Neo, a handheld Orange Pi built with Manjaro that was put on hold in March because of skyrocketing memory and SSD prices. The announcement doesn’t say who handles partner projects like it, so that’s an open question.

0

AlmaLinux OS 10.3 Released as Free Alternative to Red Hat Enterprise Linux 10.3

9to5Linux AlmaLinux OS 10.3 Released as Free Alternative to Red Hat Enterprise Linux 10.3 - 9to5Linux 9to5linux.com
preview

The AlmaLinux OS Foundation announced today the release and general availability of AlmaLinux OS 10.3 (codename Mauve Lion) as the second point release of the latest AlmaLinux OS 10 series, based on Red Hat Enterprise Linux 10.3.

Coming five and a half months after AlmaLinux OS 10.2, the AlmaLinux OS 10.3 release is based on Red Hat Enterprise Linux 10.3 and brings back the ModSecurity web application firewall and the OWASP Core Rule Set (CRS). ModSecurity 2.9.14 with CRS 4.22 is included in the release.

According to the devs, CRS 4 reorganized the rule set, so if you’re bringing rules or tuning over from an AlmaLinux 9 server, plan to review them before you put AlmaLinux OS 10 in front of production traffic.

AlmaLinux OS 10.3 also ships with the Podman 6 container tool, which moves the vendor default configuration from /etc/containers to /usr/share/containers. Moreover, rootful and rootless storage settings now live in separate drop-in directories.

This release also introduces performance enhancements, updated development tools, and improved security. The toolchain has been updated as well to GCC 16, LLVM 22, Rust 1.97, Go 1.27, GDB 17.2, and Node.js 26. Security updates include fapolicyd 2.0, Keylime 7.14, audit 4.2, and libreswan 5.4.

You can download the AlmaLinux OS 10.3 release right now from the official website as installation ISO images for 64-bit (x86_64 and x86_64_v2), AArch64 (ARM64), PowerPC 64-bit Little Endian (ppc64le), and IBM System Z (s390x) architectures. Live and cloud images will be available as well, along with containers.

As expected, this release targets new users and those who want to perform a fresh installation. Existing AlmaLinux OS users can upgrade their installations to the new version by running the sudo dnf update command in a terminal emulator or virtual console.

Also today, the AlmaLinux OS Foundation released AlmaLinux OS 9.9 “Chartreuse Bobcat” as a free alternative to Red Hat Enterprise Linux 9.9, which keeps the ALESCo-approved kernel fix shipped in AlmaLinux OS 9.8, which stops systemd and ps from using excessive CPU during task cleanup. Check out the release notes for more details.

The AlmaLinux OS Foundation announced today the release and general availability of AlmaLinux OS 10.3 (codename Mauve Lion) as the second point release of the latest AlmaLinux OS 10 series, based on Red Hat Enterprise Linux 10.3.

Coming five and a half months after AlmaLinux OS 10.2, the AlmaLinux OS 10.3 release is based on Red Hat Enterprise Linux 10.3 and brings back the ModSecurity web application firewall and the OWASP Core Rule Set (CRS). ModSecurity 2.9.14 with CRS 4.22 is included in the release.

According to the devs, CRS 4 reorganized the rule set, so if you’re bringing rules or tuning over from an AlmaLinux 9 server, plan to review them before you put AlmaLinux OS 10 in front of production traffic.

AlmaLinux OS 10.3 also ships with the Podman 6 container tool, which moves the vendor default configuration from /etc/containers to /usr/share/containers. Moreover, rootful and rootless storage settings now live in separate drop-in directories.

This release also introduces performance enhancements, updated development tools, and improved security. The toolchain has been updated as well to GCC 16, LLVM 22, Rust 1.97, Go 1.27, GDB 17.2, and Node.js 26. Security updates include fapolicyd 2.0, Keylime 7.14, audit 4.2, and libreswan 5.4.

You can download the AlmaLinux OS 10.3 release right now from the official website as installation ISO images for 64-bit (x86_64 and x86_64_v2), AArch64 (ARM64), PowerPC 64-bit Little Endian (ppc64le), and IBM System Z (s390x) architectures. Live and cloud images will be available as well, along with containers.

As expected, this release targets new users and those who want to perform a fresh installation. Existing AlmaLinux OS users can upgrade their installations to the new version by running the sudo dnf update command in a terminal emulator or virtual console.

Also today, the AlmaLinux OS Foundation released AlmaLinux OS 9.9 “Chartreuse Bobcat” as a free alternative to Red Hat Enterprise Linux 9.9, which keeps the ALESCo-approved kernel fix shipped in AlmaLinux OS 9.8, which stops systemd and ps from using excessive CPU during task cleanup. Check out the release notes for more details.

0

Manjaro Linux Has a Non-Profit Now

It's FOSS Manjaro Linux Has a Non-Profit Now itsfoss.com
preview

The Manjaro team has registered its own non-profit in Germany. Called Manjaro Project e.V., it has seven founding members and is independent of the commercial-oriented Manjaro GmbH & Co. KG entity.

You might remember earlier this year, in March, a group of team members published a manifesto calling for the project to be split from the company, with a strike following soon after.

While this was announced on the Manjaro Linux forum and not on the main project webpage, the registration is already visible in the German register portal, under the Berlin court.

An e.V.?

An e.V. (eingetragener Verein) is a registered association under German law. It is entered in a register kept by the local court, and its purpose cannot be running a commercial business. Registering gives it its own legal identity, separate from the people in it.

That identity matters to the developers because it lets them hold things as a group.

The manifesto asked for equal ownership among members and open voting on big decisions instead of everything being centered on one person. It now means there’s a body that could own the assets if they’re handed over.

Manjaro GmbH & Co. KG is a different kind of body. A GmbH & Co. KG is a limited partnership where a GmbH takes on the personal liability, with the GmbH’s managing directors handling the running of the business.

Stating the obvious, Manjaro now has two separate bodies behind it, and it’s interesting to see how the project ended up in such a situation.

How Manjaro got here

Manjaro has been a German company since 2019. Way back in April 2024, that company announced a management change when Bernhard Landauer stepped away from the company to focus on other work and a new CTO joined to replace him.

Then came the Manjaro 2.0 Manifesto in March, where signatories said the leadership’s priorities didn’t line up with what the developers and community wanted.

Project lead Philip Müller replied, saying he had no personal objection to an association but wouldn’t help set it up and that any asset transfer would have to be discussed closely with the company.

The team has since managed to push out the most recent Testing and Stable updates without Müller being involved.

What now?

The manifesto suggested handing over assets like the manjaro.org domain, the forum, and community donations. According to the team, no transfer of company assets has happened yet.

Before that, the e.V. has some groundwork to do, such as tidying up its statutes, bringing in more members, and opening its own bank account. Talks with the company come after.

For end users, I don’t expect them to be affected in any major way. This kind of feels like a takeover, but a gentle one so far. The situation for donors who had set up recurring payments is a bit hazy.

You see, donations still go to accounts under the company’s control, possibly Müller’s too, and the e.V. hasn’t settled on whether to start fresh accounts or take over the current ones.

Basically, there’s no new recipient to switch to yet, and the team hasn’t said when that gets decided. A second announcement confirming that assets have moved is what I’d watch for, since that’s when the split becomes more than a register entry.

Then there’s the Orange Pi Neo, a handheld Orange Pi built with Manjaro that was put on hold in March because of skyrocketing memory and SSD prices. The announcement doesn’t say who handles partner projects like it, so that’s an open question.

The Manjaro team has registered its own non-profit in Germany. Called Manjaro Project e.V., it has seven founding members and is independent of the commercial-oriented Manjaro GmbH & Co. KG entity.

You might remember earlier this year, in March, a group of team members published a manifesto calling for the project to be split from the company, with a strike following soon after.

While this was announced on the Manjaro Linux forum and not on the main project webpage, the registration is already visible in the German register portal, under the Berlin court.

An e.V.?

An e.V. (eingetragener Verein) is a registered association under German law. It is entered in a register kept by the local court, and its purpose cannot be running a commercial business. Registering gives it its own legal identity, separate from the people in it.

That identity matters to the developers because it lets them hold things as a group.

The manifesto asked for equal ownership among members and open voting on big decisions instead of everything being centered on one person. It now means there’s a body that could own the assets if they’re handed over.

Manjaro GmbH & Co. KG is a different kind of body. A GmbH & Co. KG is a limited partnership where a GmbH takes on the personal liability, with the GmbH’s managing directors handling the running of the business.

Stating the obvious, Manjaro now has two separate bodies behind it, and it’s interesting to see how the project ended up in such a situation.

How Manjaro got here

Manjaro has been a German company since 2019. Way back in April 2024, that company announced a management change when Bernhard Landauer stepped away from the company to focus on other work and a new CTO joined to replace him.

Then came the Manjaro 2.0 Manifesto in March, where signatories said the leadership’s priorities didn’t line up with what the developers and community wanted.

Project lead Philip Müller replied, saying he had no personal objection to an association but wouldn’t help set it up and that any asset transfer would have to be discussed closely with the company.

The team has since managed to push out the most recent Testing and Stable updates without Müller being involved.

What now?

The manifesto suggested handing over assets like the manjaro.org domain, the forum, and community donations. According to the team, no transfer of company assets has happened yet.

Before that, the e.V. has some groundwork to do, such as tidying up its statutes, bringing in more members, and opening its own bank account. Talks with the company come after.

For end users, I don’t expect them to be affected in any major way. This kind of feels like a takeover, but a gentle one so far. The situation for donors who had set up recurring payments is a bit hazy.

You see, donations still go to accounts under the company’s control, possibly Müller’s too, and the e.V. hasn’t settled on whether to start fresh accounts or take over the current ones.

Basically, there’s no new recipient to switch to yet, and the team hasn’t said when that gets decided. A second announcement confirming that assets have moved is what I’d watch for, since that’s when the split becomes more than a register entry.

Then there’s the Orange Pi Neo, a handheld Orange Pi built with Manjaro that was put on hold in March because of skyrocketing memory and SSD prices. The announcement doesn’t say who handles partner projects like it, so that’s an open question.

0

Fwupd 2.1.10 Brings Fixes, New Synaptics Touchpad Supported

Fwupd 2.1.10 Brings Fixes, New Synaptics Touchpad Supported www.phoronix.com
preview

Lead Fwupd/LVFS developer Richard Hughes of Red Hat kicked off the new week by releasing Fwupd 2.1.10 as the newest stable release for performing firmware updates on Linux.

Fwupd 2.1.10 ships with a wide variety of fixes. This takes care of various bugs reported by users as well as AI/LLM detected issues in the codebase. Nothing too particularly exciting on the fixes side unless you were personally impacted by one of the bugs.

On the new hardware support side, the only addition with Fwupd 2.1.10 is introducing support for the Synaptics 96F1 touchpad.

The full list of Fwupd 2.1.10 changes can be found via GitHub.

Lead Fwupd/LVFS developer Richard Hughes of Red Hat kicked off the new week by releasing Fwupd 2.1.10 as the newest stable release for performing firmware updates on Linux.

Fwupd 2.1.10 ships with a wide variety of fixes. This takes care of various bugs reported by users as well as AI/LLM detected issues in the codebase. Nothing too particularly exciting on the fixes side unless you were personally impacted by one of the bugs.

On the new hardware support side, the only addition with Fwupd 2.1.10 is introducing support for the Synaptics 96F1 touchpad.

The full list of Fwupd 2.1.10 changes can be found via GitHub.

0

Fwupd 2.1.10 Brings Fixes, New Synaptics Touchpad Supported

Fwupd 2.1.10 Brings Fixes, New Synaptics Touchpad Supported www.phoronix.com
preview

Lead Fwupd/LVFS developer Richard Hughes of Red Hat kicked off the new week by releasing Fwupd 2.1.10 as the newest stable release for performing firmware updates on Linux.

Fwupd 2.1.10 ships with a wide variety of fixes. This takes care of various bugs reported by users as well as AI/LLM detected issues in the codebase. Nothing too particularly exciting on the fixes side unless you were personally impacted by one of the bugs.

On the new hardware support side, the only addition with Fwupd 2.1.10 is introducing support for the Synaptics 96F1 touchpad.

The full list of Fwupd 2.1.10 changes can be found via GitHub.

Lead Fwupd/LVFS developer Richard Hughes of Red Hat kicked off the new week by releasing Fwupd 2.1.10 as the newest stable release for performing firmware updates on Linux.

Fwupd 2.1.10 ships with a wide variety of fixes. This takes care of various bugs reported by users as well as AI/LLM detected issues in the codebase. Nothing too particularly exciting on the fixes side unless you were personally impacted by one of the bugs.

On the new hardware support side, the only addition with Fwupd 2.1.10 is introducing support for the Synaptics 96F1 touchpad.

The full list of Fwupd 2.1.10 changes can be found via GitHub.

0

Kagi is abandoning its Orion browser on Windows and Linux, but the code is going open source

How-To Geek Kagi is abandoning its Orion browser on Windows and Linux, but the code is going open source www.howtogeek.com
preview

“Kagi’s Orion browser for Linux was a promising development, but now it’s in the hands of the open-source community.


in early October of this year (2026), Kagi announced they are dropping development of their Orion browser for Windows and Linux. Instead, they decided to shift their internal focus to further developing it for macOS and iOS, because a lot of its user base is there.”

“Kagi’s Orion browser for Linux was a promising development, but now it’s in the hands of the open-source community.


in early October of this year (2026), Kagi announced they are dropping development of their Orion browser for Windows and Linux. Instead, they decided to shift their internal focus to further developing it for macOS and iOS, because a lot of its user base is there.”

0

am I the only one who thinks of codeberg and similar platforms like a file exchanger or a cloud storage?

preview

And even if I am, what prevents me from using it as such? It didn’t seem like there’s some kind of file size restriction or whatever. Maybe there’s no end-to-end encryption but if put that aside, I don’t see any problems with it

And even if I am, what prevents me from using it as such? It didn’t seem like there’s some kind of file size restriction or whatever. Maybe there’s no end-to-end encryption but if put that aside, I don’t see any problems with it

0

Librem 5 second-gen $1599 RISC-V Linux phone - OMG! Ubuntu

OMG! Ubuntu Purism announces second-gen Librem 5 Linux phone - OMG! Ubuntu www.omgubuntu.co.uk
preview

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.

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.

0

KDE Plasma 6.9 Will Launch XWayland Only When Needed

Linuxiac KDE Plasma 6.9 Will Launch XWayland Only When Needed linuxiac.com
preview

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.

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.

0

Librem 5 second-gen $1599 RISC-V Linux phone - OMG! Ubuntu

OMG! Ubuntu Purism announces second-gen Librem 5 Linux phone - OMG! Ubuntu www.omgubuntu.co.uk
preview

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.

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.

0

KDE Plasma 6.9 Will Launch XWayland Only When Needed

Linuxiac KDE Plasma 6.9 Will Launch XWayland Only When Needed linuxiac.com
preview

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.

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.

0

Zswap do not write uncompressible pages to disk when RAM is free

preview

edit: I decreased swappiness and increased vfs cache pressure to reduce the amount of swapping in general.

I’m noticing that a very intended behavior of Zswap is to write pages to disk when they don’t cleanly compress (or for some other reason). How can I configure it to act kind of like Zram but only writeback when the system is actually out of RAM?

grep -R . /sys/kernel/debug/zswap/
/sys/kernel/debug/zswap/stored_incompressible_pages:8224
/sys/kernel/debug/zswap/stored_pages:218538
/sys/kernel/debug/zswap/pool_total_size:229318656
/sys/kernel/debug/zswap/written_back_pages:251371
/sys/kernel/debug/zswap/decompress_fail:0
/sys/kernel/debug/zswap/reject_compress_poor:0
/sys/kernel/debug/zswap/reject_compress_fail:0
/sys/kernel/debug/zswap/reject_kmemcache_fail:0
/sys/kernel/debug/zswap/reject_alloc_fail:0
/sys/kernel/debug/zswap/reject_reclaim_fail:0
/sys/kernel/debug/zswap/pool_limit_hit:0

My parameters: zswap.enabled=1 zswap.compressor=zstd zswap.shrinker_enabled=0 zswap.max_pool_percent=20. Swappiness is at default value.

edit: I decreased swappiness and increased vfs cache pressure to reduce the amount of swapping in general.

I’m noticing that a very intended behavior of Zswap is to write pages to disk when they don’t cleanly compress (or for some other reason). How can I configure it to act kind of like Zram but only writeback when the system is actually out of RAM?

grep -R . /sys/kernel/debug/zswap/
/sys/kernel/debug/zswap/stored_incompressible_pages:8224
/sys/kernel/debug/zswap/stored_pages:218538
/sys/kernel/debug/zswap/pool_total_size:229318656
/sys/kernel/debug/zswap/written_back_pages:251371
/sys/kernel/debug/zswap/decompress_fail:0
/sys/kernel/debug/zswap/reject_compress_poor:0
/sys/kernel/debug/zswap/reject_compress_fail:0
/sys/kernel/debug/zswap/reject_kmemcache_fail:0
/sys/kernel/debug/zswap/reject_alloc_fail:0
/sys/kernel/debug/zswap/reject_reclaim_fail:0
/sys/kernel/debug/zswap/pool_limit_hit:0

My parameters: zswap.enabled=1 zswap.compressor=zstd zswap.shrinker_enabled=0 zswap.max_pool_percent=20. Swappiness is at default value.

0

I really wanna use Linux but I don't know if my family could tolerate the alternative software!

preview

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

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

0

Linux Mint Installation Issues on a Lenovo Yoga C930

preview

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 :)

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 :)

0

Proton's official statement on AI use, MATE goes Wayland - Linux & Open Source News

play · tilvids.com
TILvids Proton's official statement on AI use, MATE goes Wayland - Linux & Open Source News tilvids.com
preview

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

blog.darlinghq.org/…/development-update-q4-2026/

Proton posts article about their security and Al use

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

Steam updates brings 64bit and better remote play

store.steampowered.com/news/…/678515036155543747

Valve adds framerate data as public info for Deck users

store.steampowered.com/news/…/685269801333948419

MATE gets its Wayland compositor

discourse.ubuntu.com/t/…/91698

Long time Linux maintainer steps back due to Al generated patches

www.phoronix.com/news/Lorenzo-Stoakes-Al-Flood

Asahi to switch licences, and progress report

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

Nexus Mods hiring a Linux dev

gamingonlinux.com/…/nexus-mods-hiring-for-a-linux…

Nvidia CEO resigns

…nvidia.com/…/nvidia-announces-ceo-transition

Tuxedo OS nears final beta

linuxiac.com/tuxedo-os-enters-final-beta-testing-…

Dolphin gets columns view, again

…kde.org/…/dolphin-gets-a-columns-view-again/

GoogleBook OS doesn’t seem great

androidcentral.com/…/lenovo-googlebook-15-review-…

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

blog.darlinghq.org/…/development-update-q4-2026/

Proton posts article about their security and Al use

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

Steam updates brings 64bit and better remote play

store.steampowered.com/news/…/678515036155543747

Valve adds framerate data as public info for Deck users

store.steampowered.com/news/…/685269801333948419

MATE gets its Wayland compositor

discourse.ubuntu.com/t/…/91698

Long time Linux maintainer steps back due to Al generated patches

www.phoronix.com/news/Lorenzo-Stoakes-Al-Flood

Asahi to switch licences, and progress report

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

Nexus Mods hiring a Linux dev

gamingonlinux.com/…/nexus-mods-hiring-for-a-linux…

Nvidia CEO resigns

…nvidia.com/…/nvidia-announces-ceo-transition

Tuxedo OS nears final beta

linuxiac.com/tuxedo-os-enters-final-beta-testing-…

Dolphin gets columns view, again

…kde.org/…/dolphin-gets-a-columns-view-again/

GoogleBook OS doesn’t seem great

androidcentral.com/…/lenovo-googlebook-15-review-…

0

Proton's official statement on AI use, MATE goes Wayland - Linux & Open Source News

play · tilvids.com
TILvids Proton's official statement on AI use, MATE goes Wayland - Linux & Open Source News tilvids.com
preview

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

blog.darlinghq.org/…/development-update-q4-2026/

Proton posts article about their security and Al use

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

Steam updates brings 64bit and better remote play

store.steampowered.com/news/…/678515036155543747

Valve adds framerate data as public info for Deck users

store.steampowered.com/news/…/685269801333948419

MATE gets its Wayland compositor

discourse.ubuntu.com/t/…/91698

Long time Linux maintainer steps back due to Al generated patches

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

Asahi to switch licences, and progress report

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

Nexus Mods hiring a Linux dev

gamingonlinux.com/…/nexus-mods-hiring-for-a-linux…

Nvidia CEO resigns

…nvidia.com/…/nvidia-announces-ceo-transition

Tuxedo OS nears final beta

linuxiac.com/tuxedo-os-enters-final-beta-testing-…

Dolphin gets columns view, again

…kde.org/…/dolphin-gets-a-columns-view-again/

GoogleBook OS doesn’t seem great

androidcentral.com/…/lenovo-googlebook-15-review-…

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

blog.darlinghq.org/…/development-update-q4-2026/

Proton posts article about their security and Al use

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

Steam updates brings 64bit and better remote play

store.steampowered.com/news/…/678515036155543747

Valve adds framerate data as public info for Deck users

store.steampowered.com/news/…/685269801333948419

MATE gets its Wayland compositor

discourse.ubuntu.com/t/…/91698

Long time Linux maintainer steps back due to Al generated patches

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

Asahi to switch licences, and progress report

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

Nexus Mods hiring a Linux dev

gamingonlinux.com/…/nexus-mods-hiring-for-a-linux…

Nvidia CEO resigns

…nvidia.com/…/nvidia-announces-ceo-transition

Tuxedo OS nears final beta

linuxiac.com/tuxedo-os-enters-final-beta-testing-…

Dolphin gets columns view, again

…kde.org/…/dolphin-gets-a-columns-view-again/

GoogleBook OS doesn’t seem great

androidcentral.com/…/lenovo-googlebook-15-review-…

0

KDE is hiring a developer with a focus for Plasma Mobile!

KDE e.V. Call for proposals - Software Engineer ev.kde.org
preview

cross-posted from: 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.

cross-posted from: 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.

0

KDE is hiring a developer with a focus for Plasma Mobile!

KDE e.V. Call for proposals - Software Engineer ev.kde.org
preview

cross-posted from: 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.

cross-posted from: 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.

0

A joke...

preview

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…

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…

0

systemd Gets Built-In System Reporting With systemd-report

Linuxiac systemd Gets Built-In System Reporting With systemd-report linuxiac.com
preview

Sorry if this has been posted before but couldn’t found it in my searches. (It’s from September 25)

The new systemd-report collects system facts and runtime metrics into unified, timestamped JSON reports for monitoring and fleet management.

systemd is getting a new reporting subsystem designed to collect both static system information and dynamic runtime metrics in one place.

Called systemd-report, the new tool gathers data from multiple metric provider services via a generic Varlink interface and combines it into a single timestamped JSON report. The work targets system and fleet management, where administrators need a consistent view of many machines.

The collected information is split into two groups. The first covers relatively static system “facts,” such as CPU architecture, hostname, kernel version, OS identification, installed RAM, CPU count, virtualization technology, TPM information, and other hardware or platform details.

The second covers changing runtime metrics like CPU and memory use, load averages, disk I/O, swap usage, system pressure, cgroup statistics, network interface states, systemd unit states, restart counters, queued jobs, and high-priority journal messages.

According to Lennart Poettering, the underlying metrics service was initially contributed by Meta with a focus on dynamic runtime information. The same interface was later extended to handle more static system facts as well, something Amutable is using for areas such as operating system deployment management.

Once gathered, systemd-report compiles all of this information into a consistent snapshot representing the state of the machine at a particular point in time.

The subsystem is designed for remote fleet management. Reports can be uploaded directly to an HTTPS server using PUT requests, letting organizations send system information to a central control plane. The setup includes periodic uploads via a systemd timer and reports triggered by events like system boot, reboot, or shutdown.

For security, reports can be cryptographically signed before being sent, and systemd currently provides three signing methods.

The simplest uses a software-generated asymmetric key stored locally. Systems with TPM hardware can produce a TPM quote covering platform measurements and the report data. A third option supports confidential-computing environments by generating a CPU TSM quote that ties the report to measurements of the secure virtual machine.

This makes systemd-report different from traditional monitoring tools like Prometheus and its node_exporter. While both expose similar information, systemd obtains data directly from lower-level OS components instead of relying on a separate scraping model.

More importantly, systemd-report focuses on complete, signed, timestamped snapshots rather than independent streams of metrics. Poettering notes that the two approaches are not mutually exclusive, and the new infrastructure could eventually provide the basis for integration between them.

The architecture is also intentionally extensible. Third-party projects can provide additional metrics or signing mechanisms simply by exposing the appropriate Varlink socket. These providers can be written in any programming language and only need to implement a small interface.

In other words, systemd-report is not just another command for displaying system information. It is shaping up as a broader reporting framework built directly into systemd, combining system facts, runtime metrics, secure signing, and remote reporting in a format suitable for managing everything from individual Linux machines to large server fleets.

For additional details, see Poettering’s announcement.

Sorry if this has been posted before but couldn’t found it in my searches. (It’s from September 25)

The new systemd-report collects system facts and runtime metrics into unified, timestamped JSON reports for monitoring and fleet management.

systemd is getting a new reporting subsystem designed to collect both static system information and dynamic runtime metrics in one place.

Called systemd-report, the new tool gathers data from multiple metric provider services via a generic Varlink interface and combines it into a single timestamped JSON report. The work targets system and fleet management, where administrators need a consistent view of many machines.

The collected information is split into two groups. The first covers relatively static system “facts,” such as CPU architecture, hostname, kernel version, OS identification, installed RAM, CPU count, virtualization technology, TPM information, and other hardware or platform details.

The second covers changing runtime metrics like CPU and memory use, load averages, disk I/O, swap usage, system pressure, cgroup statistics, network interface states, systemd unit states, restart counters, queued jobs, and high-priority journal messages.

According to Lennart Poettering, the underlying metrics service was initially contributed by Meta with a focus on dynamic runtime information. The same interface was later extended to handle more static system facts as well, something Amutable is using for areas such as operating system deployment management.

Once gathered, systemd-report compiles all of this information into a consistent snapshot representing the state of the machine at a particular point in time.

The subsystem is designed for remote fleet management. Reports can be uploaded directly to an HTTPS server using PUT requests, letting organizations send system information to a central control plane. The setup includes periodic uploads via a systemd timer and reports triggered by events like system boot, reboot, or shutdown.

For security, reports can be cryptographically signed before being sent, and systemd currently provides three signing methods.

The simplest uses a software-generated asymmetric key stored locally. Systems with TPM hardware can produce a TPM quote covering platform measurements and the report data. A third option supports confidential-computing environments by generating a CPU TSM quote that ties the report to measurements of the secure virtual machine.

This makes systemd-report different from traditional monitoring tools like Prometheus and its node_exporter. While both expose similar information, systemd obtains data directly from lower-level OS components instead of relying on a separate scraping model.

More importantly, systemd-report focuses on complete, signed, timestamped snapshots rather than independent streams of metrics. Poettering notes that the two approaches are not mutually exclusive, and the new infrastructure could eventually provide the basis for integration between them.

The architecture is also intentionally extensible. Third-party projects can provide additional metrics or signing mechanisms simply by exposing the appropriate Varlink socket. These providers can be written in any programming language and only need to implement a small interface.

In other words, systemd-report is not just another command for displaying system information. It is shaping up as a broader reporting framework built directly into systemd, combining system facts, runtime metrics, secure signing, and remote reporting in a format suitable for managing everything from individual Linux machines to large server fleets.

For additional details, see Poettering’s announcement.

0

qBitTorrent kills my VPN, Transmission does not. How to troubleshoot?

preview

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): pastebin.com/RtwDqiEN

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

journalctl qbit: pastebin.com/e2XCgGKy

journalctl PVPN: 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

~~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

UPDATE days later: nevermind, the issue was not fixed by anything other than reducing the amount of active torrents. Seems like PVPN doesn’t like me having 400+ active torrents, even though just a few of them are actively being seeded. Transmission did not show the same behaviour also because I only imported ~20 torrents to test. Guess you can’t really seed everything forever…

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): pastebin.com/RtwDqiEN

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

journalctl qbit: pastebin.com/e2XCgGKy

journalctl PVPN: 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

~~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

UPDATE days later: nevermind, the issue was not fixed by anything other than reducing the amount of active torrents. Seems like PVPN doesn’t like me having 400+ active torrents, even though just a few of them are actively being seeded. Transmission did not show the same behaviour also because I only imported ~20 torrents to test. Guess you can’t really seed everything forever…

0

Simplest way to trash Windows and switch computer to GNU/Linux? Asking for a friend.

preview

I really am asking for a friend since I don’t use windows and am clueless about it. Also, my own computers are pretty old and don’t have UEFI, so I’m clueless about that too.

My friend just bought a new Lenovo Ideapad Slim 3 with Windows 11 Home preinstalled and it immediately sent her into some kind of Microslop enrollment hell, so (yay) she wants to trash Windows altogether and switch to GNU/Linux. I’m trying to help her through it. I do it myself all the time by writing a Debian MATE ISO to a USB stick, booting from USB, and running the Debian installer. But,

  1. that’s already too complicated for a not-really-nerd, and
  2. that doesn’t do anything about UEFI since I haven’t had to deal with that. IDK if her new computer has UEFI.

I prefer staying with Debian MATE since I’m used to it and the MATE UI is fairly familiar to Windows users, and GNOME is crap imho. But I’m open to whatever if that simplifies installation.

It would be great if there was a downloadable Windows executable that simply does everything. Install it, click it, it downloads a CD image and either writes it to USB or just manages to boot the image somehow. In days of yore you could do that with SYSLINUX or related stuff. Maybe there is something equivalent now.

Added: I appreciate all the responses but should add that I’m not looking for recommendations of distros unless Debain is for some reason seriously harder to get running, like because of UEFI. Otherwise I’m looking purely for installation advice. Distro choice mostly affects usage post-installation and MATE is what I’m comfortable with so I’d rather have my friend stick with that for now. Unfortunately she’s in another state, so I can’t go help her with the install in person.

I really am asking for a friend since I don’t use windows and am clueless about it. Also, my own computers are pretty old and don’t have UEFI, so I’m clueless about that too.

My friend just bought a new Lenovo Ideapad Slim 3 with Windows 11 Home preinstalled and it immediately sent her into some kind of Microslop enrollment hell, so (yay) she wants to trash Windows altogether and switch to GNU/Linux. I’m trying to help her through it. I do it myself all the time by writing a Debian MATE ISO to a USB stick, booting from USB, and running the Debian installer. But,

  1. that’s already too complicated for a not-really-nerd, and
  2. that doesn’t do anything about UEFI since I haven’t had to deal with that. IDK if her new computer has UEFI.

I prefer staying with Debian MATE since I’m used to it and the MATE UI is fairly familiar to Windows users, and GNOME is crap imho. But I’m open to whatever if that simplifies installation.

It would be great if there was a downloadable Windows executable that simply does everything. Install it, click it, it downloads a CD image and either writes it to USB or just manages to boot the image somehow. In days of yore you could do that with SYSLINUX or related stuff. Maybe there is something equivalent now.

Added: I appreciate all the responses but should add that I’m not looking for recommendations of distros unless Debain is for some reason seriously harder to get running, like because of UEFI. Otherwise I’m looking purely for installation advice. Distro choice mostly affects usage post-installation and MATE is what I’m comfortable with so I’d rather have my friend stick with that for now. Unfortunately she’s in another state, so I can’t go help her with the install in person.

0

What are some things X11 can do that Wayland still can't?

preview

The biggest thing I can think of is that X11 is more flexible when it comes to specifying custom resolutions; which some people use to output 240p on CRT TVs for emulation. AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.

I’ve also noticed that Grsync’s password prompt is broken on Wayland. Thankfully, it has a feature that lets you preview the command it’s about to run, so that you can copy and paste it into a terminal.

Being a KDE user on EndeavourOS, I use Wayland everyday. I switched over a few years ago for Waydroid, but now X11 isn’t even an option for me with the current release of KDE.

The biggest thing I can think of is that X11 is more flexible when it comes to specifying custom resolutions; which some people use to output 240p on CRT TVs for emulation. AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.

I’ve also noticed that Grsync’s password prompt is broken on Wayland. Thankfully, it has a feature that lets you preview the command it’s about to run, so that you can copy and paste it into a terminal.

Being a KDE user on EndeavourOS, I use Wayland everyday. I switched over a few years ago for Waydroid, but now X11 isn’t even an option for me with the current release of KDE.

0

Agent Name Service is Now Part of The Linux Foundation

It's FOSS Agent Name Service is Now Part of The Linux Foundation itsfoss.com
preview

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.

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.

0

Agent Name Service is Now Part of The Linux Foundation

It's FOSS Agent Name Service is Now Part of The Linux Foundation itsfoss.com
preview

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.

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.

0

Firefox's free built-in VPN removes its data limit (until next year) - OMG! Ubuntu

OMG! Ubuntu Firefox's free built-in VPN removes its data limit (until next year) - OMG! Ubuntu www.omgubuntu.co.uk
preview

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).

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).