http://bugzilla.novell.com/show_bug.cgi?id=498511 User suse-beta@cboltz.de added comment http://bugzilla.novell.com/show_bug.cgi?id=498511#c2 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|suse-beta@cboltz.de | --- Comment #2 from Christian Boltz <suse-beta@cboltz.de> 2009-08-10 11:37:35 CEST --- Unfortunately I didn't try debug mode and can't reproduce it now :-( I also hope SUSE won't release another broken patch just to enable debugging this issue ;-) (If you find a copy of the broken kdegraphics3 patch somewhere, you might be able to reproduce the problem.) All I can tell you is - IIRC there was nothing added to the y2log while YOU took all the CPU (comment #0 contains the link to the y2logs, maybe you find something useful nevertheless) - the 100% CPU usage _started_ when the conflicts dialog popped up - the 100% CPU usage _ended_ when closing the conflicts dialog - the bug must be somewhere in the "idle" code - I had the dialog open for some time and the CPU usage was 100% all the time Maybe you can locate the problem in the conflict dialog code. Conditions are (not sure if I know all of them) - a conflict must exist - the conflict should be solvable by a vendor change (a "simple" conflict with the same vendor doesn't cause the 100% CPU usage) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.