https://bugzilla.novell.com/show_bug.cgi?id=855993
https://bugzilla.novell.com/show_bug.cgi?id=855993#c5
--- Comment #5 from Wolfgang Bauer
The above also only works, when there are few enough updates available, so that you do not hit the 15 secs. time out counter. Today, I only had one update available, and thus was able to see the above pattern with the time out. When having more updates, you are normally not able to get to the item of interest, before the time out has been reached once again. I think it's again 15s after each time you show details for one package.
As I wanted to indicate in comment#1 though, you can change that default timeout to anything you like in /etc/PackageKit/PackageKit.conf (the setting is called "ShutdownTimeout"). But then packagekitd does block YaST/zypper for a longer time of course.
Why is it that the Applet cannot restart the packagekitd, when it notice that it is not around any more? Actually the applet DOES restart packagekitd. But the update references it holds seem to be invalid then for the newly started instance. I plan to investigate this issue closer, but didn't have time yet.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.