Bug 928838

Summary:	Installer screen goes black and doesn't come back
Product:	[Fedora] Fedora	Reporter:	Stef Walter <stefw>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	anaconda-maint-list, dcantrell, g.kaviyarasu, jonathan, mfabian, mkolman, petersen, robatino, sbueno, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-29 12:48:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	834084

Description Stef Walter 2013-03-28 14:46:17 UTC

Using http://dl.fedoraproject.org/pub/alt/stage/19-Alpha-TC2/Live/x86_64/Fedora-19-Alpha-TC2-x86_64-Live-Desktop.iso

Installing in a virt-manager KVM VM with 2048M RAM and 10G disk.

During the install packages stage, the screen goes black. I imagine this is a screen saver. This is strange thing to happen during an install, and unsettling for users.

But more seriously, wiggling the mouse or pressing keys on the keyboard do not result in the screensaver going away. I can use Ctrl-Alt-F2 to get to a VT.

The host machine is F18.

Comment 1 Jens Petersen 2013-03-29 09:20:26 UTC

Mike Fabian first told me about this and I now see it at the end of
a TC3 netinstall on my Thinkpad T500.

I guess anaconda is crashing before setting up the bootloader:
the system does not boot anyway on reboot.

Proposing as an Alpha blocker, though more details are needed.

Comment 2 Jens Petersen 2013-03-29 09:35:31 UTC

The machine doesn't lockup completely though after anaconda crashes
so it should be possible to go into a vconsole and extract more info
(unfortunately I didn't, naively expecting the system would boot).

Comment 3 Mike FABIAN 2013-03-29 12:17:10 UTC

I guess this is a duplicate of bug#928287

Comment 4 Jens Petersen 2013-03-29 12:48:17 UTC


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