I have just updated my TW system and re-booted (it had been hibernated until today rather than rebooted) and to my horror I found that Discover started on boot. Why? I only ran it the other day in order to install a program from flatpak, I dont want the thing running all the time, and there seems to be no way to turn it off at least from the GUI. Can someone please tell me how to stop it permanently and only run when I want it to?
Stuart
You probably have your desktop configured to start with the sessions that were active when you last exited. I think that’s the KDE default. And, by the way, you did not tell us which desktop you are using, so I am just guessing KDE.
So close that application and logout. Then login again. Or reconfigure so that login starts with a clean session or a manually saved session.
Sorry yes KDE. I do have to start with ‘Restore Previous Session’ so yes I could change that. However when I ran Discover there does not seem to be any way to shut it down, there is no menu or quit option I can find anywhere so it looks like they expect it to run all the time once started. I will change my start up option to see if it makes a difference but I dont really see why it should be that Discover does not have a quit option!
Stuart
Yes starting with a clean session does not allow Discover to start. However to be honest there is no way this should run in the background by default I believe it must have a quit option, afterall you only need it when installing software and most I believe use either command line or YAST to do this.
Stuart
To test, I started discover.
I then closed the discover window.
Next, I checked with
ps -ef | grep -i discover
That showed 4 processes. Those were the same 4 processes from before I closed the discover window. So it does indeed seem to want to run in the background.
I then proceeded to kill the process showing “/usr/bin/plasma-discover” as CMD. That left 3 process still running.
Checking back a few minutes later, showed no processes.
I have KDE configured to start from a saved session, so this isn’t going to affect me. And I almost never start “Discover” anyway.
Don’t count on YaST. YaST is a system management tool. Not a tool to manage user GUI applications.
This reddit thread may be of interest to you.
You can disable it via Configure System Tray > Miscellaneous > Software Updates > Disable
In addition, you could also explicitly mask packagekit service until needed
sudo systemctl mask packagekit
Unmask it when wanted again.
Software updates are disabled in system tray. All I want really is to be able to run Discover when I want and have a Quit button on the GUI which ends the task and all its associated tasks rather than having to run Ksysguard and kill it!
That Reddit thread is something different, I dont want it to run at all after I’ve finished with it.
Stuart
I don’t use it at all (and really don’t see the need for it anyway). Not an OpenSUSE issue. You’re best advised to liaise with the KDE devs.
I’ll create a bug report for KDE.
Stuart
Initially I asked about this on the KDE forums and had it confirmed that this does not happen on a Kbuntu installation, when the window close button is used the program exits and it cannot be found using Ksysguard. So it has been suggested this is an openSUSE issue in the way they have set it up. Should I create a bug for openSUSE initially?
Stuart
Yes, I guess so.