Red Hat Bugzilla – Bug 160465
system-config-securitylevel won't start
Last modified: 2007-11-30 17:11:07 EST
Description of problem: system-config-securitylevel won't start. After the password-prompt there is no further reaction when launched from KDE. When launched from a console, a Python traceback is printed with "socket.error: port/proto not found" as error description. This occures to me after an update from fc3. Version-Release number of selected component (if applicable): system-config-securitylevel-1.5.8-1 How reproducible: Launch it from a console. Steps to Reproduce: 1. start system-config-securitylevel Actual results: Traceback (most recent call last): File "/usr/share/system-config-securitylevel/system-config-securitylevel.py", line 18, in ? app.stand_alone() File "/usr/share/system-config-securitylevel/securitylevel.py", line 453, in stand_alone self.readFile() File "/usr/share/system-config-securitylevel/securitylevel.py", line 353, in readFile protoname = socket.getservbyport(int(service), protocol) socket.error: port/proto not found Expected results: It should simply start ;-) Additional info:
Same happens for me. This only occurs if you have assigned custom ports to be opened.
Fixed in Rawhide. I'll have a FC4 errata about this within a day or two. Marking as duplicate of another report on this. *** This bug has been marked as a duplicate of 159100 ***
(In reply to comment #1) There's a quick-and-dirty workaround for the problem: for every assigned custom port that you add to s-c-securitylevel, create a dummy for that port number in /etc/services. E.g. I added "1022:tcp" as a custom port, so I added this line to /etc/services: mytmp 1022 # KLUDGE REMOVE THIS WHEN system-config-securitylevel IS FIXED Now when I fire up s-c-securitylevel, the "Other ports" box shows "mytmp:tcp", rather than 1022:tcp This quickie stops the getservbyport() error which is the cause of the problem. > Same happens for me. This only occurs if you have assigned custom ports to be > opened.
Update pushed.