Bug 76934 - Network configuration crash (modem)
Network configuration crash (modem)
Status: CLOSED DUPLICATE of bug 77725
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
  Show dependency treegraph
Reported: 2002-10-29 14:09 EST by Mike Hughes
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-04 07:48:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Hughes 2002-10-29 14:09:24 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; CDonDemand; rv:0.9.4)
Gecko/20011019 Netscape6/6.2

Description of problem:
Network configuration crashes on "Apply" if a modem connection has been set up
with a password containing an internal space/blank.  It saves correctly on the
first "add" but will not edit, delete or add another connection after that. 
Problem is with /etc/ppp/pap-secrets file.  Deleting this file clears the
problem.  Dump indicates "end-quote not found"

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

How reproducible:

Steps to Reproduce:
1. Set up modem (ppp) connection with password containing space such as "pass
word".  Save and exit program.
2. Re-enter Network Configuration and edit the previously created connection.
Click "Apply" on outer dialog.

Actual Results:  Program crashes when "Apply" is clicked.  Changes are not
saved.  Files are corrupted so that connection is inoperable.

Additional info:

Dump indicates "close quote not found" in /etc/ppp/pap-secrets.  Deleting this
file clears the problem and allows the connection to be rebuilt.
Comment 1 Harald Hoyer 2002-11-13 09:24:46 EST

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

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