That was the initial post.
And I still do not know if this is safe (safe != good idea).
Sure it is safe, the system wont fall flat on its face without them, but you will need to do a lot more administrative work without them reminding you about new updates being available regularly …
You will also need to remember to re-install update-manager should you want to upgrade to a newer release later on since this is the only supported path (and the only way to not end up with a mess) for release to release upgrades …
Replacing them with gnome-software you simply need to keep in mind that gnome-software is not shipped or tested at all on Ubuntu anymore so you might encounter bugs here and there due to it not being on the radar of developers or any integration work being done …
5 Likes
It may be safe (perhaps).
Is it a good idea? In my opinion, no.
Not only will you have to reinstall it as @ogra mentioned but it seems like a lot of effort for very little gain.
If you prefer more granular control over the updating element of the system, then maybe consider updating using the terminal or even writing a bash script that can be enabled to run after logon (or whenever you prefer).
2 Likes
I’m not sure what you are experiencing.
Maybe I’m too familiar with the process and the various iterations over the decades, but the Trixie Gnome update experience just doesn’t seem especially different or unusual to me.
Perhaps you might expand on this a bit.
That’s not the point here. Rather using GNOME Software.
I never said it was different with Trixie.
I said Fedora/Debian experience is different.
So, I’m an average user, I see updates in Software with a desktop notification.
I see snap updates, I see deb updates (whatever) in the same place, I just want to update, I click.
I don’t see what really could be simpler.
I heard Erich’s point about apt vs packagekit. Did Debian users recently experience a dependencies issue with Software? That’s a true question, not trolling, I’m by far not an expert on the diff between apt and pk.
For App Center devs: that’s not pro/con Software vs App Center snap, that’s just in my mind a discussion about Ubuntu’s updating way. App Center could certainly do what Software does, and for sure Software has been (is?) problematic on some points vs App Center.
Here’s a concern about Gnome Software from someone on the Debian forums.
I don’t think you can put it that simple, gnome-software uses only appstream metadata which is its own separate software database outside of the distros package db which always carries the potential of things being out of sync, you are using a third party system for updates that isnt deeply integrated with the distros package management but tries to be a generic tool for all distros out there so the potential for possible breakage is bigger …
I personally don’t like g-s simply because I’m not a fan of tools that require a permanently running daemon in my user session just to notify me once or twice a month about available updates instead of using a timer to occasionally invoke a check, but that’s just a personal thing of preferring leaner software, if you do not mind wasting resources on this that indeed should not bother you …
Would I do that switch, I’d personally still check with apt occasionally to make sure there are no low level packages without appstream data that might be missed from being updated … but this is again a personal thing and a matter of how much you trust that “other” db …
3 Likes
Thanks. IIRC, Snap Store v1 (aka Software) had been changed to make it active only if launched? (I’m not sure of this souvenir.)
We have our own issues too.
This one is pending:
Yes, because update-manager already cares for this so you didn’t need it permanently running 
Only starting it on app start and then leaving it permanently running isn’t actually a more beautiful architecture though but admittedly better than having it around all the time…
Nobody said we don’t
2 Likes
Is this kind of issue well known or should I report?
Or maybe GNOME Calculator 48 has been widely updated?
Gnome calculator is at version 47 in the last supported Ubuntu release (oracular 24.10)… How did you get 48 ? Or are you running the pre-beta OS (don’t do that on production machines), there might indeed be bugs, dependency issues and whatnot at this state of development… Also note that breakages during development do explicitly not get cleaned up (i.e. if wrong dependencies are installed or a transition failed you will keep the mess on disk forever unless you manually clean up all wrong pieces)
In addition to what @ogra wrote, that version of Apparmor is only in plucky-proposed!
Moving this to pre-release. This entire setup is unsupported and bound to explode with -proposed enabled!
3 Likes
Well since months I run Plucky like this, watching each changelog to minimize the exploding risk.
Please remind that I do this (for years now) knowing the risks… and this makes the testing real.
So, is the issue mentioned above related to using bad bad things like Plucky with proposed?
I do not have any broken dependencies.
Yes. Those packages haven’t undergone the required autopkgtests or other regression testing. While we try to make sure the dependency issue you mention is correct, it’s not guaranteed.
It doesn’t matter how long you’ve been doing it, with or without success, it’s simply unsupported and we will not address any concerns you have here.
Don’t be rude, please.
I was just saying that I’m aware of what I’m doing.
Additionally, here are the packages I run, that do come from proposed:
I don’t see anything related to the screenshot I posted before. So if this is really caused by my setup and the use of proposed/Plucky, well done. I stop this here.
The intention was not to be rude. The intention was to explain to you that you’re on your own with your setup. I am a moderator on this discourse and I have to enforce what we do and do not support.
With that, this entire discussion is closed as you cannot seem to listen to staff feedback.