Bug 664739 - packagekitd: endless loop
Summary: packagekitd: endless loop
Status: RESOLVED DUPLICATE of bug 679650
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: libzypp (show other bugs)
Version: Factory
Hardware: x86-64 Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-15 00:23 UTC by Christian Boltz
Modified: 2011-07-23 01:58 UTC (History)
2 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
pk_backend_zypp.bz2 (296.95 KB, application/x-bzip2)
2011-01-15 00:23 UTC, Christian Boltz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2011-01-15 00:23:36 UTC
Created attachment 408505 [details]
pk_backend_zypp.bz2

I just updated a package using kpackagekit, clicked around a bit in the kpackagekit settings and then noticed my laptop fan starting.

The problem is: packagekitd runs with 100% CPU usage since several minutes, and logs the same lines again and again. Looks like an endless loop...

I have no idea what caused this (I hope the attached log will help you), however packagekitd should not have any endless loops ;-)
Comment 1 kolA flash 2011-03-19 23:39:43 UTC
Maybe related?
https://bugzilla.novell.com/show_bug.cgi?id=679650
Comment 2 Duncan Mac-Vicar 2011-07-05 13:02:03 UTC
Do you still get this after the updates we released?
Comment 3 Christian Boltz 2011-07-06 18:32:02 UTC
Your question is not as easy to answer as it might sound ;-)

Easy answer: I can't reproduce this at the moment.

Correct, but difficult answer: The problem with this bug is that it happened only once or twice IIRC, and I did many successful package installations even before installing the update. This means that saying "I can't reproduce this at the moment" is not really helpful.

I'm afraid the only way to answer your question is to read the log and the code part running at the start of the endless loop (and to check if this code part was changed in the update). Unfortunately this is beyond my knownledge of packagekit, therefore I have to ask you to do this yourself ;-)
Comment 4 Duncan Mac-Vicar 2011-07-23 01:58:13 UTC
I think it is this bug. I reproduced it on my machine.

*** This bug has been marked as a duplicate of bug 679650 ***