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.
ok, any tracebacks from the crash?
need more info