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

Used in Appimage Manager

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.

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%.

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. >

> 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.

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.

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.

• 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.

For example, I saw a post the other day detailing how to set up a Brother laser printer on Kinoite. That's not something I would have initially considered a potential problem to be solved. Another I ran into some years ago had to do with an Edimax WiFi dongle that used some weirdly specific Realtek 8812 radio, for which you had to set up the driver via dkms. A little prep and knowledge in advance would have saved days of searching online.

I've started a personal to-do list of things to research and make sure I have all my ducks in a row before I make the full-time switch on my main desktop, so besides the usual "back up your files" advice, I'm hoping y'all can point out some QoL things I and others may often miss!

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.

Hi everyone. I'm launching Linguist Translate, an open-source, full-featured translation solution with an embedded offline translator based on the Bergamot Project created by Mozilla.

Site: https://linguister.io

GitHub: https://github.com/translate-tools/linguist

Today, Linguist is launched on ProductHunt. Support the project who really care about privacy: https://www.producthunt.com/posts/linguist-translate

Linguist is not just a wrapper over Google Translator like many other extensions. You can use any translation service with Linguist, thanks to custom translators! You may even deploy any machine translation (like LibreTranslate) on your localhost and then add this service to Linguist.

All features are included: text translation, full-page translation, selected text translation, Text-To-Speech, dictionary, history, and even more.

3 months-old video, but still interesting

With the recently released KDE Plasma 6.1 desktop environment, those still relying on old Intel integrated graphics should have a much more pleasant experience thanks to improvements made to the KWin compositor. For very old Intel integrated graphics, it can effectively be a night and day difference upgrading to the new Plasma 6.1 desktop.

KWin lead developer Xaver Hugl is out with a new blog post about the improved KDE Plasma desktop performance as of Plasma 6.1, which can be especially noticeable with old integrated graphics hardware such as the common Intel graphics in aging laptops. The biggest improvement to bettering the KDE Plasma desktop graphics performance is thanks to dynamic triple buffering support.

tl;dr this allows one to link Pipewire filter chains (such as EQ) to specific devices automatically. Useful for system-wide EQ, noise filters etc, especially multiple filters together. In particular, it all happens transparently so you can just connect to your normal hardware output and it should just work.

You could already do this manually with some work, but this should be simpler and more robust. I suspect this will help with the Steam Deck too, which uses some filters to correct the built-in speakers, and this has caused bugs at times.

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

> A lot of people here seemed excited for these chips. It'll be very interesting to see the gaming performance as this could bring in an entire new segment of portable devices running Linux if powerful enough to deliver solid battery life and CPU performance.

cross-posted from: https://sh.itjust.works/post/21361730

> Hello, I came across zram recently and I'd like to know if I should use it, my laptop only has ~4GB > of ram, and for the most part it'll only stutter when I open multiple programs or a game, so would > zram be adequate in my case? > > Also, would the compressing and decompressing have a significant impact on my cpu?

cross-posted from: https://lemmy.ml/post/17288716

> > This project is a port of the Proxmox Hypervisor on NixOS. > > > > ⚠️ Proxmox-NixOS is still experimental and we do not advise running it on production machines. Do it at your own risk and only if you are ready to fix issues by yourself. > > > >📬 Help / Discussions > > > >There is a matrix room for discussions about Proxmox-NixOS. > > > > Thanks > This project has received support from NLNet.

cross-posted from: https://slrpnk.net/post/10865477

> The Flatpak is already packaged and works well. It just needs to be maintained from a person that joins the Inkscape community. > > This would allow further improvements like Portal support and making the app official on Flathub.

Hello,

I'm taking Japanese lessons online and I need to communicate with my tutor in Japanese via chat.

I've set my keyboard layouts in the KDE settings as English US, French Canadian and Japanese (default). But when I switch to Japanese, I still have an English US layout when I type.

I was expecting it to be more like in Windows where you can switch between Standard alphabet (Romaji), Hiragana and Katakana with a kind of an auto complete.

Am I doing something wrong?

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

> Part one: https://zamundaaa.github.io/wayland/2023/05/18/hdr-and-color-management-in-kwin.html > > Part two: https://zamundaaa.github.io/wayland/2023/12/18/update-on-hdr-and-colormanagement-in-plasma.html