Version: 2.2.0 (using KDE 3.3.2, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-13) OS: Linux (i686) release 2.6.15-1-686 Since installing Debian 2.6.15-1.686 Kernel,kppp fails to connect with error message that it couldn't create a modem lock file(currently, but other messages have occurred). Also, pppd fails many times having to initiate kppp again before completing a connection. Wvdial always works and if I start wvdial first, then close the connection, and restart kppp, it will start, connect and most of the time get on line unless pppd fails. I have kernel images(Debian) 2.4.18-bf2.4, 2.6.8 installed on same machine and kppp works fine with them. This may not be a kppp bug and maybe it's a kernel, compiler or some other issue. Debian User and Debian-kde lists have failed to respond to my posts on this issue. I could use some guidance or work around to resolve this issue. Have been working with a Debian-kde for a couple of weeks off-list with no solution. Kppp error log and kppprc files shown below: lchata@ChatagnierL-Home:~/.kde/share/config$ cat kppprc|more [Account0] AccountingEnabled=0 AccountingFile= Authentication=0 AutoDNS=0 AutoName=0 BeforeConnect= BeforeDisconnect= CallbackPhone= CallbackType=0 Command= DNS=68.94.156.1,68.94.157.1 DefaultRoute=1 DisconnectCommand= Domain= ExDNSDisabled=0 Gateway=0.0.0.0 IPAddr=0.0.0.0 Name=SBCGlobal.net Password=******* Phonenumber=6814017:9816640:9816589:5274012:9841329 ScriptArguments= ScriptCommands= StorePassword=1 SubnetMask=0.0.0.0 Username=lenc5570@sbcglobal.net VolumeAccountingEnabled=0 pppdArguments= [General] AutomaticRedial=0 DefaultAccount=SBCGlobal.net DefaultModem=Diamond Supra Max DockIntoPanel=1 NumberOfAccounts=1 NumberOfModems=1 PPPDebug=0 RedialOnNoCarrier=1 ShowLogWindow=1 pppdTimeout=60 [Graph] Background=255,255,255 Enabled=true InBytes=0,0,255 OutBytes=255,0,0 Text=0,0,0 [Modem0] AnswerResponse=CONNECT AnswerString=ATA BusyResponse=BUSY BusyWait=3 ConnectResponse=CONNECT DLPResponse=DIGITAL LINE DETECTED Device=/dev/modem DialString=ATDT Enter=CR EscapeGuardTime=64 EscapeResponse=OK EscapeString=+++ FlowControl=Hardware [CRTSCTS] HangUpResponse=OK HangupString=+++ATH InitDelay=50 InitResponse=OK InitString=ATZ InitString1=ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Name=Diamond Supra Max NoCarrierResponse=NO CARRIER NoDialToneDetection=ATX3 NoDialToneResp=NO DIALTONE PreInitDelay=50 RingResponse=RING Speed=115200 Timeout=60 ToneDuration=58 UseLockFile=1 Volume=2 VolumeHigh=M1L3 VolumeMedium=M1L1 VolumeOff=M0L0 [WindowPosition] WindowPositionConWinX=659 WindowPositionConWinY=630 WindowPositionStatWinX=530 WindowPositionStatWinY=22 lchata@ChatagnierL-Home:~/.kde/share/config$ lchata@ChatagnierL-Home:~$ cat PPP-logfile Feb 9 20:19:44 ChatagnierL-Home pppd[18267]: pppd 2.4.3 started by lchata, uid 1000 Feb 9 20:19:44 ChatagnierL-Home pppd[18267]: using channel 2 Feb 9 20:19:44 ChatagnierL-Home pppd[18267]: Using interface ppp0 Feb 9 20:19:44 ChatagnierL-Home pppd[18267]: Connect: ppp0 <--> /dev/ttySHCF0 Feb 9 20:19:44 ChatagnierL-Home pppd[18267]: sent [LCP ConfReq id=0x1 <mru 576> <asyncmap 0xa0000> <magic 0xe79de451> <pcomp> <accomp>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: sent [LCP ConfReq id=0x1 <mru 576> <asyncmap 0xa0000> <magic 0xe79de451> <pcomp> <accomp>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00> <mru 1524> <asyncmap 0xa0000> <auth pap> <pcomp> <accomp> <mrru 1524> <endpoint [MAC:00:d0:52:01:32:f2]>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: sent [LCP ConfRej id=0x1 < 00 04 00 00> <mrru 1524>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: rcvd [LCP ConfAck id=0x1 <mru 576> <asyncmap 0xa0000> <magic 0xe79de451> <pcomp> <accomp>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: rcvd [LCP ConfReq id=0x2 <mru 1524> <asyncmap 0xa0000> <auth pap> <pcomp> <accomp> <endpoint [MAC:00:d0:52:01:32:f2]>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: sent [LCP ConfAck id=0x2 <mru 1524> <asyncmap 0xa0000> <auth pap> <pcomp> <accomp> <endpoint [MAC:00:d0:52:01:32:f2]>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: sent [LCP EchoReq id=0x0 magic=0xe79de451] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: sent [PAP AuthReq id=0x1 user="ChatagnierL-Home" password=<hidden>] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: rcvd [LCP EchoRep id=0x0 magic=0x0] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: rcvd [PAP AuthNak id=0x1 "invalid or no realm in username"] Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: Remote message: invalid or no realm in username Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: PAP authentication failed Feb 9 20:19:47 ChatagnierL-Home pppd[18267]: sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"] Feb 9 20:19:48 ChatagnierL-Home pppd[18267]: rcvd [LCP TermAck id=0x2] Feb 9 20:19:48 ChatagnierL-Home pppd[18267]: Connection terminated. Feb 9 20:19:48 ChatagnierL-Home pppd[18267]: using channel 3 Feb 9 20:19:48 ChatagnierL-Home pppd[18267]: Using interface ppp0 Feb 9 20:19:48 ChatagnierL-Home pppd[18267]: Connect: ppp0 <--> /dev/ttySHCF0 Feb 9 20:19:48 ChatagnierL-Home pppd[18267]: sent [LCP ConfReq id=0x3 <mru 576> <asyncmap 0xa0000> <magic 0x79fd18a5> <pcomp> <accomp>] Feb 9 20:20:03 ChatagnierL-Home pppd[18267]: sent [LCP ConfReq id=0x3 <mru 576> <asyncmap 0xa0000> <magic 0x79fd18a5> <pcomp> <accomp>] Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: LCP: timeout sending Config-Requests Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: Connection terminated. Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: using channel 4 Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: Using interface ppp0 Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: Connect: ppp0 <--> /dev/ttySHCF0 Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: sent [LCP ConfReq id=0x4 <mru 576> <asyncmap 0xa0000> <magic 0x1a641472> <pcomp> <accomp>] Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: sent [LCP TermReq id=0x5] Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: tcflush failed: Bad file descriptor Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: tcsetattr: Invalid argument (line 1010) Feb 9 20:20:18 ChatagnierL-Home pppd[18267]: Exit. lchata@ChatagnierL-Home:~$
/var/log/messages show the following: Feb 10 07:06:22 ChatagnierL-Home kernel: CSLIP: code copyright 1989 Regents of the University of California Feb 10 07:06:22 ChatagnierL-Home kernel: PPP generic driver version 2.4.2 Feb 10 07:06:22 ChatagnierL-Home pppd[6199]: pppd 2.4.3 started by lchata, uid 1000 Feb 10 07:06:24 ChatagnierL-Home chat[6209]: abort on (BUSY) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: abort on (NO CARRIER) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: abort on (VOICE) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: abort on (NO DIALTONE) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: abort on (NO DIAL TONE) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: abort on (NO ANSWER) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: abort on (DELAYED) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: send (ATZ^M) Feb 10 07:06:24 ChatagnierL-Home chat[6209]: expect (OK) Feb 10 07:06:53 ChatagnierL-Home pppd[6211]: pppd 2.4.3 started by lchata, uid 1000 Feb 10 07:06:53 ChatagnierL-Home pppd[6211]: Device ttySHCF0 is locked by pid 6199 Feb 10 07:07:09 ChatagnierL-Home chat[6209]: alarm Feb 10 07:07:09 ChatagnierL-Home chat[6209]: send (AT^M) Feb 10 07:07:09 ChatagnierL-Home chat[6209]: expect (OK) Feb 10 07:07:23 ChatagnierL-Home pppd[6211]: Device ttySHCF0 is locked by pid 6199 Feb 10 07:07:53 ChatagnierL-Home pppd[6211]: Device ttySHCF0 is locked by pid 6199 Feb 10 07:07:54 ChatagnierL-Home chat[6209]: alarm Feb 10 07:07:54 ChatagnierL-Home chat[6209]: Failed Feb 10 07:08:23 ChatagnierL-Home pppd[6211]: Device ttySHCF0 is locked by pid 6199 Feb 10 07:08:53 ChatagnierL-Home pppd[6211]: Device ttySHCF0 is locked by pid 6199 Feb 10 07:09:53 ChatagnierL-Home last message repeated 2 times Feb 10 07:10:53 ChatagnierL-Home last message repeated 2 times Feb 10 07:11:23 ChatagnierL-Home pppd[6211]: Device ttySHCF0 is locked by pid 6199 Feb 10 07:11:23 ChatagnierL-Home pppd[6211]: Exit. I suspect this lock is preventing kppp from starting when used first(before starting with wvdial) yielding the message "modem does not respond". So, I "kill 6199" and kppp connects without any problem and I get online. PID 6199 shows: ChatagnierL-Home:/usr/sbin# ps 6199 PID TTY STAT TIME COMMAND 6199 ? Ss+ 0:00 /usr/sbin/pppd call provider How can this be corrected?
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!