Linux

Here is the Youtube video on the topic

The people from uBlue messed something up with the signing, so that updates now dont work.

This is fixable though!

I took the broken updates as the push to move from uBlue kinoite-main to the official Fedora image.

My list of layered packages is now really long, but the chain of trust doesn't involve Github anymore (directly), which was a big concern for me.

rpm-ostree rebase ostree-image-signed:docker://quay.io/fedora-ostree-desktops/kinoite:latest

1. Closed source or open core git forges
2. Open washing
3. Discord
4. Lack of diversity
5. The FSF

KVM is used on Android, ChromeOS and Google Cloud, so this makes a lot of sense.

Video announcement by Chris Wanstrath (GitHub co-founder) of the 501(c) non-profit and $1,000,000 donation: https://www.youtube.com/watch?v=k9edTqPMX_k

OBS can use Pipewire for the mic and desktop sound inputs, but it is not yet packaged on Flathub.

Here is how to add it manually.

Used in Appimage Manager

If you think about productivity, you can't help but think that having the default state of your computer being an image with a few icons on it is less than stellar. For opening files, it will never be tidy enough to give you access to all you need, you need a launcher or a folder structure, meaning the desktop is bad at this. For opening apps, having visual shortcuts on the desktop is a duplicate of whatever panel or launcher you have.

cross-posted from: https://discuss.tchncs.de/post/18099780

Bazzite comes ready to rock with Steam and Lutris pre-installed, HDR support, BORE CPU scheduler for smooth and responsive gameplay, and numerous community-developed tools for your gaming needs.

• Support for asynchronous processing has been implemented. Nodes can choose (or be forced) to be scheduled asynchronously. The graph will not wait for the output of the node to continue processing but it will use the output of the previous cycle (or silence) instead. This adds one cycle of latency but it can avoid having some nodes blocking the processing graph. Non realtime streams and filters now also use this asynchronous processing instead of their own slightly broken version.

• The concept of node.sync-group was added. This groups nodes with overlapping sync-group together when one of them sets the node.sync = true. This is now used to make sure all nodes are scheduled together when JACK transport is started so that they all see the same transport time.

• Config parsing errors are reported earlier and much better with line and column numbers where the parsing started to fail.

• Add support for mandatory metadata when negotiating buffer parameters. This can be used to only negotiate extra buffer planes when certain metadata is negotiated. One use case is the explicit sync support that requires 2 extra fds for the timelines.

• Explicit sync metadata and support was added.

• Support was added for making and using multiple data-loops in the server and clients. Support for CPU affinity and priorities was added to the data-loops as well.

• The log topic debug levels can now be changed at runtime with metadata.

• The log levels in the pulse server can be dynamically changed with a /core message.

• The UCM conflicting devices patches were merged.

• Add snapcast-discover module to stream to snapcast servers.

• Rework how peers are linked and the counters are updated. Resume the peers when a node is unlinked and not yet processed. This should cause less occasional dropouts in the graph when reconnecting things.

• Many GStreamer element updates.

• Many more fixes and improvements.

EDIT: Whoops, looks like a repost.

cross-posted from: https://reddthat.com/post/21374304

cross-posted from: https://reddthat.com/post/21374246

What's new in this release:

• Initial support for user32 data structures in shared memory.
• Mono engine updated to version 9.2.0.
• Rewrite of the CMD.EXE engine.
• Fixed handling of async I/O status in new WoW64 mode.
• Various bug fixes.

cross-posted from: https://lemmy.world/post/17018864

I know this might be a couple months old, but I didn't know we already passed 4%.

Intel sent in as the sole patch for this week's Linux power management subsystem updates is an important fix for Intel Core hybrid systems with buggy firmware. The Intel P-State driver fix can address as much as a 50% performance hit seen with existing Linux kernel versions on affected Intel hybrid platforms.

A Kubuntu Focus developer last week reported a power management issue that breaks scheduling on heterogeneous core Intel systems with buggy firmware. It turns out systems failing to report ACPI CPPC v2 capabilities could lead to very poor performance going all the way back to Linux 5.19. On systems like with an Intel Core i5 13500H and using the EEVDF scheduler, as much as a 50% performance hit could be observed with Geekbench. There have also been other similar bug reports in recent times.

I'm preparing for a new PC build, and I decided to try a new atomic OS after having been with NixOS for about a year.

First I tried Kinoite, then Bazzite, but even though KDE has a lot of features, I found it incredibly buggy, and it even had generally poor performance, especially in Firefox. I don't really have time to diagnose these issues, so I figured I would put in just a little more effort and migrate my Sway config to Fedora Sway Atomic.

I'm glad I did. The vanilla install of Fedora Sway is awesome. No bloat and very usable. I haven't noticed any bugs. Performance is excellent. And it was very straightforward to apply my sway config on top without losing the nice menu bar, since Fedora puts their sway config in /usr/share/sway.

I'm also quite happy with the middle ground of using an OSTree-based Linux plus Nix and Home Manager for my user config. I always thought that configuring the system-level stuff in Nix was the hardest part with the least payoff, but it was most productive to have a declarative config for my dev tools and desktop environment.

I originally tried NixOS because I wanted bleeding edge software without frequent breakage, and I bought into the idea of a declarative OS configuration with versioned updates and rollback. It worked out well, but I would be lying if I said it wasn't a big time investment to learn NixOS. I feel like there's a sweet spot with container images for a base OS layer then Nix and Home Manager for stuff that's closer to your actual workflows.

I might even explore building my own OS image on top of Universal Blue's Nvidia image.

Hope this path forward stays fruitful! I urge anyone who's interested in immutable distros to give this a try.