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

This week in our forums…

Key Stats

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

Total New Posts: 325
Total New Topics: 30

Top Contributors

@tkn: 28 posts, 100 likes received
@andreas: 19 posts, 77 likes received
@Brian_Masinick: 26 posts, 74 likes received
@Jymm: 20 posts, 73 likes received
@ericmarceau: 30 posts, 70 likes received
@ugnvs: 16 posts, 58 likes received
@rogerp: 15 posts, 42 likes received
@pavlos: 11 posts, 37 likes received
@toadie: 10 posts, 35 likes received
@shybry747: 6 posts, 21 likes received

Interesting Topics

  • In General Discussions, @Zulan shared a candid pair of learning moments in Two near-disasters in two weeks - what’s the most panic-inducing mistake you’ve made on Linux?. Members chimed in with their own war stories. @tkn restored a nuked system with a single ubuntu-mate-desktop install, while @J_J_Sloan recalled a root cron job that expanded an undefined variable and ran rm -rf in the wrong place.

    cd $SCRATCH_DIRECTORY && rm -rf *
    The thread mixes practical recovery tips with seasoned advice from @ugnvs, @Brian_Masinick, and others on backups and careful habits.

  • @glitch86x asked for distro guidance in Debian with Help me to choose. The community explored Debian versus Ubuntu tradeoffs. @Halano and @pavlos pressed on use case first, @Jymm shared a clear Debian-vs-Ubuntu comparison, and @guiverc wrote a thoughtful deep dive on release cadence, package freshness, and stability paths. A great thread to bookmark if you are deciding between these two.

  • In #linux-support, newcomer @wobbly_lemon sought a GUI-friendly encryption approach in Encryption tool help. The accepted answer by @hydn highlighted age for simple CLI use and Cryptomator or gocryptfs for user-friendly vaults, with practical follow-ups from @tkn, @andreas, @Jymm, and @Norm24 on 7z, PeaZip, and Engrampa versions. It is a compact roundup of cross‑platform encryption choices.

  • @Jordan.cc started a timely browser security conversation in General Discussions with What do you think about LibreWolf?. @tkn recommended LibreWolf for banking and sensitive logins thanks to sane defaults and uBlock Origin out of the box. @andreas contrasted it with Brave, citing multiple concerns and links, while others suggested Firefox or Ungoogled Chromium when site compatibility demands a Chromium base.

  • Homelab fans will enjoy the #linux-support thread What server operating system should i switch to? from @Koylerlowtier. @andreas and @benowe1717 vouched for Debian’s stability with Docker, @tkn advocated KISS on servers with minimal GUIs, and @hydn showed a pragmatic Ubuntu LTS + free Pro ESM approach for long-lived systems. @IronRod shared a tested services list running rock solid on Debian.

  • In #arch, @BoboTheHobo asked for a more “set and forget” experience in Something more handholdy than Arch. Suggestions ranged from Arch-adjacent picks like CachyOS and EndeavourOS to non-Arch but tidy options like Fedora or Debian LTS. @Jymm flagged the ongoing AUR incident as a cautionary note, while @benowe1717 explained CachyOS’s LTS kernel option for a steadier ride.

  • A multilingual #linux-support exchange unfolded in Uscita audio dummy. @Alby had “Dummy Output” audio on Linux Mint XFCE. After language-bridging help from @tkn, @andreas, @ericmarceau, and @toadie, the fix landed: updating to a newer kernel (7.0) restored audio. A nice example of friendly collaboration across languages.

  • @hydn showcased a fast, private sync tool in Showcase with Syncthing - continuous file synchronization. It clicked for quick desktop-to-laptop syncing with no central server. @andreas compared it to a Nextcloud setup, and @toadie shared how Syncthing keeps Obsidian notes and mobile camera photos instantly in sync across devices.

  • In Showcase, @Dima posted a research-heavy benchmark in Peakload benchmarks for operating systems, using System V semaphores to drive extreme concurrency and compare Linux kernel performance with their custom VMs. @ericmarceau asked incisive questions on context and applicability, and @ugnvs pointed to Linux’s dominance in supercomputing for perspective. The authors shared GitHub resources for reproducibility.

  • @cybermaxpower unveiled a clean, Pantheon-inspired look on MX Linux in Debian with My Custom “Pantheon Hybrid” Layout on MX Linux. With Nemo, a refined top panel, and Plank Reloaded, the MX + Xfce setup nails a polished daily driver vibe. @tkn and @Norm24 applauded the aesthetics and asked about themes and icons, which turned out to be Papirus-Dark with MX’s folder color tool.

