Bug 166917

Summary:	Installing... but not copy starting... and screen view debug message
Product:	[Fedora] Fedora	Reporter:	jeong an ryeol <redhat>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED CANTFIX	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	sundaram
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-09-14 08:35:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jeong an ryeol 2005-08-27 17:50:53 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)

Description of problem:
Fedora4... Installing... but not copy starting... and screen view debug message
and my computer is rebooting...

my computer used via c3 cpu. (800MHz VIA C3 CPU)

computer information is ( http://www.danawa.co.kr/comindex_right.php3?product_view=SALE&kindc=COM&typec=BARE&codec=BBASUST1C3&partview=onlydescript ) -> this is korea computer information site.

please my computer fedora linux software install.....


< quod vide >
redhat 7.x linux ( wowlinux 7.x - www.wowlinux.com ) only install success.
but old version -_-aa ( i don't no about linux )


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. install try, but no file copying...
2. pc is auto reboot.
3.
  

Additional info:

Comment 1 Rahul Sundaram 2005-08-27 19:51:12 UTC


The description suggests that the installation itself doesnt start on the
system. Reassigning to component Anaconda, the Fedora installer

Comment 2 Chris Lumens 2005-08-29 17:36:34 UTC

Please post the traceback you are receiving.

Comment 3 Mike A. Harris 2005-09-14 08:35:29 UTC

Closing bug as the initial bug report doesn't contain any useful information
about the actual problem to be able to diagnose anything, and there have
not been any further responses from the original reporter.

Setting status to "CANTFIX" (without 2-way communication, and enough
details to diagnose the issue)