Description of Problem:
An attempt to use "Internet Configuration Wizzard" from a menu
in order to add a ppp connection ended up with the following
Traceback (innermost last):
File "/usr/sbin/internet-druid", line 1206, in ?
File "/usr/lib/python1.5/site-packages/gtk.py", line 2608, in mainloop
File "/usr/lib/python1.5/site-packages/libglade.py", line 28, in __call__
ret = apply(self.func, a)
line 126, in on_finish_page_finish
line 44, in save
line 56, in saveProfiles
line 273, in save
File "/usr/sbin/../share/redhat-config-network/netconfpkg/Conf.py", line
472, in __delitem__
Local variables in innermost frame:
self: <netconfpkg.Conf.ConfEHosts instance at 852fd98>
This is on a laptop which does have an ethernet card and is configured
to operate on an internal network but still needs an option of extra
The bomb happened when all basic data were already typed in and post-mortem
examination revealed that various files, obviously associated with
this configuration attempt, were already written in variouos subdirectories
of /etc/sysconfig/ but I have no way to asses how complete that was.
Enough to make "Dialup Configuration Tool", i.e. rp3-config, deeply
unhappy on a subsequent attempt to configure the same connection again
but not enough to make these leftovers available for edit in rp3-config
(which, BTW, looks like a serious rp3-config bug). It would be likely
better to have one tool which does the job then two where none seems
to be really up to the task and which conflict with each other.
It is also not really clear what to do to have a default route switched
to ppp connection when it is going up and restored to the previous
state afterwards; or, if you have a vague idea what routing is, that
such need may arise at all.
hmm, strange. Could you please attach your /etc/hosts???
> Could you please attach your /etc/hosts???
Mine are probably not that interesting and the laptop in question is
on another continent for quite a while and likely reconfigured already
few times. :-)
I will try to reproduce if an opportunity will arise.
Haven't seen this since then, so I'm pretty sure this has been fixed. Reopen if
still a problem in limbo or newer.
first beta of erratum is available at:
Most of the bugs reported have been removed, but as in every software change,
there could be new bugs introduced.
Please report bugs against this with explicitly stating the 1.0.1 version... Thx
and please test.