At the end, I pressed Enter and was taken back to Discover, looking like nothing has been done yet. I closed out the Discover window. I still have a small notification window down by the clock that won’t go away, but I am not too worried about that, as I need to reboot now anyway.
EDIT:
I just checked and it did create a logfile in my home directory.
I see results same as reported here. This should keep users from messing up their system.
I still say for best maintenance of ones system use a terminal (like Konsole). All package management gui’s are limited, and they all lead to a tendency for users to ignore warning or error dialogs leading to borked systems.
One should be able to learn this in about 10 minutes. Even if you don’t learn all of it just knowing the resource is there should be helpful, refer to if you need to.
I still would not recommend this method for any user. Were it up to me, Discover would not be installed on ROME nor in the repos. It is probably fine on Rock, but I have no experience with that.
Nope, you shouldn’t use it for Rock, either. The changes in Cooker that enable it to use the sync method of updating look promising.
One thing we cannot ignore is the evolution of the userbase wanting something that looks like an app store to manage their apps and system. KDE has stated themselves that the intent of Discover is not as a means to do system updates and it only appears to kind of work in KDE Neon. Even then, they rely on Canonical to backstop that process for them.
Discover’s primary function is to install user level applications, not system level applications. It’s meant to “compete” with likewise technologies such as Play, App Store, and the Microsoft Store. All of those are user level package managers.
