Bug 127383 - TB /usr/lib/python2.2/site-packages/rhpl/exception.py:280:handleException:TypeError: generic_error_dialog() got an unexpected keyword argument 'dialog_type'
Summary: TB /usr/lib/python2.2/site-packages/rhpl/exception.py:280:handleException:Typ...
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: redhat-config-network   
(Show other bugs)
Version: 2.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-07 14:37 UTC by Manish
Modified: 2012-06-20 16:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 16:12:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Manish 2004-07-07 14:37:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4)
Gecko/20030624 Netscape/7.1

Description of problem:
File "/usr/sbin/redhat-config-network-gui", line 169, in ?
    handleException(sys.exc_info(), PROGNAME, PRG_VERSION)
  File "/usr/lib/python2.2/site-packages/rhpl/exception.py", line 280,
in handleException
    dialog_type = "info")
TypeError: generic_error_dialog() got an unexpected keyword argument
'dialog_type'


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

How reproducible:
Didn't try


Additional info:

Comment 1 Harald Hoyer 2004-07-07 15:10:05 UTC
please update rhpl

Comment 2 Jiri Pallich 2012-06-20 16:12:52 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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