• 39 posts
  • 6 comments
Joined 8 months ago
Cake day: November 6th, 2025

Graphics drivers in Flatpak have been a bit of a pain point. The drivers have to be built against the runtime to work in the runtime. This usually isn’t much of an issue but it breaks down in two cases:

  1. If the driver depends on a specific kernel version
  2. If the runtime is end-of-life (EOL)

The first issue is what the proprietary Nvidia drivers exhibit. A specific user space driver requires a specific kernel driver. For drivers in Mesa, this isn’t an issue. In the medium term, we might get lucky here and the Mesa-provided Nova driver might become competitive with the proprietary driver. Not all hardware will be supported though, and some people might need CUDA or other proprietary features, so this problem likely won’t go away completely.

For those with fond memories of Puppy Linux as a very lightweight Linux distribution, released last month was a new TrixiePup64 for continuing the Puppy Linux spirit atop Debian. The new TrixiePup64 is based on Debian 13 components while shipping in both X11 and Wayland flavors. Out now is TrixiePup64 2601 as the latest iteration of this lightweight Linux distribution.

TrixiePup64 2601 is now available in pulling in the latest Debian packages while continuing to use the Linux 6.12 kernel and other components found with the Trixie release.

Some projects keep surprising me with their “solutions,” and this is one of those cases. A proposal under review by developers from GNOME and Mozilla could change how middle-mouse-button paste behaves on Linux and other Unix-like systems.

The discussions, visible in Mozilla’s Phabricator revision D277804 and a linked GNOME gsettings-desktop-schemas merge request, focus on disabling the traditional primary selection paste by default.

Mozilla proposes changing the default behavior of the Firefox browser on Unix builds so that pressing the middle mouse button no longer pastes text by default. The author of the revision frames the current behavior as a source of confusion and accidental pastes, especially when users press the middle button without expecting the clipboard contents to be inserted into text fields.

A set of 36 patches sent out overnight is making big improvements to the Linux kernel’s AES library. The patches allow for making use of the kernel’s existing architecture-optimized AES code for better performance, that code is also constant-time, lower memory use, and all-around a nice improvement over the status quo.

Google engineer Eric Biggers has been responsible for many very nice Linux x86_64 performance optimizations in recent years around the kernel’s crytographic “crypto” subsystem. His latest work for kicking off 2026 is enhancing the Advanced Encryption Standard (AES) cipher library code.

Besides Debian’s aging bug tracker interface, another challenge as the Debian Linux distribution project begins 2026 is that all volunteers have left their Data Protection Team. The Debian Data Protection Team deals with General Data Protection Regulation (GDPR) issues and related data protection/privacy related matters.

A few days ago a call for volunteers was sent out by Debian Project Leader Andreas Tille to join the Data Protection Team. Debian’s Data Protection Team was established back in 2018 for dealing with European data protection legislation like the GDPR. But all three delegated members of the team recently stepped back.

The newest open-source Apple Silicon driver being submitted for review in working toward its inclusion in the mainline Linux kernel is the Apple Silicon SMC power driver for being able to expose MacBook battery power metrics as well as AC power adapter status reporting under Linux.

Michael Reeves posted the set of patches today for the nearly 900 lines of code power driver for Apple’s System Management Controller. This new “macsmc-power” driver allows for the Linux kernel to report the AC charging status as well as battery status and power metrics to user-space. This driver is based on code for the out-of-tree driver within the Asahi Linux kernel tree but then refactored for upstream inclusion, The revised code also better handles newer Apple System Management Controller firmware, devices without batteries, and other improvements.

Following the holidays, Linux 6.19-rc4 was released today in working toward the Linux 6.19 stable kernel release in early February.

