Bug 164542 - Bad: Entering a non-standard port number in Other ports causes the GUI to no longer work.
Bad: Entering a non-standard port number in Other ports causes the GUI to no ...
Status: CLOSED DUPLICATE of bug 157620
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-28 12:10 EDT by Uxorious
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-28 13:51:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Uxorious 2005-07-28 12:10:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Description of problem:
I entered 1666:tcp in the Other ports field.
(This is the Perforce port)
Hitting OK worked great, and the port was open.

However, starting the system-config-securitylevel GUI again causes a Python error.
The problem is cause by looking up the protocol, and since etc/services doesn't contain the port, Python bails out.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Start system-config-securitylevel
2. Add 1666:tcp
3. Start system-config-securitylevel again
  

Actual Results:  system-config-securitylevel won't start

Expected Results:  system-config-securitylevel should start

Additional info:
Comment 1 Chris Lumens 2005-07-28 13:51:57 EDT

*** This bug has been marked as a duplicate of 157620 ***

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