Am Mittwoch, 16. Februar 2011, 14:11:53 schrieb Martin Schlander:
Sometimes packagekitd releases package management on its own after a minute or two - without needing to use the hammer. But not always.
Sometimes packagekitd can be told to quit via zypper, but most times it can't.
For me this always works, yet not as expected. But maybe it can shed a light on what does not work. If zypper asks whether it should tell packagkitd to quit and one chooses "yes" one almost always gets the message that it failed. No matter how often one enters yes again to try again, it will always fail. However, if one aborts zypper with CTRL+C after the first attempt which according to zypper fails and immediately after that restarts zypper up or whatever packagekitd is not reported by zypper to still block anything. So the "fail" is not really a fail. Maybe zypper itself somehow prevents packagekitd from quitting until zypper itself was quit. Another question for me is whether after zypper or YaST quit packagekitd the notifiers like kpackagekit still work, i.e. do their checks. I have a feeling that this is not the case. Sven -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org