Comment # 6 on bug 1202796 from Michael Andres

(In reply to Archer Allstars from comment #4)
> action (after logging in to my user ID). But the problem is, this process
> takes a very long time in some instances (sometimes, I experienced 10-30
> mins).

According to the pk_backend_zypp log the individual actions do not take that
long, but PK is permanently doing something. So it re-aquires the lock almost
immediately after it released it. Maybe something using PK is running wild:

> lock from 18:36:12 to 18:38:19 for 127 sec - lock free for   0 sec
> lock from 18:38:19 to 18:38:20 for   1 sec - lock free for   0 sec
> lock from 18:38:20 to 18:38:20 for   0 sec - lock free for   5 sec
> lock from 18:38:25 to 18:38:37 for  12 sec - lock free for   0 sec
> lock from 18:38:37 to 18:38:37 for   0 sec - lock free for   0 sec
> lock from 18:38:37 to 18:38:51 for  14 sec - lock free for   0 sec
> lock from 18:38:51 to 18:39:06 for  15 sec - lock free for   0 sec
> lock from 18:39:06 to 18:39:24 for  18 sec - lock free for   0 sec
> lock from 18:39:24 to 18:40:24 for  60 sec - lock free for   0 sec
> lock from 18:40:24 to 18:40:37 for  13 sec - lock free for   0 sec
> lock from 18:40:37 to 18:40:49 for  12 sec - lock free for   0 sec
> lock from 18:40:49 to 18:41:02 for  13 sec - lock free for   0 sec
> lock from 18:41:02 to 18:41:14 for  12 sec - lock free for   0 sec
> lock from 18:41:14 to 18:41:26 for  12 sec - lock free for   0 sec
> lock from 18:41:26 to 18:41:41 for  15 sec - lock free for   0 sec
> lock from 18:41:41 to 18:41:53 for  12 sec - lock free for   0 sec
> lock from 18:41:53 to 18:42:04 for  11 sec - lock free for   0 sec
> lock from 18:42:04 to 18:42:18 for  14 sec - lock free for   0 sec
> lock from 18:42:18 to 18:43:35 for  77 sec - lock free for   0 sec
> lock from 18:43:35 to 18:44:10 for  35 sec - lock free for   0 sec
> lock from 18:44:10 to 18:44:24 for  14 sec - lock free for   0 sec
> lock from 18:44:24 to 18:44:37 for  13 sec - lock free for   0 sec
> lock from 18:44:37 to 18:44:50 for  13 sec - lock free for   0 sec
> lock from 18:44:50 to 18:45:06 for  16 sec - lock free for   0 sec
> lock from 18:45:06 to 18:45:22 for  16 sec - lock free for   0 sec
> lock from 18:45:22 to 18:45:39 for  17 sec - lock free for   0 sec
> lock from 18:45:39 to 18:45:57 for  18 sec - lock free for   0 sec
> lock from 18:45:57 to 18:46:12 for  15 sec - lock free for   0 sec
> lock from 18:46:12 to 18:46:27 for  15 sec - lock free for   0 sec
> lock from 18:46:27 to 18:46:42 for  15 sec - lock free for   0 sec
> lock from 18:46:42 to 18:46:59 for  17 sec - lock free for   0 sec
> lock from 18:46:59 to 18:47:14 for  15 sec - lock free for   0 sec
> lock from 18:47:14 to 18:47:29 for  15 sec - lock free for   0 sec

We can try to enable zypper to reserve the next free slot. 

Nevertheless the behavior is weird the the first glimpse and constantly eats up
resources. I'll try to figure out mote...