Bug 465816 - Traceback starting VNC in kickstart install
Summary: Traceback starting VNC in kickstart install
Keywords:
Status: CLOSED DUPLICATE of bug 465638
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-06 15:23 UTC by Orion Poplawski
Modified: 2008-10-06 15:39 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-10-06 15:39:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2008-10-06 15:23:17 UTC
Description of problem:

PXE/kickstart install.

After "Starting VNC"

Traceback (most recent call last):
  File "/usr/bin/anaconda", line 850, in <module>
    runVNC()
  File "/usr/bin/anaconda", line 427, in runVNC
    vncS.startServer()
  File "/usr/lib/anaconda/vnc.py", line 221, in startServer
    self.initialize()
  File "/usr/lib/anaconda/vnc.py", line 101, in initialize
    netinfo = network.Network()
  File "/sur/lib/anaconda/network.py", line 301, in __init__
    available_devices = self.available()
  File "/usr/lib/anaconda/network.py", line 359, in available
    elif ksdevice.find(':') != -1:
AttributeError: 'NoneType' object has no attribute 'find'

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

Comment 1 Chris Lumens 2008-10-06 15:39:19 UTC

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


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