Posted: 2026-10-08 15:00:33 Source: https://www.youtube.com/watch?v=YIeKWy09E9Q
Posted: 2026-10-07 15:00:07 Source: https://www.youtube.com/watch?v=CMB5GCexb84
Posted: 2026-10-07 13:58:02 Source: http://www.linux-magazine.com/Online/News/Office-365-Available-for-Testing-on-Linux-via-Bottles
Linux users can now test the official Office 365, thanks to Mirko Brombin's work on Bottles.
Posted: 2026-10-06 19:00:00 Source: https://it.slashdot.org/story/26/10/06/1854244/ibm-and-red-hat-find-more-than-400-new-vulnerabilities-in-popular-java-code?utm_source=atom1.0mainlinkanon&utm_medium=feed
IBM and Red Hat say their AI-powered Lightwell initiative has identified and helped remediate more than 400 previously unknown vulnerabilities across widely used Java libraries. Phoronix reports: They announced this feat today as part of their promoting Lightwell Clearinghouse to GA, which is an enterprise service for their customers to submit open-source software dependencies for priority review and remediation. From today's announcement: "The milestone addresses a growing business risk. As autonomous AI agents become capable of combining several lower-risk software weaknesses into a more serious attack, companies need to do more than identify vulnerabilities. They need a practical way to develop, test and deploy fixes in the software that supports critical applications."
Read more of this story at Slashdot.
Posted: 2026-10-06 16:00:00 Source: https://www.linuxjournal.com/content/googles-kage-project-rethinks-linux-kernel-security-isolated-device-drivers

Google is exploring a new approach to Linux kernel security that could significantly change how device drivers interact with the operating system. The experimental project, known as Kage, uses compiler-based sandboxing to isolate drivers inside the kernel, potentially limiting the damage caused by memory corruption, programming errors, and exploitable vulnerabilities without requiring drivers to run as separate user-space processes.
The research was presented at the Linux Plumbers Conference 2026, held October 5–7, with Stanford University and Google researcher Zachary Yedidia discussing how LLVM's Lightweight Fault Isolation (LFI) technology can create restricted execution environments for native kernel code. Unlike conventional isolation techniques, which often depend on separate processes or virtual machines, Kage attempts to preserve the performance advantages of kernel-space execution while reducing the amount of memory individual drivers can access.
Early prototypes have already demonstrated the concept using NVMe storage, networking, and Wi-Fi drivers. However, Kage remains an experimental research project rather than a feature available in mainstream Linux distributions. Its developers are still investigating performance, hardware access, and compatibility with more complicated drivers, including graphics hardware.
Linux device drivers are responsible for connecting the operating system to hardware components, including graphics cards, network adapters, storage controllers, USB devices, and wireless chipsets. Most traditional Linux drivers execute in kernel space, giving them privileged access to system resources and the ability to interact directly with hardware. This architecture is one reason Linux can deliver high performance across such a broad range of devices, but it also creates a significant security challenge.
When an ordinary application encounters a memory error, the operating system can often terminate that process without affecting the rest of the system. Kernel drivers operate under different conditions. Because they typically share the kernel's address space and privileges, an invalid memory access or exploitable vulnerability can affect unrelated kernel components, potentially resulting in a system crash, privilege escalation, or complete compromise of the operating system.
The challenge becomes more complicated when considering the enormous number of drivers supported by Linux. Some are maintained by large organizations with extensive testing infrastructure, while others receive contributions from smaller development teams or individual maintainers. Even carefully reviewed drivers can contain bugs, particularly when they interact with complicated hardware, asynchronous operations, and memory-management mechanisms.
Posted: 2026-10-06 15:00:00 Source: https://www.youtube.com/watch?v=QGZTJX_Gjk4
Posted: 2026-10-03 20:51:00 Source: https://linux.slashdot.org/story/26/10/03/2056206/steam-on-linux---down-to-305-for-september?utm_source=atom1.0mainlinkanon&utm_medium=feed
Phoronix reports: Steam on Linux use in March hit an all-time high of around 5.33% marketshare. Since then it pulled back to around 4% while for September 2026 the Steam Survey results... indicate a rather steep decline of 0.85%, down to 3.05%. Meanwhile macOS is at 1.92% and Microsoft Windows at 95%... Steam's Survey reports a 7.42% increase in Chinese use, up to 31.39% overall of the Steam population. Usually those large month-over-month swings where Steam China use shoots up dramatically is a boost to Windows and a detriment to Linux. Some attribute the large increases in Simplified Chinese use to being a reporting/sampling issue. When diving into the Steam Linux data exclusively, CachyOS has spiked by another 2.65% to now account for 18.12% of the sampled Linux gaming population. That even outperforms SteamOS Holo coming in at 17.37%. Among Linux gamers on Steam, AMD CPUs still account for the high 60 percentage space thanks to the Steam Deck and Steam Machine using AMD APUs and their open-source/Linux support being popular with enthusiasts.
Read more of this story at Slashdot.
Posted: 2026-10-03 00:30:14 Source: https://www.youtube.com/watch?v=8xNQ883Qpz0
Posted: 2026-10-01 16:33:16 Source: http://www.linux-magazine.com/Online/News/Dutch-Government-Turns-to-Open-Source-for-Digital-Sovereignty
Following in the footsteps of other European countries, the Netherlands is looking to increase its sovereign digital infrastructure with open source software.
Posted: 2026-10-01 16:00:00 Source: https://www.linuxjournal.com/content/speech-synthesis-linux-adding-voice-scripts-and-systems