Among the fixes to land during this New Year’s holiday week were fixing broken MediaTek WiFi driver support for the MT792x wireless hardware and many smaller fixes throughout kernel space. Outside of the typical fixes, there were also several Dell-Alienware, ASUS, and Uniwill / TUXEDO laptop additions via the x86 platform drivers pull where just new device IDs were needed.

  • I specified already, people see the instances you post from and builds recognition for that due to the volume with which i post. So I rotate around which ones I post from

    when you use these accounts to post to huge instances like lemmy.world (which you do frequently)

    I haven’t posted to a .world comm (with the exception of linux_gaming) since the JL fallout and have moved quite a few of the comms I created there off it and am planning to move some of the larger ones I mod off there

    although I’m not convinced it’s really a problem.

    It actually did happen to me, and they were spouting right-winger Nazi bullshit sooo yea. Turned out it was UM (unsurprisingly) lmao

    And btw some of those accounts in your screenshot are the imposter accounts like Lonestar, az.social and pawn

    But some of the others I don’t post from much if at all and just make comms with them

  • Oh I don’t do that for that, there’s multiple reasons, but one of the bigger ones is to promote smaller instances because of the volume of posting it makes smaller instances more recognizable.

    Other reasons for the multitude of accounts include making comms on fitting smaller instances (I make programming related comms on programming.dev or retro related on retrolemmy for example), protecting against the imposter problem and better interconnecting wayward smaller instances (you’d be surprised at the number of, even common comms, that smaller instances are missing out on that I discover just through my posting)

  • I do crosspost all .ml content and tag the user if it’s OC, as part of boycotting efforts against .ml. It shows in the crosspost section of your client

    Not that it’s relevant in this particular case, this is my own sourced article not posted before to the Threadiverse

    Why am I cross-posting .ml content?

    I cross-post from .ml to the nearest relevant non-.ml comm to reduce the influence of .ml comms and indirectly, the instance as a whole, to make it an easier decision for other instance admins to defederate because one key reason I identified that admins don’t want to defederate is because .ml still has some very large comms and some niche comms.

    Megathread on the issue

    Some highlights from the link:

    "Don’t worry guys, the Uyghur Genocide was REALLY just birth control! ~dessalines, .ml admin, dev https://lemmy.world/post/30580167

    “See! nobody died IN Tiananmen Square, just AROUND it, so it doesn’t count!!” ~ Davel, .ml admin https://lemmy.world/post/30673342

    .ml admin, Nutomics continued transphobia https://lemmy.world/post/29222558 The original transphobic Comment from Nutomic: https://lemmy.world/post/18236068

    “NK is actually good and anything counter to that is Western propaganda!” ~dessalines, .ml admin, dev https://lemmy.world/post/31595035

    General negative sentiment to other instances who haven’t “seen the way” yet ~davel, .ml admin https://lemmy.world/post/27426510

    “If you don’t support Russia then you just don’t understand geopolitics” ~dessalines, .ml admin, dev https://lemmy.world/post/27352415

    And so so much documentation on clear heavy handed censorship and bias also on the link. So much I can’t even put them all here because this comment would be really long.

    I believe the behavior of its admins (the main admins are Lemmy devs) does harm to the overall growth of the Lemmy-verse and maybe even the Thrediverse (since Lemmy kinda kicked off the Thrediverse) because of its association with the devs of Lemmy and their insistence to use .ml as their personal political platform to spread harmful propaganda

    On the outside, bringing up Lemmy frequently leads to comments like “Lemmy? Isn’t that the place with a bunch of tankies?” Or “Tried Lemmy, but found it full of pro Russia crap so I left”. The best way forward from that I see is to either widely defederate from .ml like the rest of the Triad, or pressure them to put a fair and unbiased as possible admin team.

There’s no doubt that 2026 will bring plenty of new Linux releases, with Ubuntu 26.04 LTS likely being the most anticipated, set to arrive at the end of April. But this article isn’t about the usual names that tend to dominate the conversation year after year.

Instead, I want to focus on two relatively new projects that left a strong impression on me in 2025. What sets them apart is their originality: they aren’t built on top of existing distributions, and they take genuinely fresh approaches to how a Linux system can be designed and function.

And no, this isn’t about the wave of immutability that defined much of 2025, nor about distributions overloaded with tools in an attempt to be everything to everyone.

Today, Manjaro Linux has officially pushed a new stable update, marking the release of Manjaro 26, code-named Anh-Linh. The headline change is the move to Plasma 6.5 and GNOME 49, both now configured to use Wayland by default.

Users who still rely on X11 sessions, particularly for legacy workflows or hardware, are advised to review the project’s known issues before rebooting. For systems that require continued X11 support, the XFCE edition remains the recommended option.

Graphics support is another major area affected by this release. Manjaro now ships NVIDIA driver version 590.48.01, which drops support for older Pascal and Maxwell GPUs. Only Turing-class hardware and newer are supported by the 590xx series.