Bug 161737 - isdn status is wrong
isdn status is wrong
Product: Fedora
Classification: Fedora
Component: system-config-network (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
Blocks: 87718
  Show dependency treegraph
Reported: 2005-06-26 15:44 EDT by Georg E Schneider
Modified: 2008-02-17 00:57 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-17 00:57:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Plaintext patch (870 bytes, patch)
2005-06-26 15:44 EDT, Georg E Schneider
no flags Details | Diff

  None (edit)
Description Georg E Schneider 2005-06-26 15:44:27 EDT
Description of problem: ISDN status is not shown correctly

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

How reproducible:
Start the isdn connection and the status is not changed (as root and user)
I've seen an old patch for redhat-config-network but it worked only for root

Steps to Reproduce:
1. start system-config-network
2. connect to your isdn line

Actual results:
the connection works but the status don't change 

Expected results:
status should change for all

Additional info:
I've written as a little idea a patch:
see attachment
Comment 1 Georg E Schneider 2005-06-26 15:44:27 EDT
Created attachment 115990 [details]
Plaintext patch
Comment 2 Christian Iseli 2007-01-19 19:21:03 EST
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Comment 3 petrosyan 2008-02-17 00:57:39 EST
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.

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