Bug 47377

Description of Problem:

Most of the time the connection will not complete on the first try.  
Also, at times, the KPPP window & the script debugging window will become 
permanent residents on the desktop while not displaying whether or not 
the connection was actually completed.  When this happens, one has to 
'su' & delete the PID file, then dial again, or log out, then back in, 
and redial.

How Reproducible:
Log in & dial using KPPP (w/script which says 'root.ok' fixed as 
indicated on RedHat's site.  This is not 100% reproducible, but between 
this & not completing connection to the point of timing out & having to 
redial, it is nearly 100% reproducible.

Steps to Reproduce:
1. Just dial the ISP
2. 
3. 

Actual Results:
Most of the time the connection will not complete on the first try.  
Also, at times, the KPPP window & the script debugging window will become 
permanent residents on the desktop while not displaying whether or not 
the connection was actually made.  When this happens, one has to 'su' & 
delete the PID file, then dial again, or log out, then back in, and 
redial.

Expected Results:
Expected... (1)/home/<user>/.kde/share/apps/kppp directory to be made on 
the USER's side with PID file therein... then a completed dial-in to the 
ISP the first time it is dialed --except, of course,  when there is a 
busy, or the line doesn't answer.

Additional Information:
 The multiple tries for a completed connection happen nearly every time 
the ISP is dialed.  When this happens, the terminal is waiting for the 
host PAP, and [presumeably] the IP address to be received.

The frozen KPPP & Script window happen frequently, though not on a 
regular schedule. However, as indicated, between this & the failed 1st 
dial-in attempt, the problem is very nearly 100% reproducible.

All updates, with the exception of the kernel, have hereby been applied, 
and this behaviour has not changed in the least.

Depending upon how much one must use the 'net, this could be considered a 
high-priority deal.  Half my work-load comes off the 'net, so this is a 
very major deal to me.

Machine in question:
Toshiba Satellite2100CDT
AMD K6-2 3D 400mhz processor
64MB RAM
4.03GB HD (RH Linux-dedicated)