Weekly Forum Summary

Our Community
77

This week in our forums…

Key Stats

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

Total New Posts: 192
Total New Topics: 13

Top Contributors

@Brian_Masinick: 25 posts, 82 likes received
@Jymm: 11 posts, 45 likes received
@tkn: 10 posts, 38 likes received
@Itachixkurosaki: 12 posts, 37 likes received
@Watford: 11 posts, 29 likes received
@Frentan: 7 posts, 27 likes received
@Bitpainter75: 5 posts, 26 likes received
@svhs27102: 7 posts, 25 likes received
@RokeJulianLockhart: 8 posts, 23 likes received

Interesting Topics

  1. Typed ed instead of cd - 404 moment (brain not found)
    In General Discussions, @hydn admitted to a classic terminal slip, launching ed instead of cd and briefly panicking at the unfamiliar prompt. The thread turned into a collection of “oh no” stories, from @tkn running commands in the wrong SSH window to @Frentan repeatedly typing cwd instead of pwd. The discussion also became practical, with @andreas asking how to visually distinguish SSH sessions and members recommending color‑coded tools like Termius, Remmina profiles, custom SSH background helpers, and informative prompts to stay oriented across multiple servers.

  2. Ubuntu Core Desktop
    @Jymm started a timely Ubuntu discussion on Canonical’s revived Ubuntu Core Desktop and whether anyone wants a snap‑only, immutable system. The thread quickly broadened into a thoughtful debate. @Itachixkurosaki highlighted the benefits of an atomic desktop model, phone‑style permissions, and the KDE collaboration, but questioned the app story when strictly confined snaps are mandatory. Others like @tkn and @Brian_Masinick weighed trade‑offs around snaps, installers, flavor options, and long‑term direction, while @guiverc provided useful detail about flavor choices and snap‑free install options already available.

  3. Need Urgent Help - USB Stick recovery
    In #help-support, @ericmarceau faced a failing USB stick throwing I/O errors and refusing to mount. The community rallied with layered recovery advice. @benowe1717 suggested filesystem checks and Photorec, which immediately started showing promise. @ClaudioDC shared a successful workflow using ddrescue to image an “unreadable” stick, then mount the image to recover files with their original structure. @Jymm added diagnostics around lsblk, lsusb, dmesg, plus realistic expectations for physical flash failures. Follow‑ups from @ericmarceau documented ddrescue behavior and limitations, giving this thread long‑term value for anyone hitting similar storage issues.

  4. SourceDock – I built an open-source Linux package manager with GTK 3
    In Showcase, @aliafacan introduced SourceDock, a GTK 3 desktop application that unifies APT, Flatpak, Snap, and local .deb management behind a single responsive interface. After a warm welcome from members including @Bombilla and @Brian_Masinick, the thread evolved into a hands‑on feedback loop. @tmick tested SourceDock on Debian Testing with MATE, reported bugs and behavior around sudo and GTK recursion, and then verified that the subsequent v1.4.7 release fixed those issues across multiple Debian versions. It is a good example of community testing directly improving a fresh project.

  5. Unzipping options
    @Watford opened a General Discussions conversation asking who uses PeaZip versus other archive tools. Members compared approaches from GUI‑first to terminal‑only workflows. @Frentan described PeaZip as a feature‑rich “gold standard” yet still relies on Ark under KDE for convenience, while @Jymm adopted PeaZip after issues with Engrampa’s 7zip handling. Others, like @Halano, stick with 7z and unzip from the command line. A side discussion about Flatpak versus .deb, and the risks of third‑party PPAs such as XtraDeb, turned the thread into a broader practical look at how people prefer to handle compressed files.

  6. A MUST read: Debunking zswap and zram myths
    In news, @hydn shared Chris Down’s detailed article on when to use zswap versus zram. The post pulls out key operational points that matter for both desktop users and server admins: why zswap is often the safer default, why combining zram with disk swap can backfire, the cgroup accounting problems zram brings to servers, and the importance of coupling zram with a userspace OOM daemon. @tkn chimed in to confirm zswap is already enabled in their environment, making this a succinct jumping‑off point for anyone revisiting their swap strategy.

  7. XorMon: open source, on-prem monitoring for pretty much your whole stack
    Also in Showcase, @hydn highlighted XorMon, a free on‑prem monitoring suite from Xorux that targets a broad mix of servers, storage, SAN/LAN gear, backup platforms, databases, hypervisors, and cloud or container platforms. The overview outlines how XorMon unifies metrics and capacity planning across technologies many members run at work or in homelabs. Combined with @pave1’s earlier note about XorMon in the long‑running monitoring tools topic, this gives operations‑focused readers a concrete project to explore beyond the usual Prometheus and Grafana stack.

  8. Why has flatpak search been so slow, a few times?
    In #fedora, @RokeJulianLockhart dug into an instance of flatpak search taking over three minutes to complete, backed by timing data and strace output. @Brian_Masinick suggested wider network turbulence as a possible factor, while @tkn raised the idea of problematic modem chipsets. @Itachixkurosaki then provided a highly technical analysis, showing from the real/user/sys times and ppoll behavior that Flatpak was mostly blocked waiting on a single file descriptor, likely a slow or rate‑limited Flathub connection during appstream fetches. Practical commands for future debugging rounded out a strong example of collaborative troubleshooting.

  9. Another Way to Clear the Terminal Screen
    In the mate category, @DeanHighland shared It’s FOSS’s tip that Ctrl+L clears the terminal screen while keeping scrollback accessible, in contrast to the usual clear. @jaymo_chicago quickly confirmed it works at least in konsole, and @Itachixkurosaki stepped in with a clear explanation that this shortcut is provided by the shell, not the terminal emulator. The reply covered how clear and clear -x differ, why shells behave consistently across terminals and SSH sessions, and even reminded users about reset when a binary dump scrambles the display.

  10. Linux installation
    In Debian, a previously opened thread on getting Kali Linux running on a Dell Latitude gained a key follow‑up this week. Building on earlier advice from @machiner, @Itachixkurosaki tracked down a Fedora thread with the same Intel AX201 Wi‑Fi card and timeout error, and pointed to Intel AMT in the BIOS as the root cause. The recommended fix was simply to disable AMT under BIOS manageability, which frees the wireless card so Linux can claim it. The reply illustrates how cross‑distro research can solve stubborn “device is unclaimed” errors without resorting to kernel downgrades or manual driver hacks.

