Weekly Forum Summary

Key Stats

In the past week, our Linux forums had the following activity and key statistics:

  • Total New Posts: 227
  • Total New Topics: 25

Top Members

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

  • Best Reply: @guiverc’s primer on Qt, KDE Frameworks, and LXQt differences in Looking for comments - Differences between Qt on KDE vs LxQt on Lubuntu
    Why it stands out: It clearly separates what Qt provides from what KDE Frameworks add, explains how Kubuntu and Lubuntu use the same Qt stack but diverge to meet different goals, and ties it back to Ubuntu’s packaging process. It’s the kind of concise, high‑signal answer that helps readers make smarter desktop and toolkit choices without confusion.

Thanks for reading. See you again next week! :penguin:

:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the site-help or Our Community forum category.

3 Likes

Key Stats

In the past week, our Linux forums had the following activity and key statistics:

  • Total New Posts: 272
  • Total New Topics: 29

Top Members

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

  • Best Reply: @Carrot’s deep‑dive on Intel AX210 slowdowns with Comcast gateways in Intel AX210 speeds capped at 20 Mbps on multiple distros. It clearly explains the MCS/PMF misadvertising bug on certain ISP routers, offers a practical workaround with NetworkManager, and references an in‑flight kernel fix and community patch.

    “Certain routers
 have a software bug that likely resulted from a copy/paste of the router capabilities into the basic MCS requirements
 You’ll likely need to run this command to disable pmf if you get any slowdowns or spikes on ping:
    nmcli connection modify “YOUR_WIFI_NAME” wifi-sec.pmf 1”

Thanks for reading. See you again next week! :penguin:

:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the site-help or Our Community forum category.

4 Likes

This week in our forums


Key Stats

In the past week, our Linux forums had the following activity and key statistics:

  • Total New Posts: 259
  • Total New Topics: 30

Top Members

Interesting Topics

Activity by the @staff Group

  • Security tooling for quick fleet triage: @hydn released a read-only checker for the new “Dirty Frag” issues and supporting modules in Dirty Frag (CVE-2026-43284 / CVE-2026-43500) check script. It reports OK, MITIGATED, and other states for at-a-glance status across systems.

  • To improve clarity and safety in member submissions, the team published Showcase category guidelines: What to include when sharing your project. The guide clarifies expectations around source links, licenses, unsigned binaries, screenshots, and responsible disclosure.

  • In Showcase, @toadie continued iterating a Go-based TLS cert monitoring tool in [Go] cert-checker, adding a help flag, better flag error handling, UI testing, and a new dark mode variant. The fast feedback loop from members led to tangible UX gains in just a couple of posts.

Best Reply or Topic of the Week

  • Best Reply: @tkn’s concise, well-sourced answer in Bootable USB Key - Partition Table Format? clearly lays out why legacy MBR remains the most reliable choice for older BIOS machines, includes references, and sets realistic expectations about GPT on legacy systems. It is a model of practical, actionable guidance.

Thanks for reading. See you again next week! :penguin:

—
:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the site-help or Our Community forum category.

5 Likes

Key Stats

In the past week, our Linux forums had the following activity and key statistics:

  • Total New Posts: 216
  • Total New Topics: 16

Top Members

Interesting Topics

Activity by the @staff Group

Note: The automated weekly recap by @system also continued, helping surface hot threads and momentum, while @hydn’s new Getting Started Guide set a friendly tone for first-time posters.

Best Reply or Topic of the Week

  • Best Reply: @Nosugrof’s solution in External USB drive unmounts or powers down randomly is a practical gem. After thorough troubleshooting, they shared a small “mksim” script that safely simulates user activity to prevent power management from idling external drives during long backups, validating the fix over a 30-hour run. It is a tidy, reproducible workaround many can adopt when BIOS and cgroup options fall short.

Thanks for reading. See you again next week! :penguin:


:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the site-help or Our Community forum category.

5 Likes

This week in our forums


Key Stats

In the past week, our Linux forums had the following activity and key statistics:

Total New Posts: 434
Total New Topics: 38

Top Members


Interesting Topics


Activity by the @staff Group

  • @hydn enabled footnote markdown and broadened the solved workflow in Enable citations, pairing it with a smart “question” tag approach so Q&A-style threads work across categories without enabling the plugin everywhere.

  • @toadie shipped a substantial update to the certificate toolchain in Go cert-checker. The 1.2 release adds a config file, cleaner output modes, and better report handling, with @ugnvs suggesting tiered UIs for “simple” vs “advanced” flows that are now taking shape.

  • @system launched a new weekly digest thread, Linux Weekly News: Key Stories from the Past Week, to centralize upstream highlights, releases and recommended reads. It’s meant as a living index you can reply to with your finds each Monday morning.


