Bug 236483 – fallback to vnc on failure to start X -- but no network.

Bug 236483 - fallback to vnc on failure to start X -- but no network.

Summary:	fallback to vnc on failure to start X -- but no network.

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	anaconda (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Cantrell
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-04-14 20:01 EDT by David Woodhouse
Modified:	2007-11-30 17:12 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-04-20 16:12:10 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description David Woodhouse 2007-04-14 20:01:15 EDT

When X fails to start, I get offered VNC. But the network isn't brought up first.

Comment 1 David Cantrell 2007-04-20 16:12:10 EDT

We call getLinkStatus in _isys which returns 1 for having a link, 0 for not
having a link, and -1 for unknown state.  In isys.py, we return that value to
the caller.  In network.py in hasActiveNetDev(), we say:

if isys.getLinkStatus(dev):
    return True

Hahahaha....we're dumb sometimes.

Committed fix to rawhide.

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