Activity by the @staff Group

Best Reply or Topic of the Week

  • Best Reply: @ugnvs in Using SNAP command - how to force messaging to log file?
    The reply distilled a classic shell redirection pitfall into a crisp, reproducible example, showing that ordering matters when redirecting stderr and stdout.

    $ snap list junk 2>&1 > snap_err.txt
    error: no matching snaps installed

    $ snap list junk > snap_err.txt 2>&1
    $ cat snap_err.txt
    error: no matching snaps installed
    A small fix with big impact for logging and scripting reliability.

Badge Recognition

  • Congratulations to @tkn, the most recent recipient of the Top Contributor badge. Keep up the great posts and helpful insights. See the badge page for details: Top Contributor

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.

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: 179
Total New Topics: 13

Top Contributors

@Brian_Masinick: 15 posts, 39 likes received
@Jymm: 11 posts, 38 likes received
@ericmarceau: 10 posts, 33 likes received
@Bombilla: 23 posts, 29 likes received
@Powder: 6 posts, 19 likes received
@toadie: 6 posts, 18 likes received
@tpmcd: 5 posts, 17 likes received
@IronRod: 4 posts, 15 likes received
@NothingConspicous: 6 posts, 15 likes received
@system: 3 posts, 13 likes received

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

A clear indicator in your specific situation is the fact video is frozen and audio (sometimes) continues. That, combined with the fact you can ssh in, clearly identifies the issue as a video freeze not a system freeze…

Top Contributor

Congratulations to @Jymm on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 196
Total New Topics: 14

Top Contributors

@Brian_Masinick: 22 posts, 67 likes received
@DenalB: 23 posts, 64 likes received
@andreas: 14 posts, 45 likes received
@ericmarceau: 13 posts, 39 likes received
@Jymm: 8 posts, 28 likes received
@Norm24: 3 posts, 20 likes received
@Bombilla: 17 posts, 18 likes received
@pavlos: 3 posts, 18 likes received
@rogerp: 7 posts, 16 likes received
@toadie: 4 posts, 14 likes received

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

Clear steps, results, and caveats make this a great reference for similar hybrid-GPU troubleshooting.

Top Contributor

Congratulations to @Brian_Masinick on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 187
Total New Topics: 13

Top Contributors

@Jymm: 15 posts, 55 likes received
@DenalB: 16 posts, 42 likes received
@ericmarceau: 13 posts, 39 likes received
@Norm24: 7 posts, 32 likes received
@Bombilla: 17 posts, 21 likes received
@Brian_Masinick: 7 posts, 19 likes received
@toadie: 8 posts, 17 likes received
@Bobsa57: 4 posts, 16 likes received
@shybry747: 4 posts, 15 likes received

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

Top Contributor

Congratulations to @Jymm on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 120
  • Total New Topics: 10

Top Contributors

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

Top Contributor

Congratulations to @Jymm on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


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

2 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: 202
  • Total New Topics: 18

Top Contributors

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

  • Best Reply: @Norm24’s concise, source‑backed explanation in the firmware thread clearly guided readers through a sensitive update path and linked official resources. Read it here: https://linuxcommunity.io/t/-/10564/2

Top Contributor

Congratulations to @Jymm on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 201
  • Total New Topics: 19

