Bug 430098 - traceback when transitioning to stage#2 - rhpxl - IndentationError: expected an indented block
Summary: traceback when transitioning to stage#2 - rhpxl - IndentationError: expected ...
Keywords:
Status: CLOSED DUPLICATE of bug 430074
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rhpxl
Version: 5.2
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Chris Lumens
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-24 15:04 UTC by James Laska
Modified: 2013-09-02 06:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-24 15:12:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description James Laska 2008-01-24 15:04:38 UTC
Description of problem:

Booting the installer fails when transitioning to stage#2

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

RHEL5.2-Server-20080124.nightly/i386
 * rhpxl-0.41.1-1.el5
 * anaconda-11.1.2.90-1

How reproducible:
%100 on HP system

Steps to Reproduce:
1. Boot installer using kickstart or manually step through loader
  
Actual results:

Traceback in anaconda:

File "/usr/lib/python2.4/site-packages/rhpxl/xhwstate.py", line 743
   print _("Found HP Virtual Mouse")
        ^^^^^
IndentationError: expected an indented block

The surrounding code indicates that the "print" stmt should be indented into the
if conditional block?

        ## Check for HP iLO 2 virtual mouse and if it exists configure evdev
        ilomousehw = ilomouse.ilomouseCheck()
        if ilomousehw.isDevicePresent():
        print _("Found HP Virtual Mouse")
            ilomouse_conf = xf86config.XF86ConfInput()
            xconfig.input.insert(ilomouse_conf)
            ilomouse_conf.identifier = "ilomouse"

Expected results:

 - No traceback

Additional info:

Comment 1 Chris Lumens 2008-01-24 15:12:49 UTC

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


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