Comment 10 for bug 1025184

Revision history for this message
Florian R, (xyz) wrote :

> What makes you think that?
Well, basically only the time, no technical idea. As it is taking soo much time and CPU is low, i would expect some timeout the script is waiting for, perhaps some missing folder issue or whatever... i am just guessing.

Is there a way how i can run this trigger in some kind of debug mode for having logging messages?

---------------------
> Give concrete examples of packages that approx. 6 minutes at this step.
"aptitude upgrade amarok" yesterday. Took more this time, approx. 10 minutes.

---------------------
> Do some packages pass this step much faster?
Just giving it a try, am upgrading...will give feedback soon