zypp-checkpatches continues to run because it is not safe to kill it as it refreshes update sources. If you leave it alone it will finish at some point.

What is missing to detect is that if you start opensuse-updater again it should detect if it running at it id not start the process itself but it was startef by an old applet.

I could also disable exiting until the process is done, but that would not be very safe or not?

Also we could wait to quit until the process is done. That can be slow. But is perhaps the solution I like more.

Actually I'd like to see a solution when everything quits ASAP, that would be for the user the most comfortable approach.

The issue seems to be in zypp-checkpatches not beeing able to quit at all, if I understand it correctly it always has to finish. How about having zypp-checkpatches handle signals and try to quit even before complete finish? I doubt it can't be made interruptible, at least to some extent.

Having at least some interruptibility of zypp-checkpatches, we could visualize the remaining time by having some passive popup stating "opensuseupdater quit, but still waiting until zypp-checkpatches finishes and cleans up".

BTW I hope zypp-checkpatches handles cases when a user kills it as it may and will likely happen. I've done it at least once ;-)

Yes, but those operations are handled in libzypp so the whole library would need to be made interruptible.

Jano, is there any chance to solve this bug by using bi-directional communication between zypper and opensuseupdater? For example a stop command that the updater could send to tell zypper to exit. 

Yes, as mentioned in bug 339045, but i don't know the time frame yet.

BTW in 10.3 it feels much better, if I quit the applet the (disk/cpu) activity
seems to stop.

Later: I will fix that in opensuseupdater as soon as zypper can be told to stop.

Due to bug 364875 this feature cannot be implemented.