Top Contributors

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

  • Solution sleuthing that saves a printer install: @SilentTiger254 tracked down a usable PPD from a Proton prefix to get an Epson L3550 working on Nobara. The step-by-step notes and verification checks make this a standout fix for printer headaches on Fedora-likes. Read the accepted answer here: Epson L3550 on Nobara(Fedora) — solution.

Top Contributor

Congratulations to @Jymm on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 144
  • Total New Topics: 10

Top Contributors

Interesting Topics

Activity by the @staff Group

Best Reply or Topic of the Week

  • Best Reply: @andreas’s concise and effective guidance in Help with Limine pointed @ImInYourWalls to the official Matrix support room and documentation, which immediately resolved their bootloader issue. The follow-up confirmed success and exemplified how directing to upstream channels can get fast, authoritative answers.

“I just got help there and read the documentation. It works now!” — @ImInYourWalls

Top Contributor

Congratulations to @andreas on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 137
  • Total New Topics: 17

Top Contributors

Interesting Topics

Activity by the @staff Group

  • Announcing a tidy way to share timely links, @hydn introduced the new category and clarified how it differs from Articles & Guides in News & Shares forum category :bookmark: (new!). The follow-up explanation helped members choose the right space based on whether they had a personal connection to what they shared.

  • On a tricky suspend issue, @andreas offered practical systemd tips for Nvidia users, recommending enabling resume services to fix black screens on wake (direct reply). Earlier in the same thread, @tkn surfaced a relevant Ubuntu MATE fix guide that several members tried.

  • The automated weekend round-up kept momentum in Showcase, with @system highlighting new member projects and tools in Saturday Showcase: Built & Shared by Members This Week.

  • In the shells discussion, @shybry747 shared their switch from bash to zsh and early impressions, helping frame expectations for casual terminal users (direct reply).

Best Reply or Topic of the Week

  • Best Reply: @benowe1717’s clear, actionable diagnosis for random freezes on resume from suspend, especially on systems with Nvidia GPUs. They explained how the Nvidia service should hook into systemd’s suspend target and what to check in the unit file. The guidance directly addressed the symptom and pointed to a reproducible fix path. Read it here: Weird behavior on suspend — reply by @benowe1717.

Top Contributor

Congratulations to @andreas on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 136
  • Total New Topics: 10

Top Contributors


Interesting Topics

In Showcase, @andreas shared a hands-on hardware project in Simple thermo-hygrometer using an Arduino Micro. The thread walks through using an Arduino Micro with a DHT20 sensor and a 16x2 LCD over I²C, with photos and a linked write-up. @pavlos chimed in with an OLED-based variant and wiring tips, while others appreciated the approachable entry point into microcontroller tinkering.

Also in Showcase, @Halano presented RayMothFM (Next-gen file manager), a speed-focused graphical file manager that leans heavily on keyboard workflows. Features like built-in archiving, checksum tools, image viewing and conversion, and libvips-powered thumbnails sparked interest from @taki_at_gamma_linux, who plans to integrate it into Gamma Linux once version 2 stabilizes.

In General Discussions, @taki_at_gamma_linux opened a creative thought experiment with If you could design your own Linux distro… :penguin:. Members described highly customized, often minimalist systems, including @Halano’s idea for a tightly optimized, bit-packed distro tailored to a single x86_64 machine. The discussion highlighted how personal workflows and hardware shape distribution design choices.

Another lively General Discussions conversation began when @taki_at_gamma_linux asked What’s the first command you type every day? :desktop_computer:. Replies ranged from classic sudo apt update to recovery-oriented sudo dpkg --configure -a, and long chained maintenance commands with apt and fastfetch. Participants like @Jymm, @ugnvs, @guiverc, and @shybry747 compared habits and philosophies around terminal use in daily work.

In Articles & Guides, @andreas shared a reflective piece in Keeping programming fun. The topic links to an external article about using (or deliberately not using) AI for debugging and problem solving in development. @ericmarceau and @pavlos added perspectives on when AI can help versus when it risks dulling one’s own problem-solving skills, and pointed to reliable vendor examples such as Adafruit for microcontroller code.

