(*** This bug was imported into bugs.kde.org ***) Package: kppp Version: 2.0.3 (using KDE 2.1.1 ) Severity: normal Installed from: Mandrake RPMs Compiler: gcc 2.96 OS: Linux OS/Compiler notes: Mandrake 8.0 looking at source from current stable release of KDE If there is a script for a dial-up connection it will execute regardless of whether or not script-based login is selected. In particular if I select a terminal-based login and have instructions for a script the script will execute and the terminal will not appear. The problem is in connect.cpp in the method ConnectWidget::timerEvent In the section of the method starting with // wait for newline after CONNECT response (so we get the speed) vmain=2; executes regardless of the authorization method designated by the user which forces script execution. I don't have the option to test other authentication methods but I found that the following code allows proper selection of terminal login. // repeating from roughly line 390 emit startAccounting(); p_kppp->con_win->startClock(); // new branch if(gpppdata.authMethod() == AUTH_TERMINAL) { vmain = 10; } else { vmain = 2; scriptTimeout=gpppdata.modemTimeout()*1000; } return; I assume that AUTH_PAP AUTH_CHAP and AUTH_MSCHAP will also need to be dealt with in order to avoid automatic script execution but as I mentioned I don't have the ability to test these. (Submitted via bugs.kde.org)
When my ISP changed their login-procedure from script to PAP overnight I was bitten by the same bug. I changed my sciptbased login to PAP and was surprised to see it didn't work. Using the commandline utilities in /etc/ppp (ppp-on and ppp-off) -did- work, but using kppp didn't. Not having seen the bugs on kppp but using the source on kppp it turned out that the presence of a login-script precedes the PAP (or other) method. Fow now I've removed the login-script in KPPP and for now it works. So it's more of nuisance in stead of a real problem. However for less advanced users with a dialup connection it will be more of a struggle. Are you interested in a patch or is this problem already fixed in KDE 3.1.x > ? At the moment I'm using Mandrake 8.2 and KDE 2.2.2.
Is this bug still present in a recent version of KDE, such as 3.5.8?
As proposed on http://techbase.kde.org/Contribute/Bugsquad/Bugs_to_be_done this bug is marked as closed (no response within 30 days). If the problem still exists please re-open.