Bazzite July 2025 Update: Bazaar, Z13, Kernel 6.15, Steam Hardware Survey

This help wanted issue has been around but no one’s working on it:

2 Likes

You’ve mentioned multiple times that you make your own image. None of this affects you, just like none of the deprecations we made last time affected you either.

I don’t know why you’re bringing random dogma from across the internet here, the guy who made that video doesn’t work on ublue, it doesn’t affect us. Why would we care about any of that?

You seem to have a specific view of what you think you want us to be, if you want that future to happen just go do it, you don’t need our permission to build what you want. I can’t even follow your arguments anymore.

4 Likes

Oh I’ve been using Newsflash as its my absolute fav RSS reader but it never occurred to me it can be used for this. Like the idea though!

So theoretically speaking if we added Newsflash to the default flatpaks, autosubscribed the image-relevant feed as a script that runs post install, and then set Newsflash to run at system startup, all users would be notified about threads like this one, right?

And as an added benefit they’d get a cool RSS reader preinstalled :smiley:

3 Likes

Is there a way to push out a notification to the KDE default notification system when important changes are impending?

I just found there is a Decky Loader plugin for this, which is quite cool, I think using the desktop integrated notification system would work great, or a pop up system like how the old Bazzite Portal used to work on initial setup, some may not like it, I know I hate notifications and pop ups, but I think this one would be acceptable.

I don’t think pushing out information over RSS will have any impact on anything, the target market users for Bazzite probably don’t even know what RSS is, I do, but have never even used it for anything, and I have been gaming since the early 80’s.

No? But the points made aren’t imaginary ones? like adding Bazaar will not lead to adding ChatGPT or whatever.

Brother, I wouldn’t be going insane here if I managed to restore Discover and get it running. I tried adding only the plasma-discover-kns and plasma-discover-flatpak ones to the install list, and granularly tried putting packagekit, plasma-discover-rpm-ostree, and plasma-discover-offline-updates in remove list. It still won’t run - I tried this literally five minutes ago. I thought I was doing something wrong and for my sanity, checked a build from more than a week ago before the changes come in… And it works then!

Of course I’m going crazy when the “official” workaround doesn’t even work for me.

Neither is my point imaginary. I have my issues with the practice of removing existing features that works well enough in favour of a beta feature. In general, I have been pretty consistent about my issues being taking away of things - I don’t care when it’s additive and I can ignore it.

I do care when Discover worked fine for me, and the new store can’t even check for updates without locking the entire app and when they make flashing-screen-like effects due to loading immediately as you type (I may not be epileptic, but it is never comfortable for me).

Edit: and of course, just like last time, someone else is being snarky on me, when I have been perfectly good faith and genuine in conveying my issues, which then leads to the thread being locked without a satisfying resolution. Disappointing, but not unexpected at this point.

Also:

sorry for the gen alpha speak but “lil bro mention modern app practices and expect us to ignore it” I was perfectly fine with your point on pushing beta software, it’s whatever I disagree, but I wouldn’t respond if you didn’t say shit like adding app practices or whatever