| Summary: | kppp disconnects (I don't have a clue why) | ||
|---|---|---|---|
| Product: | [Unmaintained] kppp | Reporter: | Joerg Teichmann <joerg_teichmann> |
| Component: | general | Assignee: | Harri Porten <porten> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.1.2 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Joerg Teichmann
2004-09-21 18:40:53 UTC
On 21 Sep 2004, Joerg Teichmann wrote:
> I don't know what exactly happens, but it happens several times.
> I also do not know how to reproduce the problem and whether it is related to one system or version.
> I would expect to stay connected (what a surprise)!
Does the disconnent happen immediately after dial-in or after longer
periods of time?
Harri.
hey, youre really fast! It happens after longer periods of time. (no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 434)]
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x41086b89 in wait4 () from /lib/libc.so.6
#0 0x41086b89 in wait4 () from /lib/libc.so.6
#1 0x410fa000 in sys_sigabbrev () from /lib/libc.so.6
#2 0x40eb2061 in waitpid () from /lib/libpthread.so.0
#3 0x406d3344 in KCrash::defaultCrashHandler(int) ()
from /usr/lib/libkdecore.so.4
#4 0x410139d8 in sigaction () from /lib/libc.so.6
#5 0x402d0b99 in KServiceTypeProfile::offers(QString const&, QString
const&)
() from /usr/lib/libkio.so.4
#6 0x402b941a in KTrader::query(QString const&, QString const&, QString
const&, QString const&) const () from /usr/lib/libkio.so.4
#7 0x402b9373 in KTrader::query(QString const&, QString const&, QString
const&) const () from /usr/lib/libkio.so.4
#8 0x400803a6 in
ToggleViewGUIClient::ToggleViewGUIClient(KonqMainWindow*) ()
from /usr/lib/konqueror.so
#9 0x400613d0 in KonqMainWindow::KonqMainWindow(KURL const&, bool, char
const*) () from /usr/lib/konqueror.so
#10 0x4005ee88 in main () from /usr/lib/konqueror.so
#11 0x41002a51 in __libc_start_main () from /lib/libc.so.6
Is this really a backtrace from a kppp problem? The backtrace shows Konqueror crashing. I think it happened in Windowmaker, but it also often happens under KDE, especially under heavy load (during apt-get ---): Mar 11 18:16:03 spezi pppd[1977]: pppd 2.4.1 started by knoppix, uid 1000 Mar 11 18:16:03 spezi pppd[1977]: using channel 5 Mar 11 18:16:03 spezi pppd[1977]: Using interface ppp0 Mar 11 18:16:03 spezi pppd[1977]: Connect: ppp0 <--> /dev/ttyS1 Mar 11 18:16:03 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:05 spezi pppd[1977]: rcvd [LCP ConfReq id=0xcd <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:05 spezi pppd[1977]: sent [LCP ConfAck id=0xcd <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:06 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:07 spezi pppd[1977]: rcvd [LCP ConfReq id=0xce <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:07 spezi pppd[1977]: sent [LCP ConfAck id=0xce <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:09 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:09 spezi pppd[1977]: rcvd [LCP ConfReq id=0xcf <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:09 spezi pppd[1977]: sent [LCP ConfAck id=0xcf <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:11 spezi pppd[1977]: rcvd [LCP ConfReq id=0xd0 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:11 spezi pppd[1977]: sent [LCP ConfAck id=0xd0 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:12 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:13 spezi pppd[1977]: rcvd [LCP ConfReq id=0xd1 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:13 spezi pppd[1977]: sent [LCP ConfAck id=0xd1 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:15 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:15 spezi pppd[1977]: rcvd [LCP ConfReq id=0xd2 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:15 spezi pppd[1977]: sent [LCP ConfAck id=0xd2 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:17 spezi pppd[1977]: rcvd [LCP ConfReq id=0xd3 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:17 spezi pppd[1977]: sent [LCP ConfAck id=0xd3 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:18 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:19 spezi pppd[1977]: rcvd [LCP ConfReq id=0xd4 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:19 spezi pppd[1977]: sent [LCP ConfAck id=0xd4 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:21 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:21 spezi pppd[1977]: rcvd [LCP ConfReq id=0xd5 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:21 spezi pppd[1977]: sent [LCP ConfAck id=0xd5 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:23 spezi pppd[1977]: rcvd [LCP ConfReq id=0xd6 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:23 spezi pppd[1977]: sent [LCP ConfAck id=0xd6 <asyncmap 0xa0000> <auth chap MD5> <magic 0x6b3febd5> <pcomp> <accomp>] Mar 11 18:16:24 spezi pppd[1977]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc848b9cd> <pcomp> <accomp>] Mar 11 18:16:33 spezi pppd[1977]: Terminating on signal 15. Mar 11 18:16:33 spezi pppd[1977]: sent [LCP TermReq id=0x2 "User request"] Mar 11 18:16:36 spezi pppd[1977]: sent [LCP TermReq id=0x3 "User request"] Mar 11 18:16:39 spezi pppd[1977]: Connection terminated. Mar 11 18:16:39 spezi pppd[1977]: Exit. I suggest posting the log on comp.protocols.ppp and asking whether anyone can analyze it. If you find out please post the result here. Harri. Harri: pppd disconnected because it was killed by a SIGTERM. 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! |