209817 – Failed to initialize the catalog

Bug 209817 - Failed to initialize the catalog

Summary: Failed to initialize the catalog

Status:	RESOLVED DUPLICATE of bug 207607

Alias:	None

Product:	openSUSE 10.2
Classification:	openSUSE
Component:	Installation (show other bugs)
Version:	Alpha 4 plus
Hardware:	Other Other

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

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2006-10-03 21:36 UTC by Geronimo Orozco
Modified:	2006-10-04 17:59 UTC (History)
CC List:	0 users

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

Attachments
Failed to initialize the catalog. Try Again screenshot (34.66 KB, image/png) 2006-10-03 21:36 UTC, Geronimo Orozco	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 Geronimo Orozco 2006-10-03 21:36:19 UTC

I got the 5 isos from kirk openSUSE-10.2-Alpha4plus-i386-CD1.iso toopenSUSE-10.2-Alpha4plus-i386-CD5.iso.

When I try to install the system at the very beggining of the installation it wont let me install it, because a faliure initializing catalogs. And I cant continue.
I have tried in a vm machine and in a real box. (both failed)
Also I run the test for the cds, and it says the cd is Ok.

This is a blocker bug because it wont let you install the system. 

Attached a screenshot of the step when get blocked.

Comment 1 Geronimo Orozco 2006-10-03 21:36:59 UTC

Created attachment 100205 [details]
Failed to initialize the catalog. Try Again screenshot

Comment 2 Christoph Thiel 2006-10-04 06:55:28 UTC

Looks like bug #207607 -- did you install from CD?

Comment 3 Geronimo Orozco 2006-10-04 16:28:38 UTC

Yeah, I tried to install it from CD looks very similar

Comment 4 Christoph Thiel 2006-10-04 17:59:38 UTC

Alright -- please try again with Alpha5, which is due tomorrow.

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