Linux users have long had a pragmatic relationship with text-to-speech. The classic open-source engines have been available for years, wired into accessibility tools and the occasional script, dependable but unmistakably robotic. They do the job where the job is simply to convert text to some kind of speech, but the mechanical output has kept them out of anything where the voice actually matters. The arrival of high-quality speech synthesis delivered over an API changes what is possible, letting Linux users add genuinely natural voices to scripts, services, and applications without hosting a heavyweight model themselves.
Anyone who has used the traditional Linux speech engines knows the trade-off. They are free, local, and scriptable, which fits the Linux ethos perfectly, but the voices are clearly synthetic. For accessibility and for utilitarian tasks where intelligibility is all that counts, that has been acceptable. For anything user-facing where the quality of the voice shapes the experience, it has not.
The alternative of running a modern, high-quality speech model locally is possible but comes with real costs: significant computational requirements, model management, and the ongoing maintenance of a demanding piece of infrastructure. For many use cases, particularly on servers, embedded systems, or ordinary workstations, that overhead is disproportionate to the need. This is the gap that an API-based approach fills, offering the quality of a large modern model without the burden of hosting one.
Delivering speech synthesis over an API fits naturally into how Linux users already build things. Rather than installing and maintaining a model, you make a request to a service and receive audio back, which you can then play, save, or pipe into whatever comes next. A text to speech api turns text into natural-sounding audio through a simple network call, which means a script or service can produce high-quality speech with nothing more than the ability to make an HTTP request and handle the response.
This composability is what makes it appealing in a Linux context. The request can come from a shell script, a systemd service, a cron job, a Python program, or any application that can talk to a network endpoint. The returned audio slots into the familiar toolchain of files, pipes, and media players. For users accustomed to assembling capabilities from small, cooperating parts, a speech API is just another well-behaved component that happens to produce audio, and it drops into existing workflows without disturbing them.
Posted: 2026-10-01 15:00:28 Source: https://www.youtube.com/watch?v=TswkmHQHQfU
Posted: 2026-09-29 22:00:00 Source: https://linux.slashdot.org/story/26/09/29/1858218/microsoft-makes-linux-containers-native-on-windows-11?utm_source=atom1.0mainlinkanon&utm_medium=feed
BrianFagioli shares a report from NERDS.xyz: Microsoft has made WSL Containers generally available, giving Windows 11 developers a built-in way to build, run, and deploy Linux containers through Windows Subsystem for Linux. The release includes wslc.exe for managing containers, GPU support, networking improvements, health checks, storage mounts, and integration with Microsoft Defender for Endpoint and Intune. Microsoft also claims up to twice the performance when Linux environments access files stored on Windows. Docker Desktop, Podman Desktop, and Rancher Desktop are not going anywhere, but developers who only need basic container functionality now have another option built around WSL. One notable feature is still missing: Compose support. Microsoft says adding it is now a priority.
Read more of this story at Slashdot.
Posted: 2026-09-29 18:49:32 Source: http://www.linux-magazine.com/Online/News/Linux-May-Soon-Work-on-Snapdragon-X2-Based-PCs
If you're thinking about buying a Snapdragon X2-based desktop or laptop, Linux may soon be an option.
Posted: 2026-09-29 16:00:00 Source: https://www.linuxjournal.com/content/archinstall-45-released-aarch64-support-real-time-kernels-and-major-installer-fixes

