Bug 195912 - network device control
Summary: network device control
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhn-applet
Version: 4.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Mike McCune
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-19 15:24 UTC by Mike
Modified: 2012-06-20 13:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:20:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike 2006-06-19 15:24:57 UTC
Description of problem: Cannot shut down network. Constantly restarts when I
shut it down.


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


How reproducible:
Very.

Steps to Reproduce:
1.open network device control
2.deactivate
3.within 5-10 sec. it restarts.
  
Actual results:


Expected results:
network should stay disabled until I restart.
I do this as a safety measure as I have dsl and want the added protection.
this used to work but no longer does.
Also, in the device control it says rhine II which I could not find your
component or version list.
I'm new to this Operating System so excuse my Ignorence. Thanks, Mike 


Additional info:

Comment 1 Robin Norwood 2006-10-17 16:56:43 UTC
mass reassign to mmccune

Comment 2 Red Hat Bugzilla 2007-04-12 00:46:57 UTC
User bnackash's account has been closed

Comment 4 Jiri Pallich 2012-06-20 13:20:35 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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