Bug 310022

Summary:	10.3 Beta 3 1CD-KDE - installer asks for CD even though it is in drive
Product:	[openSUSE] openSUSE 10.3	Reporter:	Forgotten User xI2C5NvggO <forgotten_xI2C5NvggO>
Component:	Installation	Assignee:	Jan Kupec <jkupec>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	jsuchome
Version:	Beta 3
Target Milestone:	---
Hardware:	i586
OS:	openSUSE 10.3
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Yast logs showing CD not being found even though present

Description Forgotten User xI2C5NvggO 2007-09-12 20:46:02 UTC

Installing 1CD-KDE on a low-end machine (Pentium 1, 133 MHz, 80M RAM), all is well up to 'network setup' when YaST repeatedly asks for CD even though it is still in the drive. Selecting OK causes drive activity, an info window as it is evaluated then back to asking for the CD again. Select cancel causes installation to abort.

Switching to a console, hwinfo --cdrom shows CD-ROM present and apparently happy 

logs are painful to extract (will need to go via floppy) but I will provide if requested.

Also seen in earlier betas on this system.
-- 
Cheers
Richard (MQ)

Comment 1 Andreas Jaeger 2007-09-14 11:31:57 UTC

Please attach the YaST log files as described in http://en.opensuse.bugs/Bugs/YaST

Comment 2 Forgotten User xI2C5NvggO 2007-09-14 16:18:29 UTC

Created attachment 164121 [details]
Yast logs showing CD not being found even though present

Comment 3 Forgotten User xI2C5NvggO 2007-09-14 16:25:59 UTC

Please find attached.

I had a struggle to get remote logging to go - first the network card needed starting, then the nfs share wouldn't mount (needed to do as per the wiki, and use -o nolock in the mount command). But I got there - hope it's useful?

BTW the URL above should of course be http://en.opensuse.org/Bugs/YaST
R.

Comment 4 Jiří Suchomel 2007-09-18 14:00:55 UTC

Jano, please check.

Comment 5 Jan Kupec 2007-09-18 14:34:20 UTC

Thanx for reporting. Its because the dbus is wasn't running on your system.

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

Comment 6 Jan Kupec 2007-09-18 14:36:09 UTC

JFYI: the next release (RC1) should contain the fix. If the problem still occurs, please file a new bug report and attach the logs.

Comment 7 Forgotten User xI2C5NvggO 2007-09-18 16:40:31 UTC

OK thanks - will test on RC1 and report back.

Comment 8 Forgotten User xI2C5NvggO 2007-09-22 19:12:32 UTC

Works fine with RC1. Thanks!