The Arch Linux project has released Archinstall 4.5, the latest version of its guided text-based installer, bringing expanded AArch64 support, new real-time Linux kernel options, additional translations, security improvements, and numerous fixes for installation workflows.
Archinstall 4.5 was released on September 29, 2026, roughly three months after Archinstall 4.4. The new version arrives just ahead of Arch Linux's October installation media refresh and has already been packaged as archinstall 4.5-1 for Arch Linux repositories.
While Archinstall remains optional, it provides users with a guided way to configure an Arch Linux installation without manually performing every step described in the Arch installation guide. Version 4.5 concentrates primarily on hardware support, installer reliability, security, and expanding the range of systems that can use the guided installation process.
One of the biggest changes in Archinstall 4.5 is improved support for AArch64, the 64-bit ARM architecture.
The installer can now handle GRUB and Limine EFI installations on AArch64 systems. It also gains support for the proper AArch64 root partition type GUID.
Previously, parts of Archinstall's bootloader configuration were more heavily oriented toward x86_64 installations. The latest changes make its guided installation workflow more useful on ARM64 hardware.
AArch64 has become increasingly important throughout the Linux ecosystem. The architecture can now be found in cloud servers, development boards, laptops, workstations, and specialized computing platforms.
Supporting both GRUB and Limine EFI installations gives Archinstall more flexibility when preparing these systems.
GRUB remains one of the most widely used Linux bootloaders, and Archinstall 4.5 extends its installation logic to AArch64 EFI systems.
This allows ARM64 installations to use a bootloader workflow much closer to what Archinstall already provides on conventional x86_64 UEFI computers.
The change doesn't mean every ARM device will automatically become compatible with Arch Linux. ARM hardware can still have highly platform-specific firmware and boot requirements.
It does, however, remove an important Archinstall limitation for AArch64 machines that provide conventional UEFI environments.
The same architectural expansion applies to Limine.
Limine is a modern multiprotocol bootloader supported as one of Archinstall's bootloader choices. Archinstall 4.5 extends its EFI installation support to AArch64 as well.
Posted: 2026-09-29 15:00:04 Source: https://www.youtube.com/watch?v=HQzHcHd3h-s
Posted: 2026-09-26 16:04:00 Source: https://news.slashdot.org/story/26/09/26/0559227/ai-finds-so-many-linux-bugs-canonical-changes-to-a-two-week-stable-release-update-cycle?utm_source=atom1.0mainlinkanon&utm_medium=feed
"Finding vulnerabilities faster also puts pressure on Linux distributions to fix and deliver patches faster," writes Slashdot reader BrianFagioli AI has transformed bug discovery from "a manual, time-intensive process into a highly automated engine," notes Canonical's blog, leading to a "recent explosion in the volume of CVEs". Additionally, the upstream kernel community became its own CVE Numbering Authority (CNA) and assigned CVE (Common Vulnerabilities and Exposures) identifiers to thousands of bugs, arguing that at the kernel level, almost any type of bug that can affect a running system, could potentially be classified as a vulnerability. As a result, the volume of CVEs has skyrocketed exponentially, creating a massive backlog of alerts and forcing defenders to drastically increase the speed of their fixes to close the window of risk. To address the growing volume of CVEs and the demand for faster security fixes, we are transitioning to a unified, 2-week release cycle... While a patch is being prepared, Canonical aims to provide safe workarounds where applicable, so users aren't left exposed in the meantime. Where no safe workaround exists, Canonical will say so clearly and point users toward general hardening steps instead. The goal is to get environments into a defensible, safer state within 24 to 48 hours of public disclosure — well before a patch ships. This doesn't replace the patch; it buys the time needed to fix the vulnerability properly, without sacrificing security. "Linux did not suddenly become wildly insecure overnight," notes the blog Nerds.xyz. "We are getting much better at finding and cataloging problems that may have previously gone unnoticed." There is something almost ironic about all of this. AI is routinely pitched as a tool that will make software development faster, but it is also making vulnerability discovery faster. That means maintainers now have to accelerate the other side of the equation too. For Ubuntu users, that should ultimately be good news. More bugs being discovered is preferable to vulnerabilities sitting unnoticed in the Linux kernel.
Read more of this story at Slashdot.
Posted: 2026-09-25 19:45:43 Source: http://www.linux-magazine.com/Online/News/KDE-for-People-Initiative-Calls-for-AI-Ban-in-Plasma
A new community of KDE wants the project to adopt a strict no-AI policy for KDE Plasma.
Posted: 2026-09-23 20:28:15 Source: http://www.linux-magazine.com/Online/News/KDE-Sets-Ambitious-Goals-for-2026-and-Beyond
KDE Connect reveals the goals for the Linux desktop darling, with one of those goals long overdue.
Posted: 2026-09-18 21:32:40 Source: https://www.youtube.com/watch?v=UZZsIWUBOss
Posted: 2026-09-17 14:20:12 Source: http://www.linux-magazine.com/Online/News/It-s-Time-to-Test-Fedora-45-Beta
Fedora 45 beta has been released with updated Gnome, KDE Plasma, and kernel.