LinuxCommunity.io

I think, in this case, Eugene, you might be on the wrong side. Whether it be - hammer, - gun, - knife, - bazooka, - missile, - mine, etc., those instruments have no ability to act independently! Place all of them in proximity of somebody, no harm can be done to those people without a human consciously using those to commit an act of aggression. “AI” as it is termed, has been deliberately given a set of guidance rules, by their creators, such that once their baseline - activation - sensor/scanning - motivation - decision-making and - action-/goal-pursuit circuits and logic have been enabled, again by a human/creator, said “AI” may (and as recently demonstrated can) pursue goals and undertake actions independantly of the creators, because the creators did not take the necessary precautions to incorporate the minimum set of self-regulating “overriding values rules” that would filter out the “wrong” kind of decisions! To me, this last points to potentially criminal negligence, depending on the severity of the outcomes of the “AI”'s actions. My two cents worth. … and it is for that reason that I again encourage people to consider the comments I put forth in an earlier Ubuntu discussion.

Got hit with this after waking my ThinkPad today. DRM Panic screen (Tux plus a QR code) that kernels 6.12+ can show instead of a frozen console. Setup - ThinkPad T14s Gen 3 AMD (21CQ), BIOS 1.50 - Kali, kernel 7.1.5+kali-amd64 - Wi-Fi: Qualcomm WCN6855 (ath11k_pci), firmware WLAN.HSP.1.1-03125 (April 2024) - Sleep mode: hybrid-sleep Getting the log The QR code encodes a https://deb.li/panic#... URL containing the compressed kernel log. Scan it with your phone and open the full URL, and the page decodes the log in the browser. Note that the page tells you to reportbug to Debian. On Kali, file at bugs.kali.org instead. The relevant part auto RIP: 0010:ath11k_hal_srng_access_begin+0x12/0x40 [ath11k] ath11k_ce_send+0xc1/0x2a0 [ath11k] ath11k_htc_send+0x1fa/0x320 [ath11k] ath11k_wmi_cmd_send+0x54/0x320 [ath11k] ath11k_wmi_pdev_set_param+0x67/0xc0 [ath11k] ath11k_mac_op_start+0xcb/0x3f0 [ath11k] drv_start+0x48/0x130 [mac80211] ieee80211_reconfig+0x83/0x1cf0 [mac80211] wiphy_resume+0x89/0x1c0 [cfg80211] ... Kernel panic - not syncing: Fatal exception in interrupt The ath11k driver page-faulted while resuming from sleep. mac80211 restarted the radio, the driver sent a firmware command, and it touched a ring buffer that wasn’t mapped anymore because the chip hadn’t come back cleanly. It’s a known class of ath11k/WCN6855 resume bugs, and it’s intermittent: I’d suspended and resumed several times the weeks before without issues. Fix Unload the Wi-Fi driver before sleep and reload it after resume, so there’s nothing for ath11k to resume. auto sudo mkdir -p /usr/lib/systemd/system-sleep sudo tee /usr/lib/systemd/system-sleep/ath11k >/dev/null <<'EOF' #!/bin/sh case "$1" in pre) modprobe -r ath11k_pci 2>&1 | logger -t ath11k-sleep ;; post) modprobe ath11k_pci 2>&1 | logger -t ath11k-sleep ;; esac EOF sudo chmod 755 /usr/lib/systemd/system-sleep/ath11k This runs for suspend, hibernate and hybrid-sleep. To confirm it ran after a resume: auto journalctl -b -t ath11k-sleep You lose Wi-Fi for a few seconds on wake while it reconnects. That’s the tradeoff. oto Firmware isn’t the issue here. firmware-atheros is current (20260810-1) and still ships the WLAN.HSP.1.1-03125 build for WCN6855 hw2.1. The fault is in the ath11k driver’s resume path, so the sleep hook is the workaround until it’s fixed upstream. Logging this here if helpful to anyone else. I’ve also reported upstream to the ath11k and linux-wireless mailing lists and will update this thread if a fix lands.

Bitpainter75: > ’ve been on CachyOS for about two and a half years now. Before that I spent roughly five years switching between openSUSE and Kubuntu. > > If CachyOS or Arch in general ever stopped being an option for me, I’d probably go back to openSUSE. I always liked it and felt comfortable there. Those are solid choices on both ends. If you ever want to experiment with KDE again, the Kubuntu is no longer the featured KDE version; I’d suggest looking at KDE Neon to explore the latest KDE Plasma software; otherwise you’re in great shape with what you’re using! J_J_Sloan: > SuSE, and then OpenSUSe was my OS of choice for years, until the switch to the not-yet-ready KDE 4.0 forced me off to Ubuntu, where everything just worked, and later to Kubuntu, after KDE settled down. Same thing: SUSE is a good choice; if something happened with KDE and you want to stick with KDE Plasma, as above I’d recommend KDE Neon; if you want more of a “rolling release” configuration, Open SUSE Tumbleweed is an excellent option; I’ve used it on many occasions. If you don’t really need KDE Plasma, then OpenSUSE Tumbleweed with the Xfce desktop would be a reliable choice and you wouldn’t have to continually reinstall, you could simply update your system periodically and that would take care of it; with the “rolling nature” of Tumbleweed you may experience quite a few updates each time, so keep that in mind before deciding upon it, but I do endorse it as a solid experience, going with the package update route rather than the reinstallation route.

