I’m not super familiar with sysext, but from my understanding, you’d need to create an additional sysext to include, or find an existing one for DMS (I couldn’t find one).
Your other options would be using rpmtree or a custom image. Theres already a few images out there that are based on Bluefin with Niri + DMS added.
Tbh I’m recalling struggling to find good documentation for sysext. Asking in the ublue discord will probably get you better answers.
Dash’s more significant feature is its speed. It’s not meant to be used in place of bash at all, its meant to be symlinked in place of sh to give you a faster and smaller shell with a simpler and more auditable codebase.
Dash is not a a Bash alternative, it is an sh alternative. You definitely should not replace Bash with it. If your goal is to learn career relevant skills, stick with bash.
weird, I wonder why it worked for me. i havent used it in a while, so maybe I’m misremembering something or something just changed
Is there something wrong with Heroics cloud saves? I havent tried using my saves on a windows system using Galaxy, but they’ve worked across devices running Heroic.
Nah just officially support Heroic, its already great.
“read the changes before installing a major update”
Obviously I dont think people need to read every change log for every piece of software. I do think its a good idea to read the release notes for a major update of your DE thought, since its the piece of software that is going to effect you the most.
And once it is no longer on and has become a setting, they can just remove the setting and force people to drop gsettings and then remove it completely.
What reason do they possibly have to do this? The setting already exists and is feature complete. It doesnt require maintenance. They also noted in the merge request that many RHEL users use it, so RedHat has a financial incentive not to remove it.
They could also instead ask people on first launch. Some people enable telemetry, so they will find out how many people prefer to keep it, which I bet will be most.
They could also just make it a setting. I really dont think it makes a big difference. They can also still use telemetry to see how many users enable it. Based on this thread, I really doubt it will be most.
The first time startup wizard should be kept relatively short and minimal. This just seems like a very unnecessary thing to include.
It will break their workflow for a few seconds before they change the setting back. Or they could read the changes before installing a major update and change it before even doing anything.
Maybe in the future it will be added to the initial setup guide along with stuff like choosing if you want mouse acceleration, but I really dont think its that big a deal.
Do any DEs still have 1 click folder opening by default?
If you add the shortcut at the DE level it definitely should work in every program. Idk if Gnome actually let’s you bind copy and paste though.
It already is configurable, theyre just defaulting it to off. You will be able to turn it back on.
It’s very easy for a user to accidentally paste private or sensitive information somewhere dangerous if theyre unaware of this feature.
The FreeDesktop specification refers to this feature as an “easter egg”, and something like this should absolutely not be an easter egg.
This change would mean disabling it by default and adding a settings entry that actually explains it, making sure users are informed before they can accidentally use it.
And that is the exact reason that was given in the gnome merge request. A user being able to accidentally paste a bunch of text they didnt even know they’d copied incredibly design.
It’d be so easy for them to just add “by default” to the end of the title.
The project already has some paid options with more features: https://xpipe.io/pricing
AFAIK some HDMI to DP converters can be used to work around this. Since the converter is handling the VRR management in its own code, then converting it to DP, there’s no need for a FOSS implementation
deleted by creator
Duh, but now that this has replaced SDDM as the main login manager for plasma, Cachy will likely replace SDDM with it by default.
More details on your GPU and how you installed your drivers would be helpful to understand your issue. You should not need to explicitly enable GPU permissions in every flatpak as some of these comments are suggesting. That is to give apps direct GPU access, which is not necessary for hardware acceleration. A lot of the info in this thread is not accurate.
Sunshine should be able to do hardware encoding for that GPU, it has support for VA-API