Best Reply or Topic of the Week

  • Best Reply: @pavlos’ precise fix for misrouted HTML links on Ubuntu MATE in Browser link to html - not opening default browser after update. When desktop URL launchers started opening Slack instead of Firefox, he zeroed in on MIME associations and recommended editing ~/.config/mimeapps.list to point text/html and x-desktop at firefox.desktop. The change made the default browser stick again after reboot, which the OP confirmed solved the issue.

“for some unknown reason it prepended firefox_ to existing lines
 Your binary should be just firefox, not firefox_firefox.”

That’s the kind of practical, reproducible answer that saves people hours.

Thanks for reading. See you again next week! :penguin:


:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the site-help or Our Community forum category.

5 Likes

Key Stats

In the past week, our Linux forums had the following activity and key statistics:

  • Total New Posts: 396
  • Total New Topics: 35

Top Members

Interesting Topics

  • In Debian, @IronRod asked a simple question that unlocked a flood of practical experiences in Interested: Which version? Debian or Debian-derived distro?. Members compared stock Debian to derivatives like Ubuntu MATE, MX Linux, antiX, Zorin, and LMDE. @ericmarceau weighed community and workflow comfort against Ubuntu’s growing Snap defaults, @Brian_Masinick recommended antiX for lean setups, and @Greyfox shared daily-driver notes on GNOME with Debian 12 and 13. It’s a great snapshot of what “Debian family” looks like across desktops and headless servers.

  • @andreas started a reflective thread in Debian with Debian seems very enticing
 talk me out of it?. Weighing a move from Fedora to Debian Stable for CUDA, Python work, and a GTX 1060, the discussion covered driver age vs stability, Flatpaks for fresh GNOME apps, and managing NVIDIA from upstream repos. @hydn argued you likely won’t notice “outdated” drivers on a 1060 and shared a playbook for installing NVIDIA/CUDA on Stable. The “itch” won: several members, including @andreas and @ClaudioDC, spun up Debian and reported back happily.

  • In General Discussions, a hands-on debugging journey unfolded in Memory at 99% CPU1, memory hogging. @oswald_carter noticed a core pegged on battery power. With careful guidance from @hydn, the thread stepped through GRUB kernel params, initramfs/grub update pitfalls, and narrowing down kernel vs userspace culprits using top and ps. @ericmarceau suggested cpupower as a temporary control. The thread is a good model for methodical troubleshooting when a system goes sideways.

  • Policy crossed paths with Linux in General Discussions as @hydn highlighted California moves to exempt Linux from its upcoming age-verification law after backlash. The proposed amendment would exclude FOSS operating systems from the OS-level age checks. @andreas added context with EDRi and EFF perspectives on why age verification is intrusive and misses the mark, while others noted the practical gray areas around ecosystems like SteamOS.

  • Editors were a hot topic in General Discussions when @IronRod shared a fast, native contender in Zed – slick, capable, and fast. Members compared Zed to Code OSS, VSCodium, and the usual suspects. @toadie explored day-to-day ergonomics like tab behavior, while @Brian_Masinick and @ericmarceau made the case for vi/vim, neovim, and GVim for their ubiquity and efficiency. If you’re hunting for a lean VSCode alternative, this thread has the notes you want.

  • In #security, @hydn published a practical guide, Fail2ban on Linux: Protect Your Server from Brute-Force Attacks. Beyond the basics, the follow-up tip shows how to integrate Cloudflare’s API so bans propagate to your Cloudflare account too. @IronRod chimed in confirming Fail2ban is part of his standard server stack. If you want a hardened-by-default baseline, this walkthrough is worth bookmarking.

  • Dual-boot reality checks appeared in #help with @Greyfox’s detailed report, Linux then Windows install for dual-boot: Windows removing Linux from UEFI?. After a fresh Windows install, Linux UEFI entries vanished. @hydn recommended using efibootmgr to confirm whether entries are deleted vs reordered, and suggested rEFInd for a resilient boot flow that’s less dependent on firmware behavior. @IronRod added experience-based guardrails like Windows Update Blocker.

  • GPU stability came up in #help as @IronRod traced a stubborn amdgpu freeze to MES errors in AMD GPU Linux regression in 6.10. Moving up to kernel 6.19.14 resolved his system-wide hangs, with @Trenien reporting partial improvements on similar hardware. It’s a concise read if you’ve seen “MES failed to respond” in your journal and need a path forward.

  • In Showcase, @linuxjedi introduced a collaboration-focused diagnostic tool in My sosreport analysis tool project. Looking for feedback. “sos-vault” ingests sosreports, indexes 10,000+ files, and adds shared annotations. The current build uses Docker and LUKS-backed storage for privacy and isolation. @ericmarceau probed desktop/container tradeoffs and the upcoming open-source variant. If you triage systems for a living, this is one to watch.

  • Rounding out the week in Debian, @IronRod reported smooth fleet upgrades in Debian 13.5 released. @andreas clarified that point releases consolidate updates rather than introduce feature changes, and @Brian_Masinick noted the value of point releases for servers even if desktop users just keep rolling with regular updates.