Over in #linux-support, @GOMpt requested help with HDMI not connecting / mirroring since last 2 Gnome updates on Manjaro. @andreas suggested checking GNOME extensions as a possible culprit, while @Brian_Masinick provided a detailed, methodical approach for using prior backups and incremental updates to isolate regressions. The thread is a good example of structured troubleshooting on a rolling distro.

In General Discussions, @taki_at_gamma_linux floated a more ambitious project idea with What About a Linux Rescue Environment :ring_buoy:?. Building on a real-world recovery incident, the proposal is for a dedicated, distro-agnostic rescue environment with a TUI that guides users through detecting installations, mounting partitions, and repairing systems. @ugnvs and @tkn compared this idea to existing tools like SystemRescue and Boot-Repair while encouraging a workflow-focused design.

The Articles & Guides category featured a thoughtful thread in The joy of simple computing, where recent replies focused on how non-technical family members interact with systems. @DenalB and @DeLinuxCo shared stories of simplifying computing for spouses, including a successful, low-friction Linux Mint setup that quietly replaced Windows and significantly reduced maintenance needs.

In #our, @hydn announced New t-shirt designs in our shop!, introducing the “Userland Collection” of subtle, terminal-themed shirts. The topic highlights designs like uptime and [ OK ] Started Answering Instead of Scrolling. and notes how community purchases and advocate memberships directly help cover hosting and community costs.

Finally, in #linux-support, @appsy opened Bluetooth Missing after a recent Ubuntu update stopped detecting their Bluetooth adapter. The starter post notes that prior attempts using AI tools had not resolved the issue, setting the stage for community-driven debugging focused on drivers, kernel updates, and service configuration.


Activity by the @staff Group

@andreas had a strong presence this week across both help and project threads. In Simple thermo-hygrometer using an Arduino Micro he documented a complete Arduino-based sensor build and later shared configuration habits in What’s the first command you type every day? :desktop_computer:, including an update-system alias that wraps apt and Flatpak updates. He also provided targeted troubleshooting steps in HDMI not connecting / mirroring since last 2 Gnome updates by guiding the OP through GNOME extension isolation.

Staff member @system continued to publish curated roundups and digests. The automated Linux Weekly News: Key Stories Ahead of This Week update surfaced kernel and infrastructure articles relevant to developers, while Saturday Showcase: Built & Shared by Members This Week highlighted community projects like RayMothFM and the Arduino thermo-hygrometer, giving extra visibility to members’ work in Showcase.

In General Discussions and news, @shybry747 contributed to multiple AI and tooling discussions, including Linus Torvalds uses AI to debug an Intel GPU driver bug and What is the default shell of your main distro?. Their posts emphasized treating AI as a tool rather than an authority and pointed out shell features, such as history search, that can meaningfully improve everyday workflows.

From the infrastructure and moderation side, @toadie checked in on their long-running Kubernetes Homelab thread with an update about adding a fourth Raspberry Pi to the cluster. They followed up with practical tool recommendations, like oxker and k9s, plus a linked Ansible course, giving homelab enthusiasts a roadmap for automating and observing small clusters.

Staffers also supported newcomers and site logistics. In Newbies with Questions? …Ask away! and What’s the first command you type every day? :desktop_computer:, staff welcomed new members and helped steer them toward better topic practices and useful resources. These touchpoints, combined with the visible curation and announcements in #our, show @staff continuing to balance technical depth with an accessible, friendly onboarding experience.


Best Reply or Topic of the Week

The standout reply this week is @tkn’s clear explanation of the classic bash fork bomb in What should a new Linux Admin never do?.

In that post, @tkn rewrites the cryptic :(){ :|:& };: function into a readable bomb() definition, then walks through what bomb | bomb & literally means and what it does in practice. The reply breaks down process forking, background execution, and exponential growth of processes in a way that is approachable for newer admins while still being technically accurate. It directly addresses the risks of fork bombs and why process limits matter, making it an excellent teaching resource for anyone learning safe administration practices.


