I’ve never had issues with Discover on Fedora KDE and then even when I moved to Kinoite. I didnt have any issues using it on my Bazzite machine. I wanted it back, I also wanted to see if it was something I could do with a SysExt, which as I said is something I’m excited about, as I have started using them to add stuff on my Kinoite work machine.
It doesn’t take Bazaar away, it just puts the items back for anyone who wants it. Spoiled for choice
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/)
I couldnt see one - I also dont want to layer it, because it will pull in a couple of hundred megs of kde dependencies every time you update. I tried doing it as a sysext (myrepo) but it keeps segfaulting and I havent worked out the issue
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
TBF they inherited the Romulan Supernova plot from the movies. If they were going to embrace that I’d have rathered they told it properly instead of alluding to it all the time (prodigy season 2), or picking up after what could have been a compelling story. What’s worse is they keep setting things up and never paying them off - Borgati says there’s a big threat out there, ok tell that story - no. Burnham solves the burn and finds a butt load of dilithium - cool lets see them rebuild the federation - no. Here’s a back door pilot for a series with the Enterprise G on a 5 year mission and Picard’s son is picking up Q trial - no. Here’s a setup for the continuing missions of the Ceritos under jack ransom - no.
Finish a damn story.
Looks a bit shit
I’d be happy if they brought back the wifi toggle instead of making me go into a settings screen
you don’t need my permission mate, I honestly don’t know why I have earned your derision??