Bug 51380 - ksconfig crashes when invoked
Summary: ksconfig crashes when invoked
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ksconfig
Version: 7.1
Hardware: noarch
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-09 21:57 UTC by ctolley
Modified: 2008-05-01 15:38 UTC (History)
0 users

Clone Of:
Last Closed: 2001-08-09 21:57:32 UTC

Attachments (Terms of Use)

Description ctolley 2001-08-09 21:57:28 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2smp i686)

Description of problem:
Whether starting via the X menu item (Program -> System -> Kickstart
Configurator) or via command-line:


ksconfig returns the following error:

Traceback (innermost last):
  File "/usr/share/ksconfig/ksconfig.py", line 387, in ?
NameError: select

I'm not a Python programmer, but I gambled and commented out line 387 and
the application started, and appears to create valid kickstart config
files, but I don't know the overall impact of leaving that line commented

How reproducible:

Steps to Reproduce:
1. Install Kickstart 1.2-1 and ksconfig 1.2-1 via rpm
2. From X, choose Kickstart Configurator from (Programs -> System ->
Kickstart Configurator), or invoke from a terminal program (Eterm or xterm,
3. Invoking from a terminal client lets you immediately see the error msg,
or you can CTRL-ALT-F1 over to the 1st TTY to see the error there.

Actual Results:  Traceback (innermost last):
  File "/usr/share/ksconfig/ksconfig.py", line 387, in ?
NameError: select

Expected Results:  Either provide an updated package, patch or snippit of
code that will correct this error.

Additional info:

Comment 1 Brent Fox 2001-08-10 20:04:29 UTC
This is a dupe of bug #37753.  You have found a correct workaround.  I could
provide you a fix, but it would just consist of the same change that you made. 
You sound like a Python programmer to me.  ;)

Anyway, ksconfig has gone through a major rewrite in regards to interface and
things like that.  The next release will not have this problem.

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