A busy kernel and distro week with notable security, tooling, and gaming updates that most Linux users will want on their radar. ## :top_arrow: Top Stories - Several vulnerabilities have been discovered in the Linux kernel — LWN reports on a batch of kernel issues across multiple subsystems, with Debian, Ubuntu, Fedora, SUSE, RHEL, and others already pushing updated packages and noting that “fixes are available in the latest stable kernels 7.2.10, 6.18.56, 6.12.112, 6.6.158, 6.1.189, 5.15.222, and 5.10.271.” Anyone maintaining Linux systems should ensure they are tracking their distro’s latest kernel updates or these upstream versions to avoid running with known privilege-escalation and denial-of-service bugs. - X.Org Server 21.1.25 and Xwayland 24.1.14 released due to more security issues — The X.Org project has pushed Xorg 21.1.25 and Xwayland 24.1.14 with fixes for newly found flaws in the legacy X11 stack, and the release notes call out that these are again security-driven point updates. Desktop users on Xorg (including older NVIDIA setups or thin clients) and Wayland users relying on Xwayland compatibility should take these updates as soon as their distro ships them. - Gentoo infrastructure sponsors wanted — Gentoo’s infrastructure team says several long-time sponsors have pulled out and that they can currently only maintain a “small number of critical machines,” so they’re asking for new partners to donate hardware, colocation, VMs, hosted servers, or money. Organizations that depend on Gentoo or value a source-based distro with Portage should seriously consider the sponsorship options laid out on the wiki, which range from providing 2 vCPU/4 GB VMs to funding colo bills. - Ubuntu currently suffering from sustained DDoS attack — Canonical has confirmed that ubuntu.com, ISO mirrors, and related sites have been intermittently unreachable since October 8 due to a distributed denial-of-service attack, saying their operations and security teams are working to restore normal access. Ubuntu users and admins should expect download and update disruptions around 26.10 images, snaps, and documentation while Canonical tightens network defenses. - Linux 7.3-rc7 released, stable 7.2.10 and long-term kernels updated — Kernel.org lists 7.3-rc7 as the current mainline (released 2026-10-12) and 7.2.10 as the latest stable as of 2026-10-11, alongside refreshed longterm series 6.18.56, 6.12.112, 6.6.158, 6.1.189, 5.15.222, and 5.10.271. This cadence affects everyone from distro maintainers to in-house kernel users, who should align their baselines and backports with these tags, especially in light of the active security fixes above. ## :shield: Security Watch - Several vulnerabilities have been discovered in the Linux kernel — The coordinated advisory notes that multiple bugs affecting current and LTS lines are fixed in 7.2.10 and the longterm releases 6.18.56, 6.12.112, 6.6.158, 6.1.189, 5.15.222, and 5.10.271, with distros already shipping patched kernels. Anyone running older point releases of these series should plan a maintenance window to roll forward, especially on multi-tenant or internet-facing hosts. - X.Org Server 21.1.25 and Xwayland 24.1.14 released due to more security issues — The X.Org team has once again had to issue urgent point releases addressing newly reported vulnerabilities in Xorg and Xwayland, continuing the trend of frequent security-only updates to the aging X stack. Users on desktop Linux where Xorg or Xwayland is installed should track their distro’s security channels and update promptly, even if they’ve already moved most workloads to Wayland. - Fake Express packages on npm spread a Linux worm — SafeDep’s write-up describes how malicious npm packages impersonating the popular Express framework dropped a Linux-focused worm, detailing indicators in the “dirtyblanket” campaign. Developers shipping or deploying Node.js apps on Linux should audit their dependency trees for suspicious Express-like package names and tighten npm publishing and CI policies. ## :package: Releases & Updates - Linux 7.3-rc7 mainline snapshot — The 7.3-rc7 tag, released 2026-10-12, is expected to be the final release candidate before 7.3, so kernel testers and distro teams should finalize regression checks now. - Linux 7.2.10 stable — Version 7.2.10, released 2026-10-11, ships a batch of fixes captured in ChangeLog-7.2.10, and is the target for anyone tracking the current stable series. - Linux 6.18.56, 6.12.112, 6.6.158, 6.1.189, 5.15.222, 5.10.271 longterm updates — All current LTS branches got new point releases on 2026-10-03 or 2026-10-11 with security and bug fixes, so distro vendors and embedded integrators should align their kernels accordingly. - Ventoy 1.1.18 adds experimental SteamOS recovery support — The new Ventoy 1.1.18 release can now handle SteamOS recovery images experimentally and improves the Linux remount feature, which is useful for admins maintaining multiboot USB sticks or doing frequent OS testing. - Q4OS 6.10 “Andromeda” ships with Plasma 6.3.6 and TDE 14.1.5 — This Debian 13.7 “Trixie”-based release updates KDE Plasma to 6.3.6 and Trinity to 14.1.5, giving conservative desktop users a fresh but stable dual-UI experience. - Xorg Server 21.1.25 and Xwayland 24.1.14 — Besides security fixes, these coordinated point releases also keep Xwayland and Xorg aligned for distros that need to support both X11 and Wayland workloads during the transition years. ## :hammer_and_wrench: Worth Reading & Trying - Will Linux phones become a viable alternative to the Android/iOS duopoly? — This long-form analysis pulls together the current state of mobile projects like postmarketOS/Nura, PinePhone, and Librem 5 and argues what market share and ecosystem shifts would be needed for “Linux phones” to matter beyond enthusiasts. - Gentoo infrastructure sponsors wanted — Beyond the sponsorship appeal, the accompanying wiki pages detail Gentoo’s infra layout, from minimum VM specs (2 vCPU, 4 GB RAM, 25 GB disk) to how they think about colo and cloud, which is instructive for anyone running volunteer-backed infra. - Creating distro build tooling for a small community — q66’s post on Chimera Linux’s “cbuild” explains why they rolled their own cross-distro build tooling and what tradeoffs small projects face versus using existing CI/build systems. - 3-2-1 backup strategy with restic and Backblaze B2 — This guide walks through implementing a classic 3-2-1 backup plan on Linux using restic and B2, including concrete commands and notes on testing restores, which is directly applicable to homelab and small-shop setups. - Fake Express packages on npm spread a Linux worm — The incident report is a practical case study in how supply-chain attacks propagate through popular package ecosystems and how defenders can instrument detection. ## :penguin: From LinuxBlog.io - Linux Bash Scripting: Writing Your First Script — A hands-on primer dated 2026-09-28 that walks shell users through variables, loops, conditionals, functions, and error handling with real Bash examples. - Linux server performance: Is disk I/O slowing your application? — This 2026-09-12 piece explains how to use tools like top and iostat to distinguish CPU from disk bottlenecks and ties it back to real-world tuning advice. - Master Linux Bash History with historyctl, HISTFILE, and Shortcuts — Published 2026-09-03, it shows how to tune HISTSIZE, enable timestamps, sync history across terminals, and use advanced search shortcuts to speed up terminal workflows. - Linux swap Commands: Create and Manage Swap Files/Partitions — A 2026-08-26 guide to using mkswap, swapon, and swapoff to size and manage swap on modern Linux systems, including tips for troubleshooting. - How to Set Up Hibernation on Linux (Swap Done Right) — This 2026-08-24 article walks through setting up hibernation with appropriate swap configuration and systemd integration on a Debian/XFCE desktop. - Linux Kernel Parameters Tuning for Better Performance — From 2026-08-22, it offers a curated sysctl baseline and explains key knobs for network throughput, memory pressure, and file I/O that Linux admins can safely experiment with. Let’s dig into any of these in more depth or share what you’re testing and upgrading in your own setups in the replies below. --- Our community remains free of banner ads thanks to our partnership with Better Stack. Better Stack offers infrastructure observability services, uptime monitoring, logging, incident management, and a free tier worth checking out. Visit: betterstack.com

I view the ArtCraft “works” within the context of a much leveraged, and well-funded, industry: - reverse engineering! The fact that AI has eliminated the exclusive access to those capabilities is a disruptor to an extent that cannot be fully fathomed! If what ArtCraft has released are identical clones, visually, then it is highly likely that intellectual property is at play. If what has been released is functionally identical, but has a different GUI interraction to achieve the same functional results, the workflow may fall into the category of intellectual property, depending on how the original creators submitted the “patent claims”. If what has been released achieves identical results, but with different GUI interraction … and … different workflow, that is the whole reason for existence of the reverse engineering industry, and all bets are off. No human-created software is safe from “cloning” given that AI has achieved such a referential milestone! For me, the implication is that IPOs depending on “captive revenue streams” from a monopoly-like proprietary software have reached a peak and will henceforth diminish, because the risk of AI-generated competition causing early interruption of expected revenue streams is too great a hurdle to ignore for the monies invested! Regardless of whether we embraced it or demonized it, the AI-dominated age has arrived! Hang on to your hats … because it is going to be a rough ride!