Top Contributor

Congratulations to @andreas on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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: 195
  • Total New Topics: 16

Top Contributors


Interesting Topics

In General Discussions, @J_J_Sloan kicked off a lively language discussion in Programming languages. Members compared Bash, C, Perl, Python, Prolog, Crystal, Rust, and even Julia for sysadmin work and scripting. @tkn and @ericmarceau shared real world Bash and C tooling, while @andreas described moving personal projects to Codeberg and using Python and Prolog in research, giving the thread a great mix of practical and academic perspectives.

Also in General Discussions, @taki_at_gamma_linux asked a thoughtful licensing and architecture question in Why can we make Linux distros, but not really Windows or macOS distros? :thinking:. Replies from @pavlos, @ugnvs, @tkn and others broke down how open source licenses, modular design, and “share alike” terms make Linux highly remixable. The thread also explored how commercial licensing restricts Windows/macOS derivatives and even dug into Intel’s use of MINIX in firmware as a contrasting example.

In Showcase, @Itachixkurosaki opened Just asking for a little feedback on what I can do better to get concrete critique on a self hosted portfolio and résumé aimed at breaking into IT. Detailed feedback from @ericmarceau, @andreas, @rogerp and @ugnvs covered résumé gaps, font size, content density, portfolio structure, voice authenticity, and even OPSEC concerns. The conversation evolved into an in depth look at how to present homelab projects professionally while protecting personal data.

Over in #linux-support, @ericmarceau raised a subtle but important data integrity concern in Writing to USB stick - (Caja) non-sync’ed?. After observing that Caja reported copies as finished while the system was still flushing buffers, they asked how to make completion reflect real writes. @Jymm, @taki_at_gamma_linux, @pavlos, @mrtoo, @andreas and @tkn unpacked the buffering layers, sync behaviour, udev options, user expectations, and even filing an upstream issue. It is a useful thread if you rely on USB storage for backups.

In General Discussions, @taki_at_gamma_linux started a reflective meta thread, Do Linux users overcomplicate simple things? :thinking:. The question contrasted graphical installers with elaborate terminal workflows and asked where “control” ends and “overengineering” begins. Responses by @ugnvs, @tkn and @ericmarceau argued that complexity often reflects exposed options rather than unnecessary complication, and that scripting is both convenience and a form of play for many users.

In Showcase, @Halano presented a lightweight Arch tooling project in Archpkg Browser. The FLTK based GUI makes browsing Arch repositories quick and visually simple. @taki_at_gamma_linux provided feedback and a pull request, and @hydn dropped in encouragement, while @Halano outlined plans for a more distribution friendly file manager to complement the current GPU heavy RaymothFM.

Also in Showcase, nostalgia met X11 in Windows 2000 for X11, where @Halano shared a project that directly draws on X11/Xft to recreate classic Windows 98/2000 era shells. Screenshots and comments from @andreas, @jaymo_chicago, @ericmarceau and @ClaudioDC highlighted both the authenticity of the retro design and the potential to ease transitions for users moving from older versions of Windows to Linux.

In #linux-support, @ericmarceau opened Bluetooth connectivity issue to investigate why only a single Bluetooth speaker worked correctly on Ubuntu MATE while others refused to take over audio. @Itachixkurosaki responded with a detailed walkthrough of PulseAudio/PipeWire profiles, pavucontrol, and A2DP vs HSP/HFP, and later added a follow up on auto switching via WirePlumber once @Norm24 reported a partial workaround through MATE’s sound preferences.

In #community-picks, @benowe1717 documented a substantial homelab milestone in How I Chose to Ready my Homelab for the Upcoming SSL Certificate Changes. The article explains the coming reduction in TLS certificate lifetimes, then walks through automation strategies for lab services. @hydn added a long reply comparing CA signed and self signed certificates, arguing that for purely internal labs, trust distribution matters more than who signs the cert, and the two exchanged thoughts on usability, browser warnings, and when external CA trust really adds value.

