[–] [S] 4 points 1 week ago (1 child)

Sorry for the inconvenience. I'd like to explain a bit:

Vanilla OS is based on the rolling-release Debian sid, which lets us bring newer features and better hardware support. But that also means some libraries will inevitably be deprecated over time. That's why we always recommend Flatpak as the first option for installing apps.

Regarding the Augest update: that was a major release (Vanilla OS 3 Reunion), and we did everything we could to minimize the migration impact for existing users. The subsystem change is one of the breaking changes we couldn't avoid. The underlying Distrobox v1 is no longer receiving updates and had already been causing quite a few compatibility issues, so we had to move to Distrobox v2. Unfortunately, v2 introduces breaking changes in exporting bins and apps, which meant the containers had to be recreated. We fully understand the impact this has on our users, but this migration is necessary to ensure stability over the next few years.

We really appreciate your feedback, and we remain committed to improving reliability in the future, in line with our original vision of providing an obstruction-free Linux experience for people around the world.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (1 child)

    What are the interesting kernel features?

    I see zfs mentioned and custom optimisation flags, but those seem pretty easy to do in nixpkgs. I didn't look at the patches.

    I guess the binary cache is nice if you want that specific kernel config.

  • source
  • parent
  • context
  • [–] 7 points 1 week ago (3 children)

    It's pretty damn solid. I've been running it on my Framework 13 AMD 7040 for years, and I recently acquired a 64GB Framework Desktop and it's running like a dream on it. Definitely recommend it for (mostly) effortless Arch.

  • source
  • parent
  • context
  • [–] [S] 8 points 1 week ago

    I'm one of the developers here. It's quite common for distros that use non-LTS kernels to ship kernel versions that are already EOL. Fedora, for example, currently ships kernel 7.2 as well.

    As for the delay, you can see from @eleijeep@piefed.social's comment that we need to ensure the OS is stable enough before release. It took us a week to resolve the compatibility issue between kernel 7.2 and our ABRoot, which was preventing the system from upgrading. We shipped the earlier snapshot rather than 7.2.15 just because it's better tested.

  • source
  • parent
  • context
  • [–] 59 points 1 week ago (19 children)

    Man, this distro really blew up. I remember around 2 years ago hearing about it for the first time, and then was like “oh maaaaan, not another arch/endeavourOS/Garuda/manjaro”. Anyway, it’s been my main distro for around 2 years now and I’m never going anywhere. lol

  • source
  • [–] 4 points 1 week ago

    I really liked this distro when I tried it when 3 first released. I’m on Debian stable gnome and may just switch over to get gnome 51 because gnome 48 is feeling a little too old at this point.

    I already use flatpaks for everything so that won’t change much at all anyway.

  • source
  • [–] 2 points 1 week ago

    I've been having the same issues with an arch-derived distro and it also gets stuck, leading me to believe that the issue's on flatpack's distribution end.

    (I use shelly for my updating, and it works fine for pacman and AURs, but at least for the past day it's hung up on flatpacks. I also tried running "flatpack update" in bash with no results.)

    Because of that I don't think there's any solution other than manual installation until Flatpack solves the distribution issue.

  • source
  • [–] 1 point 1 week ago (2 children)

    I've been using Vanilla OS on my laptop since August 2024. It has been a great experience aside from two major updates breaking my system.

    The first was in June 2025 when an update fucked my mail client and I had to manually edit some config files to fix it.

    The second was in August this year (2026) when the update fucked an important program that I had compiled in, and exported from, the main Vanilla OS container that starts when you start the terminal. For some reason they changed the main container used by the terminal and so everything I had done in the previous one was gone.

    It's annoying that they don't have enough testing to identify these showstopping issues before releasing, but this is the nature of niche distros. The users are the testers.

    Sooner or later I will be reformatting this laptop with something more reliable, but it's unfortunate because Vanilla OS is a great base OS to build on. I hope they can sort out their QA for future releases to prevent issues that break backwards compatibility.

  • source
  • [–] [S] 30 points 1 week ago (2 children)

    it's a bit odd how openai's blog post makes it sound like security bugs in Linux fall in two categories, info leak and local privilege escalation. i would guess that they probably did also ask their model to find some RCEs, but they're selling those to exploit vendors (or perhaps to intelligence agencies directly?) rather than blogging about fixing them.

  • source
  • view more: ‹ prev next ›