Activity by the @staff Group

  • @hydn published a concise update on forum structure and quality-of-life tweaks in Forum housekeeping: tag cleanup + sidebar improvements. Highlights include a cleaned-up tag taxonomy, five pinned sidebar tags for quick navigation, and numeric unread counts in the sidebar to help you spot where conversations are active.

  • In the Fedora corner, @shybry747 shared a field report in Fedora 44 released, covering smooth upgrades across multiple machines, both GNOME and Sway spins. The follow-on from @andreas and others digs into GNOME 50 changes, extensions, and why fewer extensions often means fewer upgrade snags.

  • For those managing SSH bans and jails, @hydn surfaced a lightweight management layer in Fail2ban-ui: Fail2Ban UI is a swissmade web interface. It’s a web UI you can run locally to manage Fail2ban without dropping to the shell every time. @toadie bookmarked it for later testing.

  • Shipping tools continues: @toadie cut a new release of a utility for certificate checks in [Go] cert-checker. Version 1.3 is live, and it’s a handy companion for anyone juggling TLS monitoring in small infra or homelab setups.

Best Reply or Topic of the Week

“If you are making any type of change that requires a restart of a critical service or network component on a remote machine, set up an at job to run 5 minutes in the future. If your change works, cancel it; if not, you know you’re back in five minutes to try again.”

It’s a simple, battle-tested trick that can save you from lockouts and late-night drives to the rack. A great example of operational wisdom you can apply immediately.

Thanks for reading. See you again next week! :penguin:


Our community remains free of banner ads thanks to our partnership with Better Stack. There are no ad impression or click requirements. They are simply long-term supporters of the LinuxCommunity.io initiative.

Better Stack offers infrastructure observability services, uptime monitoring, logging, incident management, and a free tier worth checking out. Visit: betterstack.com


:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the site-help or Our Community forum category.

3 Likes

This week in our forums


Key Stats

In the past week, our Linux forums had the following activity and key statistics:

Total New Posts: 375
Total New Topics: 34

Top Members

@hydn: 69 posts, 204 likes received
@Jakarta2: 38 posts, 112 likes received
@Brian_Masinick: 31 posts, 95 likes received
@ericmarceau: 23 posts, 66 likes received
@tkn: 18 posts, 58 likes received
@andreas: 16 posts, 52 likes received
@Jymm: 15 posts, 51 likes received
@ugnvs: 13 posts, 50 likes received
@IronRod: 18 posts, 49 likes received
@toadie: 11 posts, 37 likes received

Interesting Topics

Activity by the @staff Group

  • @hydn introduced a new recognition cadence in Introducing Weekly Badges: Top Penguin & Top Contributor, celebrating members weekly on the front page and preserving a running archive of standout contributions.

  • To demystify membership flair and participation, @hydn published a clear Guide to Our Groups covering how to find, request, and manage group memberships and avatar flairs.

  • In Ubuntu, @shybry747 shared hands-on reservations in Ubuntu Sway Remix, noting multi-monitor quirks and non-obvious workarounds seen in the project’s wiki, opting to stick with Fedora Sway for now.

  • A healthy debate unfolded around Microsoft’s Fedora-derived distro in Announcing Azure Linux 4.0. @toadie and @ugnvs voiced skepticism about big vendor aims, while @hydn urged a cautious but practical stance, taking what’s useful while keeping eyes open.

Best Reply or Topic of the Week

  • Best Reply: @Jakarta2’s Secure Boot/MOK diagnosis in Faced A issue while installing linux. He pinpointed why a missing MokManager (mmx64.efi) combined with a pending key enrollment in UEFI NVRAM can fail boot, then laid out a clean test path: temporarily disable Secure Boot, recreate the USB from a verified ISO, and retry. It’s a concise, accurate explanation that helps newcomers distinguish partitioning issues from Secure Boot mechanics.

