http://bugzilla.novell.com/show_bug.cgi?id=518125 Summary: Zypper hangs on install waiting for transaction lock Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 3 Platform: 32bit OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: badshah400@gmail.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.0) Gecko/20090617 SUSE/3.5.0-2.2 Firefox/3.5 While installing a large number of packages (I was trying to install the gnome patterns from the internet) zypper hangs (after some packages have been installed) attempting to install a package. This happens randomly and zypper actually shows that the package has been retrieved successfully at 0 B/s (which is strange, considering it shows the correct speed for all earlier packages), but the install hangs at 0%. Only a Ctrl-C Ctrl-C sequence works and the following message is then shown "Installation of gnome-panel-2.26.2-1.9 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: waiting for transaction lock on /var/lib/rpm/__db.000" Problem also occurs with YAST, in which case only killing y2base as root is the only way out. Once this error happens, it keeps re-occurring every time the software management is used subsequently. One has to restart for the problem to disappear. Reproducible: Sometimes Steps to Reproduce: 1.Select a large number of packages to install using zypper or YAST. 2.At some stage process hangs trying to install a package at 0% 3.Kill install procedure and try again. Error persists. 4.Restart, and attempt installation. Works until error occurs randomly again. Actual Results: Installation fails with message: "(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: waiting for transaction lock on /var/lib/rpm/__db.00" Expected Results: Installation successful. -- 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.