

Why is the headline so incredulous of the literal developer who authored the patches?


Why is the headline so incredulous of the literal developer who authored the patches?


risk of being eaten
yeah they were


odds are pretty good these days, and if you’re worried dont switch now, but next time you buy hardware buy it with the intention that you may switch and opt for some Linux friendly hardware, which is pretty simple - avoid nvidia and realtek (avoid realtek on windows too if I’m being honest), make sure things are compatible with standards.


why the hell aren’t people running this shit in isolated containers?


you don’t need my permission mate, I honestly don’t know why I have earned your derision??


I also said ublue is free to do what they want, why are you attacking me for suggesting I want to put something back the way it was? I never asked for your attention, I’m not pestering the developers about it, instead I attempted to author a fix for anyone who also is not a fan of the change.
Yes, I dont like a core system tool not being part of my desktop, I dont want my updates to fire via a timer, and I have updated my ostree via discover on my bazzite box. I understand a lot of your target audience does want those things, an appliance type experience - I even suggested 2 posts up that perhaps bazzite was no longer for me as the target audience.
I appologise for drawing your ire
edit: FYI I’m not some bad faith poster, having defended bazaar - Also my particular bazzite box has been rebased between Fedora and Aurora, probably accumulated some artifacts in the process, which may explain why my discover had not been previously hobbled. Have a good night


the ublue project / bazzite decided to make their own flatpak first app store called Bazaar. Fair enough its their distro. However they created it with GTK4/Adwaita libraries, so its a Gnome native app and looks completely ugly on a KDE Plasma desktop. Also as a flatpak first app store it doesn’t update anything else on your machine like what discover is capable of (cant update ostree, knew stuff etc). This means you have to use the ujust terminal app to access updates, which I dont agree with.
I think technically you could layer it back in with rpm-ostree install kdediscover - however this pulls back a couple of hundred meg of plasma dependencies, which if you’re not aware, when you update your system would be redownloaded and reinstalled with each new ostree snapshot, slowing down the update process even further. I I tried doing it as a sysext (myrepo) but it keeps segfaulting and I havent worked out the issue edit: I have fixed the segfault issue and readded the ostree backend. Sysexts are new experienmental alternative to package layering which hold a lot of potential (check out tim ravier’s development of them here https://travier.github.io/fedora-sysexts/)


The removal of KDE Discover has me considering going back to plain Kinoite on my HTPC. I figure I can build a sysext with the handful of bazzite bits I actually use and keep the unbutchered plasma experience
If they dont use wine, they’ll sell you a subscription to a cloud machine running legacy Windows to run your legacy apps in. They already have this product Windows cloud pc is a thing