Yes, I know the system updates automatically, but I bet some people still run it. I run it for Flatpaks, for example, as I open my HTPC console once per week and have many Flatpaks that are not updated. When I use the Steam update setting (Game Mode), they never get updated.
The app does its job really well, and I’ve never had a problem with it.
The problem with it is that it’s literally a terminal window.
I understand if it can’t be integrated into the KDE/GNOME settings window, but it really needs to be a standard GUI application that has a list of checks with loading indicators and a green check mark next to them. If advanced users want to know exactly what’s going on, a “Show More Info” button would be totally fine, of course.
But general users need to have a simple window that shows what is being updated and either the percentage of progress or a progress bar.
Yep, you caught me again. You’re pretty good at that …
But the rules are implemented with scripts that I can run from the terminal if I question something.
For example, I added a -v switch to my fedora-python-dx-has-updates.sh script that will allow me to see which fedora packages need updating in that distrobox.
I want to take a moment to address the tone of some of the replies to my original post.
I’m a relatively new user of Universal Blue, and I came here to offer constructive feedback after installing and using the system, feedback meant to improve the user experience for everyone, especially newcomers.
That’s why I find the tone from both @klmcw and @inffy quite disappointing, particularly as one of you is a moderator. Rather than engage with the actual content of my suggestion, the responses came off as dismissive or condescending. Phrases like “build it yourself” or suggesting something is “not needed” don’t foster community or encourage participation. They send the message that new voices aren’t welcome unless they’re contributing code, which is exactly the kind of gatekeeping that pushes people away from open source projects.
Universal Blue promotes itself as “ready to go” and user-friendly. That means making the experience welcoming not only in terms of UI and polish, but also in how we talk to each other. A system that relies on a terminal interface for basic updates is not accessible/understandable to most casual users, and that’s a fair critique to make. It’s not just about my needs as a user, it’s about the long-term sustainability and adoption of the OS.
A casual user should not have to see the terminal to do a basic system update.
I’m asking for more than just a better update UX, I’m asking for a better culture of communication around feedback. You don’t have to agree with every suggestion, but please don’t shoot them down with attitude. If we want to grow this project, that kind of mindset needs to change.
There was no attittude, just my own opinion about updates in general, which are non-intrusivue and hidden from the user in general with uBlue systems (aurora/bluefin).
If someone wants a GUI for it, someone has to write it. Create an issue for it in the github and see if someone takes the job. But there are propably more important tasks for us maintainers than creating a GUI for everything.
Yeah the intent is for no one to ever see that, we used to not have it, all the updates are usually automated. But people want their dopamine hit.
We’re mostly just syadmins, we do need someone to whip up a GUI we don’t have those skills readily on hand. We could bury it in the utilities menu but realistically this gets fixed in the long term by attracting more people to help out.
Stranger things have happened, we got a new app store because someone on the internet decided to fix the problem, who knows what’s possible when people dive in!
A totally reasonable and valid answer. I agree with you, the normal user should not have to see that, but on the update side, he needs something to say that the system is up to date. Even if that something is a simple utility in the icon area that says, “System up to date.”
I’m spitballing, ofc.
Edit: I just read your edit. If I had the skill I would try to develop something for sure.
Those are the discussions that are coming with an explosive expansion of a “distro” (yeah, I know). Many people will give some feedback, and sometimes the answer is simply “we would if we could.” The casual user just asks for a feature, the answer should never be “do it yourself.” If the user could do it himself, he would already be on GitHub doing it. Those who know already do.
I even tried using the Steam Decky plugin’s Flatpak updater, and it detects over 30 Flatpak updates. However, the Steam update menu reports no updates.
I wish I could snap my fingers …