http://bugzilla.novell.com/show_bug.cgi?id=544546 Summary: satsikver is incredibly slow Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: aaronw@doofus.org QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.2 Firefox/3.5.3 GTB5 AutoPager/0.5.2.2 (http://www.teesoft.info/) I recently upgraded from 11.0 to 11.1 and went to install the KDE 4.3 upgrade and so far YaST has been running at 100% CPU for over an hour. Here's a sample from y2log: 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 resolving update/feature rules 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 resolving job rules 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 installing old packages 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 resolving update/feature rules 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 resolving job rules 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 installing old packages 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 resolving update/feature rules 2009-10-05 22:38:28 <1> flash(28854) [satsolver] PoolImpl.cc(logSat):81 resolving job rules My machine is a 3.2GHz I7 with 6GB of RAM. Reproducible: Always Steps to Reproduce: 1. Go to http://en.opensuse.org/KDE4 2. Click on Install via 1-click KDE4 Desktop for version 11.1 3. Enter root password 4. Accept defaults and click next. 5. Wait... y2log updates from time to time, but is extremely slow. One core is pegged at 100% I don't know how long this will take as it's still going on. Actual Results: Stuck in CPU loop Expected Results: Install KDE 4.3 -- 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.