Bug 106259 - "redhat-control-network" does not allow to deactivate modem connection
"redhat-control-network" does not allow to deactivate modem connection
Status: CLOSED DUPLICATE of bug 105785
Product: Fedora
Classification: Fedora
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
  Show dependency treegraph
Reported: 2003-10-04 05:53 EDT by Joachim Frieben
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:58:55 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 Joachim Frieben 2003-10-04 05:53:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20030926

Description of problem:
Establishing a valid Internet connection via modem by means of
"redhat-control-network" works nicely. However, the displayed status of the
corresponding connection remains "inactive", and thus it is not possible to
deactivate the connection via the "Deactivate" button in order to disconnect.
One has to kill the "pppd" daemon manually which is not very convenient.

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

How reproducible:

Steps to Reproduce:
1. Launch the Red Hat "Network Device control" from the "System Tools" menu.
2. Activate a previously entered modem based Internet connection.

Actual Results:  The modem gets online, but the corresponding entry in the
status display remains inactive.

Expected Results:  The status entry should turn active.

Additional info: None.
Comment 1 Harald Hoyer 2003-10-06 05:52:47 EDT

*** This bug has been marked as a duplicate of 105785 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:58:55 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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