Description of problem: Unable to change hostname. system-config-network fails during the parsing of what seems to be a valid pap/chap-secrets files. Example pap-secrets and error log are attached below. Version-Release number of selected component (if applicable): 1.5.6 Steps to Reproduce: 1. copy attached pap-secrets to /etc/ppp 2. run system-config-network 3. select DNS tab, type in some new hostname, click on File->Save.
Created attachment 303078 [details] pap-secrets and error log
seems like you have gziped the attachment twice :-/ Component: system-config-network Version: 1.5.6 Summary: TB368e1d58 ConfPAP.py:105:getfields:BadFile: Error occured while parsing //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 209, in save papconf = getPAPConf() File "/usr/share/system-config-network/netconfpkg/NC_functions.py", line 300, in getPAPConf DVpapconf = ConfPAP.ConfPAP(getRoot() + PAPFILE) File "/usr/share/system-config-network/netconfpkg/conf/ConfPAP.py", line 35, in __init__ Conf.Conf.__init__(self, filename, '#', ' \t', ' \t') File "/usr/share/system-config-network/netconfpkg/conf/Conf.py", line 205, in __init__ self.read() File "/usr/share/system-config-network/netconfpkg/conf/ConfPAP.py", line 40, in read self.initvars() File "/usr/share/system-config-network/netconfpkg/conf/ConfPAP.py", line 86, in initvars 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 0x8d72518> self: <netconfpkg.conf.ConfPAP.ConfPAP instance at 0x8ca7d8c> m: None
Fixed in git repo. Should be in next update. Jirka
*** Bug 445627 has been marked as a duplicate of this bug. ***
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.