Bug 85707

Summary: neat-control pops up a wrong error
Product: [Retired] Red Hat Linux Reporter: Jaap Bril <jaap.bril>
Component: redhat-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-02-05 14:15:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 81720    

Description Jaap Bril 2003-03-06 11:20:55 UTC
Description of problem:
neat-control used to activate ISDN-interface (ippp) gives error popup that
states that interface cannot be activated, AND PROCEDES to activate it anyway.


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


How reproducible:
100%


Steps to Reproduce:
1.configure ippp0
activate on startup is not checked
allow all users [..] is checked
auto obtain adress with dialup
No routes
provider (works)
All compression
No options
No callback
AUTO dialup
PAP + Sync ppp
default route is checked

2.
reboot (ippp is down)
3.
Use neat-control to startup ippp
    
Actual results:
Error popup that states neat-control could not activate the interface.
Interface gets activated anyway.
In effect all is OK
But users keep complaining!!

Expected results:
activate interface without comment ( or only to state it is an automatically
activated interface)


Additional info:

While typing this bug I used neat-control to check on the configuration;

It crashed with a dump.

Comment 1 Harald Hoyer 2003-03-10 14:21:03 UTC
ok, any tracebacks from the crash?

Comment 2 Harald Hoyer 2003-03-31 15:50:58 UTC
need more info