http://bugzilla.suse.com/show_bug.cgi?id=899755 http://bugzilla.suse.com/show_bug.cgi?id=899755#c17 --- Comment #17 from Jonathan Kang <sckang@suse.com> --- (In reply to Michael Andres from comment #16)

According to comment#1 PK is currently configured to terminate after 15 seconds idleness.

Reason for this was, that the PK-backend was not able to drop the libzypp-lock while it's idle. This way a running PK prevented zypper/yast from running, even if PK was idle. This has been fixed with libzypp-16.1.1, PK is now able to drop and re-acquire the libzypp-lock.

So as long as PK drops the libzypp-lock, it won't block zypper running?

It may however be the system has been modified while PK was idle. So after re-acquiring the libzypp-lock PK-backend must sync it's data with the systems current state, but this does not always work (see comment#6).

In comment#7 I sketched a demo which - in a loop - acquires the libzypp-lock and syncs it's data. This is basically what the PK-backend needs to do, if you want to stop terminating after 15 seconds.

I guess the only improvement needed at PK side is syncing the data with zypp properly, if I didn't mistake your explanation. -- You are receiving this mail because: You are on the CC list for the bug.