725045 – After first pass setup, back to console with an error message about rpm.lock

Bug 725045 - After first pass setup, back to console with an error message about rpm.lock

Summary: After first pass setup, back to console with an error message about rpm.lock

Status:	RESOLVED DUPLICATE of bug 723777

Alias:	None

Product:	openSUSE 12.1
Classification:	openSUSE
Component:	Installation (show other bugs)
Version:	Beta 1
Hardware:	Other Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2011-10-19 02:41 UTC by Forgotten User CxVz4LpaB5
Modified:	2011-10-19 07:45 UTC (History)
CC List:	0 users

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

Attachments
screenshot of the error message (158.13 KB, image/jpeg) 2011-10-19 02:41 UTC, Forgotten User CxVz4LpaB5	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Forgotten User CxVz4LpaB5 2011-10-19 02:41:36 UTC

Created attachment 457437 [details]
screenshot of the error message

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20100101 Firefox/8.0

I have installed os 12.1 beta in a xen server, fully virtualized.
I have choose the minimal software selection during the setup and after the end of the first part of the installation I am back on the console and got

error: can't create transaction lock on /var/lib/rpm/.rpm.lock (no such file or directory)

see screenshot


Reproducible: Always

Steps to Reproduce:
1. Use Opensuse 11.4 Xen
2. Install os 12.1 beta in full mode
3. choose minimal package selection during setup


Expected Results:  
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (no such file or directory)

Comment 1 Andreas Jaeger 2011-10-19 07:45:34 UTC

duplicate of bnc#723777

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