I give up on Discover - it seems to be getting worse and worse…
When you open it, it asks for a login.
Give the login, and it merrily goes away to find updates, click Update All, and it seems to be happy for a while, but then comes back and tells you it has failed/has found a bug, but, ONLY THEN does it asks you to login again, and the process then repeats, ad nauseum…
I used to just do zypper dup, and all was good, but SOME software was not being updated, so thought I would try Discover…
Going back to zypper…
For Tumbleweed, the appropriate rolling upgrade method is to use ‘zypper dup’.
1 Like
BTW, if you believe Discover is not working as well as you think it should, then you should consider submitting a bug report
https://bugs.kde.org/enter_bug.cgi?format=guided&product=Discover
1 Like
Thanks, yep, may do that…
Uninstall it and just use terminal with zypper dup. I did it and I live happily.
Yes, have used zypper dup until a short while ago, but this does not update flatpaks (and snaps??), so thought I would give Discover a go…
Looks like zypper is the way to go, maybe occasionally running Discover, just to update the “rest”…?
I think something is wrong with your system. Discover doesn’t ask for your password when you open it, if that happens there’s something broken in your system, maybe you changed some permissions, but that’s just a guess.
Discover works well on my PC, I also do offline updates and it has always worked flawlessly.
The only problem with Discover is that it is not able to install software from a local rpm, for this you need to use Yast, the reason I believe is in the openSUSE policy, when you install software e.g. chrome from a local rpm, the system warns you that the rpm is not verified, as it was not created for openSUSE specifically, using Yast click on ignore and the installation is successful, Discover does not have this possibility so from mistake.
Discover also doesn’t ask for a password to update the system, at least that’s the default setting.
@hornetster flatpaks should be installed as your user… flatpak update as your user should suffice, if asking for a password, maybe you installed flatpaks as system?
1 Like
Discover/PackageKit work fine to update a Tumbleweed system, always have.
The thing Discover/PackageKit can’t do, is resolve problems for you, if you’ve got Packman enabled, for instance, or home: repos, or anything else, and there is a package conflict, or other error, it’s just going to not update.
You have to use zypper dup to resolve those.
1 Like
Thus why not use it in the first place?
Because relying on users to remember to update is a fools errand, and having Discover/Packagekit there to do most of the heavy lifting and remind you to update is generally a good thing?
1 Like
Well, once a week I have a maintenance window for all the systems I manage (and my users know this, thus they will log out and leave it to me). I may getting a bit older, but until now I did not forget it when it is is tuesday morning. 
I just press F6 first-boot of the day to zypper dup 
On Tumbleweed with GNOME, I have this shortcut bound to F6:
kgx --command="sudo sh -c 'zypper clean --all && zypper refresh --force --services && zypper dist-upgrade --details --allow-downgrade --allow-name-change --allow-arch-change --allow-vendor-change && sync && flatpak update && sync && fstrim --all --verbose && sync && read -n '1' -s -r -p 'Done''"
Not if the term used by those GUI tools is “update”, as the typical usage of posters here suggests. Updates in TW are uncommon. Upgrades to the rolling release distribution are frequent. Thus users should be checking their factory mailing list or announcements mailing list email frequently if not daily for availability of another release, and what changes accompany. Religiously using appropriate language may turn some of those “fools” into more astute rolling release users.
you can update your flatpaks with flatpak update… but going back to your problems with Discover, I think as one user wrote it happens because you installed your flatpaks as system, while I always install them as user, following the openUSE flatpak wiki.
This way you won’t have password prompts to update or install flatpak.
https://en.opensuse.org/Flatpak
3 Likes
The average user doesn’t know, or care what the difference between update and upgrade is, and to spend a bunch of time bikeshedding over semantics doesn’t help anybody.
1 Like
My thought is to induce as many average TW users as possible into the group of astute non-average users who understand they’re using a rolling distro and what it means to be doing so. We who know should stick to technically correct language, both in forums and in documentation.
2 Likes
Thanks all.
Will stick to zypper dup, and occasionally run Discover for the flatpaks - thanks.
I suspect TW is defaulting to system though, because I totally get what OP complains about. Discover does a poor job at that, to be fair (but they’re working on improving flatpak support, which I hope include system-wide flatpak installs).
The point is also, why doesn’t TW default to user-level flatpak installs? Would make much more sense IMO.
I don’t remember exactly where they’re installed on my system, but for sure I’m prompted for the sudo password every time I try to update my flatpaks or edit any files they created (e.g. .desktop entries). Which always seemed weird to me.
Yep, I would have used defaults, so it must be defaulting to system…