That was there before 133, don’t remember the exact release that added it.

Cinnamon’s accent color support works by changing the GTK theme, which Firefox would follow.

The Firefox 133 update changes the accent color without changing the GTK theme, I believe it’s following the accent color portal.

I do like Files, but I sometimes struggle to use it. I've used multiple versions of Files, and during that time they've moved around buttons and actions multiple times.

I've had two XFX cards, an RX 480 and 6700 XT. Didn't have issues with either one, no coil whine with the fans.

It's just the standard Flathub version.

I also did a test to make sure it was nothing else. I reverted back to 132, create a new profile, and verified that it didn't respect my accent color. Then I updated back to 133 and verified that it was now respecting my accent color.

Bizarrely enough, I think KDE apps also read that info from ~/.config/gtk-3.0/gtk.css. So use Flatseal, KDE’s settings, or the CLI to give all apps access to that file.

True, although not in the same way. KDE is using its own GTK theme and uses ~/.config/gtk-3.0/gtk.css to override colors to the accent color. But this method is broken for sandboxed versions of Firefox since they can't access ~/.config/gtk-3.0/gtk.css (though with flatpak you could create an override to allow it).

I believe (and hope) Firefox is now following the standardized accent color portal for determining the accent color. If so, then this accent color change should work on Gnome, KDE, Pantheon, and other desktops that support the accent color portal. If true, then even sandboxed apps should follow the accent color without messing with the sandbox.

You’re up to date. Staging refers to the updates they release every 2 weeks.

That’s in contrast to the stable releases they release once a year, which incorporates all the development that happened in the past year of staging updates.

Fixed the title.

Good for those who want Wayland native windows.

But as with new code and features, it may have bugs. I wouldn’t be surprised if some distros make it default back to Xwayland instead.

The big thing it has going for it is that they set up btrfs snapshots out of the box so you can rollback if necessary.

They also do more automated testing than Arch so theoretically it should be more stable.

No, you are never specifying to actually upgrade the package with the 'u' flag. Running pacman -Sy archinstall would upgrade the package, since it would first refresh the package cache then reinstall the latest version.

Also, there's not really a benefit to using 2 'y's but it does add some extra stress to the package mirrors, so I would avoid doing that.

Current Arch ISO is from November 1, so you likely used the old version (unless you used pacman -Syu before you used in the installer).

Flatpak firefox stores that stuff in ~/.var/app/org.mozilla.firefox

1. Flatpak, create a shell script to call the flatpak command and pass arguments
2. If the app doesn’t work well as a flatpak or isn’t packaged, I would use distrobox
3. If the app doesn’t work well in distrobox, I’d rpm-ostree install it
4. If I’m feeling fancy, I might look into installing homebrew. But you need to do some workarounds with PATH and homebrew otherwise it can break things; Universal Blue includes these workarounds out of the box

Fedora Silverblue

• I like Gnome
• I like that Fedora adopts new technology quickly
• I like how it makes updates more reliable
• I like flatpak

Preferably the drivers and quirks of the hardware would all be patched upstream so that you don’t need to use a distro with the fixes patched in.

Mac Mini doesn’t come with a keyboard. So unless you’ve owned an iMac or bought a keyboard separately, you won’t have that convenience.

That being said, I haven’t touched the power button on my Mac Mini since I got mine on the 8th.

“Boiling The Ocean” refers to the fact that this is what all the hackfest topics share in common: They’re all very difficult long-term efforts that we expect to still be working on for years before they fully bear fruit. A second, mostly incidental, connotation is that the the ocean (and wider biosphere) are currently being boiled thanks to the climate crisis, and that much of our work has a degrowth or resilience angle (e.g. running on older devices or local-first).

https://blogs.gnome.org/tbernard/2024/10/05/boiling-the-ocean-hackfest/

I'm just saying that I think it would be more accurate to group Gnome closer to Windows and KDE than MacOS. Especially if Dash to Dock and Appindicators are enabled, like in Ubuntu.

I could switch between Gnome, KDE, Windows, and most Linux DEs relatively easily, but MacOS's feels quite different to me.