I wonder how it compares with duck.ai. They have a comparison chart, but don't include that.
that_leaflet
Yup, just another hot fix update. There's been 4 of them so far this series. 1.21.1, 1.21.3, 1.21.7, and now 1.21.8.
A system that has updated from say Ubuntu 16.04 to 24.04 is different from a system that fresh installed Ubuntu 24.04.
The upgrade process is imperfect. It may keep older software around, old configuration files. Users may also make small tweaks and forget about them.
I remember like a year ago OpenSUSE Tumbleweed broke for users who had old installs. They were using the old networking stack, the upgrade system never migrated them to the newer networking stack. And since OpenSUSE’s test suite was only made up of new installs, the issue wasn’t caught until after it was released.
Fedora Atomic tries to solve this issue. When you update, the entire root filesystem is effectively replaced (the immutable parts anyway). Though it tries not to touch manual changes you make in places like /etc. It does something called a 3 way merge to preserve your changes and does keep better track of them than traditional distros.
I think I had this bug before where I had to change the tty to actually get into the graphical environment.
I used Aeon before, it wasn't bad. The default apps were better than Fedora Silverblue's (it had Tweaks preinstalled, didn't have Firefox installed as an RPM). It uses Distrobox rather than Toolbox, which is nice because Distrobox lets you specify a custom home for each box. Though Distrobox hasn't seen any development these past few months and their decision to use POSIX compliant shell script seems like a maintenance nightmare. Toolbox uses Go.
But my biggest problem with MicroOS is that I don't feel like the update mechanism is as robust as Fedora Atomic. At the end of the day, it's using zypper and btrfs snapshots. It doesn't have the same protections against configuration drift, you can only rollback to versions of the OS you've previously installed (with Fedora Atomic you can rollback to any specific commit, even ones you've never installed).
And Fedora Atomic's bootc is super nice for customizing your image.
As far as I’m aware, Wayland apps can only “steal” focus by going through the proper channel, the xdg activation protocol.
Or maybe it’s a bug with Gnome 43?
I think you need to use Wayland, focus stealing protection set to strict, and no Xwayland apps. Xwayland apps can bypass the focus stealing protection.
This is at least the third time this has happened. There was also a malicious app that was a cryptocurrency miner.
I don't know how Canonical can take themselves seriously when it comes to Snap. It's beyond embarassing. Their near complete lack of moderation has hurt people over and over again.
Heroic is really nice and what I recommend, but the UI is a bit clunky and spread out.
Strange. Discord, ProtonMail, ProtonUp-Qt, and Spotify should all work perfectly. Except maybe some drag and drop issues for Discord and ProtonMail? And Discord's activity status is blocked from tracking you. What issues did you have specifically?
I can see OpenRGB having issues given that tries to talk to the hardware itself, did you install the udev rules?
Handbrake has access to all your files by default so that shouldn't be an issue.
What Flatpaks did you have issues with?
Probably the biggest one is the next piece of the Wayland session restore puzzle clicking into place: David Edmundson has implemented support for the
xx-session-management-v1
Wayland session restore protocol in Qt 6.10! This means that software built on top of Qt 6.10 (for example, Plasma and KDE apps) will be able to start implementing the protocol themselves. Once they do, then finally real session restore will work on Wayland
I hope we’re able to opt out of apps positioning their own Windows. My favorite thing about Wayland is that apps can’t control where their windows open, so they always open in a consistent location chosen by the compositor.
Annoys me whenever I use Windows, MacOS, or Xwayland apps that open up in seemingly random locations.
A group called Collective Shout lobbied payment processors and banks to stop supporting platforms like Steam and Itch.io due to some NSFW content on them. So Steam and Itch.io responded by removing the offending content.
So pretty much Steam and Itch.io were being forced to censor legal content, hence people are angry. Collective Shout markets themselves as feminists fighting for women, but they have ties to Christian anti-pornography groups, and in reality, probably want to remove as much pornographic and queer media as they can.