Activity by the @staff Group

Staff remained active across support, infrastructure, and project feedback topics throughout the week.

In #help-support, @benowe1717 gave detailed recovery guidance in Need Urgent Help - USB Stick recovery, covering safe use of e2fsck, filesystem‑specific tools, and introducing Photorec as a practical option when hardware is failing. Their input helped @ericmarceau move from stalled dd attempts toward viable recovery steps.

In Showcase, @tmick spent significant time testing and improving new tools. In SourceDock – I built an open-source Linux package manager with GTK 3, they reproduced problems on Debian Testing with MATE, opened bugs upstream, and then verified that SourceDock v1.4.7 corrected GTK and privilege handling issues on multiple Debian versions. In :rocket: Tired of GDebi crashing? I built a lightweight, visual wrapper for local .deb installs!, they helped debug launch issues on Debian Testing, eventually tracing them to graphics driver and EGL problems with Nouveau.

On the site operations side, @hydn handled a subtle content issue in Onebox preview images do not render in #site-help. After @RokeJulianLockhart noticed that onebox thumbnails rendered correctly in the composer but not in the final post, investigation showed Discourse had cached failed image downloads and stopped retrying. Clearing the failed records and rebaking topics restored previews, and @hydn enabled the Solved plugin in that category to make resolutions easier to find in future.

Staff also continued shaping the community’s monitoring and tooling conversations. In Free and open-source Monitoring tools for Linux, @hydn acknowledged @pave1’s suggestion of XorMon and then followed up with a dedicated showcase thread XorMon: open source, on-prem monitoring for pretty much your whole stack so the project has a clearer home. In SourceDock – I built an open-source Linux package manager with GTK 3 and other showcase items, staff welcomed new builders and encouraged deeper integration testing.

Finally, @system continued its regular editorial work, publishing automated roundups such as Saturday Showcase: Built & Shared by Members This Week and Linux Weekly News: Key Stories Ahead of This Week. These highlight member projects like SourceDock and Riff, as well as notable kernel and distro news, helping keep the community aligned on what is new and worth exploring.

Best Reply or Topic of the Week

Best Reply: @Itachixkurosaki’s deep dive into flatpak search slowness

In Why has flatpak search been so slow, a few times?, @Itachixkurosaki provided an exceptionally clear, evidence‑based explanation of what was happening under the hood. By interpreting real/user/sys timings and strace output, they showed that flatpak search was spending almost all its time blocked in ppoll on a single file descriptor, likely waiting on a slow or rate‑limited Flathub connection during metadata updates. The reply also recommended concrete diagnostic commands (strace -f -tt -T -yy, flatpak --log-session-bus) for future incidents and clarified which logged signals were noise. It stands out as a model for turning a frustrating, intermittent performance issue into an understandable and debuggable scenario for other users.

Top Contributor

Congratulations to @Itachixkurosaki 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