“MokManager (mmx64.efi) is used by shim when Secure Boot needs to process a pending key enrollment request. If that request exists in UEFI NVRAM but the boot media does not contain the required mmx64.efi file, boot can fail exactly as shown.”

Thanks for reading. See you again next week! :penguin:


Our community remains free of banner ads thanks to our partnership with Better Stack. There are no ad impression or click requirements. Their ongoing support of the LinuxCommunity.io initiative is something we genuinely appreciate.

Better Stack offers infrastructure observability services, uptime monitoring, logging, incident management, and a free tier worth checking out. Visit: betterstack.com


:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the #site-help or Our Community forum category.

7 Likes

This week in our forums


Key Stats

In the past week, our Linux forums had the following activity and key statistics:

Total New Posts: 438
Total New Topics: 41

Top Members

@tkn: 58 posts, 199 likes received
@Brian_Masinick: 51 posts, 177 likes received
@Jakarta2: 46 posts, 148 likes received
@andreas: 29 posts, 107 likes received
@ericmarceau: 28 posts, 98 likes received
@Jymm: 19 posts, 83 likes received
@guiverc: 9 posts, 40 likes received
@Bombilla: 19 posts, 35 likes received
@Norm24: 6 posts, 25 likes received
@toadie: 6 posts, 20 likes received

Interesting Topics

Activity by the @staff Group

Together these staff contributions balanced practical how‑tos, curation of helpful tools, and community media you can plug into during the week.

Best Reply or Topic of the Week

  • Best Reply: @Jakarta2’s secure‑boot sleuthing in the Linux Mint install thread is an excellent example of clear diagnosis and actionable fixes. In response to a boot failure showing “Failed to start MokManager,” he traced the issue to a pending MOK enrollment and missing mmx64.efi on the media, then outlined a stepwise recovery plan that starts with resetting Secure Boot keys and clearing NVRAM. It is thorough, reproducible guidance that others can follow: Shortly after starting Linux, the text on the display looks encrypted and stops working — Reply #14.

“Once that MOK request is stored in firmware, shim attempts to launch MokManager on the next boot and fails because the required file is not available
 I would recommend the following, in order
”

Honorable mentions go to @suivue for upstream packaging insights in the 26.10 upgrade discussion and to @tkn for the step‑by‑step hardware triage on GPU artifacting and thermals.

Badge Recognition

  • Congratulations to our latest weekly honorees:

Well deserved, and thanks for keeping the conversations helpful and welcoming for everyone.

Thanks for reading. See you again next week! :penguin:


Our community remains free of banner ads thanks to our partnership with Better Stack. There are no ad impression or click requirements. Their ongoing support of the LinuxCommunity.io initiative is something we genuinely appreciate.

Better Stack offers infrastructure observability services, uptime monitoring, logging, incident management, and a free tier worth checking out. Visit: betterstack.com


:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the #site-help or Our Community forum category.

8 Likes

This week in our forums


Key Stats

In the past week, our Linux forums had the following activity and key statistics:

Total New Posts: 259
Total New Topics: 24

Top Members

@Brian_Masinick: 38 posts, 132 likes received
@Jakarta2: 28 posts, 96 likes received
@ericmarceau: 23 posts, 94 likes received
@andreas: 13 posts, 44 likes received
@tkn: 17 posts, 38 likes received
@Ldbennet: 9 posts, 38 likes received
@Jymm: 7 posts, 34 likes received
@ugnvs: 8 posts, 31 likes received
@Bombilla: 16 posts, 25 likes received
@toadie: 5 posts, 16 likes received

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

  • Best Reply: @ericmarceau’s clear, step-by-step recovery in Black screen GRUB prompt after updates stood out for speed and precision. His live-ISO approach with grub-install followed by update-grub resolved @Ldbennet’s first-week boot failure in minutes, and the thread layered on a gentler Boot-Repair alternative for brand-new users.

    “Once you have identified which device has your bootable system 
 enter:
    sudo grub-install /dev/sdX
    sudo update-grub
    Then reboot. That should fix it.”

Badge Recognition

  • Top Contributor: No new awardee is listed this week. The badge page was recently updated following removal of the gamification plugin. See the badge page here: LinuxCommunity.io

Thanks for reading. See you again next week! :penguin:


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


:warning: Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the #site-help or Our Community forum category.

4 Likes