Bug 85707 - neat-control pops up a wrong error
neat-control pops up a wrong error
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
8.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks: 81720
  Show dependency treegraph
 
Reported: 2003-03-06 06:20 EST by Jaap Bril
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-05 09:15:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jaap Bril 2003-03-06 06:20:55 EST
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 09:21:03 EST
ok, any tracebacks from the crash?
Comment 2 Harald Hoyer 2003-03-31 10:50:58 EST
need more info

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