| Summary: | Kppp fails to connect unless wvdial or pon is run first; then kppp will work until reboot. Also, pppd fails with exit status 0 after kppp connects. | ||
|---|---|---|---|
| Product: | [Unmaintained] kppp | Reporter: | Leonard Chatagnier <lenc5570> |
| Component: | general | Assignee: | Harri Porten <porten> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Leonard Chatagnier
2006-02-10 05:40:11 UTC
/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! |