Can't save network config after yum update

arthurbuliva · 05-29-2008, 01:01 AM

Hi friends,

Fedora 8; I run a successful yum -y update command. So now I would like to change a few network configurations.

So I run /usr/bin/system-config-network and the dialog pops up.

I then do my changes here and
there but on clicking on "Save", I get a popup claiming that:

Code:

Component: system-config-network
Version: 1.5.5
Summary: TB368e1d58 ConfPAP.py:105:getfields:BadFile: Error occured while parsin
g //etc/ppp/pap-secrets

Traceback (most recent call last):
  File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 831
, in on_applyButton_clicked
    self.save()
  File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 393                                                     , in save
    self.saveDevices()
  File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 413                                                     , in saveDevices
    devicelist.save()
  File "/usr/share/system-config-network/netconfpkg/NCDeviceList.py", line 214,                                                      in save
    papconf.delallitem([key, server])
  File "/usr/share/system-config-network/netconfpkg/conf/ConfPAP.py", line 236,                                                      in delallitem
    var = self.getfields()
  File "/usr/share/system-config-network/netconfpkg/conf/ConfPAP.py", line 105,                                                      in getfields
    raise Conf.BadFile, "Error occured while parsing %s" % self.filename
BadFile: Error occured while parsing //etc/ppp/pap-secrets

Local variables in innermost frame:
var: []
regexp: <_sre.SRE_Pattern object at 0xa656c98>
self: <netconfpkg.conf.ConfPAP.ConfPAP instance at 0xa37b6cc>
m: None

Now I have no idea on what to do about that error. Any help will be appreciated.

lazlow · 05-29-2008, 09:39 AM

Have you rebooted since you did the updates? Some updates do not take effect until their particular service has been restarted (usually just easier to reboot). If the update "locked down" things until the update takes effect, you will not be able to make changes until after a restart.