In #help-support, @taki_at_gamma_linux published a tutorial style guide, :desktop_computer: How to Set Up a VNC Server with x11vnc — From LAN to Remote Access. The post walked readers from basic LAN VNC to firewalls, SSH tunneling and CGNAT. @Itachixkurosaki then contributed a substantial reply comparing that “classic” approach with modern remote access patterns using tunnels and out of band consoles, followed by @taki_at_gamma_linux revisiting their recommendations in light of CGNAT and security considerations. The exchange turned the thread into a layered look at how to design remote access today.

Finally in Debian, @J_J_Sloan highlighted how widely Debian is used in Debian runs in some important spaces. The topic notes Debian’s role at Google, HP, global NTP servers, cloud infrastructure and CERN’s migration from RHEL to Debian Trixie. @andreas chimed in that this reach really lives up to Debian’s “universal operating system” slogan, underscoring why Debian discussions remain central on the forum.


Activity by the @staff Group

In #our-community, @hydn provided an operations update in Scheduled maintenance—September 20th, 2026. They announced a brief period of downtime for urgent OS livepatching and a Discourse security update, clarified that the larger scheduled upgrade for September 20 remains on track, and confirmed completion once both kernel and forum patches were applied.

Within server, @hydn shared a new article integration in Master Linux Bash History with historyctl, HISTFILE, and Shortcuts, outlining how to enhance Bash history beyond simple arrow key recall. @tmick followed up to say they had learned new techniques from the piece, hinting at members adopting more advanced shell workflows.

In #desktop-apps, @hydn added a practical configuration tip to How to Set Up Hibernation on Linux (Swap Done Right). They described switching an XFCE system to hybrid sleep, documented the tradeoffs between suspend, hibernate, and hybrid, and shared how to extend XFCE’s idle timeout beyond the GUI limit by editing xfce4-power-manager.xml directly.

Across General Discussions and Debian, @andreas and @system helped keep ongoing discussions moving. @system compiled a new Saturday Showcase: Built & Shared by Members This Week recap that pointed readers toward member projects such as @Itachixkurosaki’s portfolio, @Halano’s Archpkg Browser, and the Windows 2000 for X11 shell. This automated highlight post amplifies member work and guides weekend browsing.

Staff also stayed active in welcoming and supporting newcomers. In long running community threads like Welcome! Introduce yourself, @Bombilla and @hydn greeted many first time posters, helping them settle into the forum. In What’s everyone working on? 2026 edition :keyboard: :screwdriver:, @Bombilla welcomed @mr_mcbride while staff and regulars encouraged deeper project sharing in Showcase.

Finally, curation work continued behind the scenes. @hydn featured @benowe1717’s TLS automation write up by moving How I Chose to Ready my Homelab for the Upcoming SSL Certificate Changes into #community-picks, signaling it as a high value reference for others planning for shorter certificate lifetimes.


Best Reply or Topic of the Week

The standout contribution this week is @Itachixkurosaki’s in depth response in :desktop_computer: How to Set Up a VNC Server with x11vnc — From LAN to Remote Access.

In that reply, they:

  • Broke down what port forwarding actually does, using clear analogies that are accessible to less experienced readers.
  • Compared “classic” VNC over exposed ports with more modern, layered remote access patterns that rely on SSH, VPNs, zero trust tools and out of band consoles.
  • Emphasized realistic constraints like CGNAT and ISP restrictions, then mapped those constraints to practical alternatives for homelab and small server setups.

The post builds directly on the original guide rather than contradicting it, and the resulting conversation provides a nuanced, up to date view of how to think about remote desktop access in 2026.


Top Contributor

Congratulations to @taki_at_gamma_linux on earning this week’s Top Contributor badge! :trophy:

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 Better Stack


: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