Bugzilla – Bug 721671
Installation error.
Last modified: 2011-10-25 10:35:55 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 When the installation almost done，it stopped and gave an error messages.Here is the last four line message. Initializing virtual console... Found a Linux console terminal on /dev/console(100 columns x37 lines) ...starting YaST2... error:can't create transaction lock on /var/lib/rpm/.rpm.lock(No such file or directory) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Appears to be the same as reported bugs 721680, 721676, 721670, 721815. I mounted my 12.1 beta1 / and see that there is in fact a /var/lib/rpm/.rpm.lock of zero bytes.
Comment #0: Please, could you attach full logfiles? Comment #1: So were you able to install? Did you tested with newer images as well?
Oh, I just met that /var/lib/rpm/.rpm.lock error as well. Michael, could you take a look?
This is very likely just another dupe of bug 723777, check whether the X server has crashed.
(In reply to comment #2) > Comment #0: Please, could you attach full logfiles? > > Comment #1: So were you able to install? Did you tested with newer images as > well? Sorry！ I cannot attach any logfiles，I cannot login into the desktop and already format the system，the iso MD5 was tested correct.
*** Bug 724639 has been marked as a duplicate of this bug. ***
*** Bug 721670 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Oh, I just met that /var/lib/rpm/.rpm.lock error as well. Michael, could you > take a look? We usually don't allow rpm to write something to the console. OTOH there have been a few buggy rpm versions, where rpm did not create the db directory (/var/lib/rpm/) on the fly upon rpm_init. So there've actually been a few libzypp versions writing this as error message to the screen. (bnc#697115) Libzypp works around this rpm bug since libzypp-9.5.0 (May 2011). AFAIK Beta1 contains libzypp-9.11.0, so this message should no longer occur, unless YaST calls zypp:target:init("/") within the instsys, where /var/lib/rpm/ exist, but is AFAIK readonly. I think YaST does this to utilize some of the libzypp methods and simply ignores the failed database init. Which might be ok as we don't want to install any packages to the instsys. Later, for the actual installation, YaST calls zypp:target:init("/mnt"), which initializes /mnt/var/lib/rpm/, and this is the call that must succeed in order to actually install some package. - IMO the 'create transaction lock on /var/lib/rpm/.rpm.lock' is due to YaSTs zypp:target:init("/") call, and if so, not causing any harm. If the above message was serious, we would not be able to install a single package to the system. So most probably not related to this bug. But it may also be YAST is calling rpm directly, and those calls are responsible for the message. Anyway I somewhat doubt, that the message is related to the aborted installation. Comment #1 et al. indicate these bugs may actually be caused by some XOrg problem. That's IMO more likely.
yes, probably dup *** This bug has been marked as a duplicate of bug 723777 ***