Version: (using KDE KDE 3.2.3) Installed from: RedHat RPMs OS: Linux After upgrading to v3.2.3 under Fedora Core 2, when initiating a connection with kppp, everything seems to be working fine, the connection icon docs in the system tray, but I cannot connect to any server, either http or ftp; I cannot ping any hosts either. Here is a typical output I get, when running kppp via a command in a terminal: [user@localhost user]$ kppp Opener: received SetSecret Opener: received OpenLock Opener: received OpenDevice QMetaObject::findSignal:Accounting: Conflict with AccountingBase::changed(QString,QString) Opener: received ExecPPPDaemon In parent: pppd pid 3161 Opener: received OpenResolv Couldn"t find interface ppp0: No such device Kernel supports ppp alright. Opener: received RemoveSecret Opener: received RemoveSecret Opener: received KillPPPDaemon In killpppd(): Sending SIGTERM to 3161 Opener: received RemoveSecret Opener: received RemoveSecret Opener: received OpenResolv Opener: received OpenResolv Opener: received RemoveLock It was pppd that died pppd exited with return value 5 Sending 3157 a SIGUSR1 My hardware is the NetMod ISDN terminal, USB version; more information on this device can be found at http://netmod.intracom.gr/
Assigning to kppp but I doubt this has anything to do with KDE, seems to be a pppd/modem driver issue.
Have you tried pinging a host by its IP, eg. 80.232.38.13? What does /sbin/ifconfig show?
> Assigning to kppp but I doubt this has anything to do with KDE, seems to be a pppd/modem driver issue. I did not change anything, but KDE. I access NetMod using ACM (USB Abstract Control Model driver for USB modems and ISDN adapters), having created this device file as instructed in NetMod's Linux configuration guide: [root@localhost root]# mknod /dev/usb/ttyACM0 c 166 0 [root@localhost root]# mknod /dev/usb/ttyACM1 c 166 0 [root@localhost root]# ... Things worked smoothly up to KDE-3.2.2 (inclusive). ---------- > Have you tried pinging a host by its IP Yes, both hostnames and IP addresses tried -- no results. > What does /sbin/ifconfig show? [user@localhost user]$ less /sbin/ifconfig "/sbin/ifconfig" may be a binary file. See it anyway? [answered "no" here] [user@localhost user]$ ll /sbin/ifconfig -rwxr-xr-x 1 root root 55204 2004-06-03 13:03 /sbin/ifconfig*
> Things worked smoothly up to KDE-3.2.2 (inclusive). Additionally, after downgrading to KDE-3.2.2 (using what is on the Fedora Core 2 distribution ISO's), connections work fine again.
Re ifconfig: please *execute* /sbin/ifconfig while you are connected and send the output. The fact that switching the KDE RPMS reproduces the problem doesn't rule out a problem introduced by the distributor rather than KDE. Can you compile kppp from sources?
[user@localhost user]$ /sbin/ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2673 errors:0 dropped:0 overruns:0 frame:0 TX packets:2673 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1473458 (1.4 Mb) TX bytes:1473458 (1.4 Mb) ppp0 Link encap:Point-to-Point Protocol inet addr:213.16.146.28 P-t-P:194.219.252.157 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:8 errors:2 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:232 (232.0 b) TX bytes:362 (362.0 b) Compile kppp from sources? Well, first of all, kppp itself appears to be working alright; anyway -- as I understand it -- kppp, being part of kdenetwork, would require compiling this package from sources, which would in turn require to compile the whole bunch of KDE packages, a process through which I have neither the time, nor the disk space required to go, not to mention the lack of guarantee for success...
The PPP interface is there at least so kppp's job is done. What's remaining seems like a network setup issue like e.g. a firewall. Without you spending some time on compiling an older kppp version it will impossible to pin down potential reasons for a regression from here.
No network setup issues... It's just a standalone PC, using iptables, which worked fine with KDE-3.2.2; I also stopped the iptables daemon, but to no avail. How do I do the compilation? How do I handle package management issues, after installing without using RPM? (you may e-mail me directly)
You could download ftp://ftp.kde.org/pub/kde/stable/3.2.2/src/kdenetwork-3.2.2.tar.bz2 tar xvfj kdenetwork-3.2.2.tar.bz2 cd kdenetwork-3.2.2 ./configure make and you should end up with the old kppp version as kppp/kppp. No need to permanently install it. Just try if it works better than the new one from the RPM.
Do I have to download and compile? (Isn't enough just to use the binary from KDE 3.2.2 -- just extract it from the RPM, using MC?) What about any garbage left on my system? (How do I clean up afterwards?) Do I have to be root? (kppp is a symbolic link to consolehelper in RedHat 9.0/Fedora Core).
Sure. As it's easier you might do this as a first step (compiling will be needed only if we'll have to identify a single patch that is causing your problems). What garbage do you mean? All you need to extract is the (real) kppp binary and temporary replace it (make a backup copy of the old one). You'll have to follow the kppp symlink to find out what it is pointing to and where the real kppp binary is located and how it is named. RH's consolehelper has already been the cause of many problems. Don't remember how the setup concretely is.
I'm posting this from FC2, using (the original) kppp from kdenetwork that came with FC2 ISO's, extracted from the .RPM as described above. I wanted to wait until I install the new ppp FC2 upgrade (as it conflicted with initscripts, but no update to that was posted until today). kppp from KDE-3.2.3 still doesn't work, though, with the updated ppp (ppp-2.4.2-3.FC2.1.rpm). What's very odd is that somehow the executables' sizes change from their original on my system, for no apparent reason. When the packages are installed, their sizes are as follows: [root@localhost sbin]# ll kppp* -rwxr-xr-x 1 root root 547088 2004-04-14 18:26 kppp (3.2.2) -rwxr-xr-x 1 root root 547152 2004-06-03 22:40 kppp (3.2.3) After some usage, their sizes become as follows: [root@localhost sbin]# ll kppp* -rwxr-xr-x 1 root root 657416 2004-04-14 18:26 kppp (3.2.2) -rwxr-xr-x 1 root root 652972 2004-06-03 22:40 kppp (3.2.3) > What garbage do you mean? After compiling (if/when I do it). Does anything get written on my system, elsewhere than where the tarfile is extracted, and the compilation is performed? (both are presumably the same folder) > ... follow the kppp symlink ... I'm already employing the "quick and dirty solution" described at http://devel-home.kde.org/~kppp/faq.html
On 14 Jul 2004, Doryforos wrote: > I'm posting this from FC2, using (the original) kppp from kdenetwork > that came with FC2 ISO's, extracted from the .RPM as described above. OK. I looked through the list of changes between 3.2.2 and 3.2.3 but can't see any change obviously being responsible. > I wanted to wait until I install the new ppp FC2 upgrade (as it > conflicted with initscripts, but no update to that was posted until > today). > > kppp from KDE-3.2.3 still doesn't work, though, with the updated ppp > (ppp-2.4.2-3.FC2.1.rpm). > > What's very odd is that somehow the executables' sizes change from their > original on my system, for no apparent reason. That's really strange. Do you have a corrupted file system maybe? You could check this by running 'fsck' on your partition(s). > > What garbage do you mean? > > After compiling (if/when I do it). Does anything get written on my > system, elsewhere than where the tarfile is extracted, and the > compilation is performed? (both are presumably the same folder) You could do the compilation in a temporary directory like /tmp and delete everything afterwards. But now that you have a working kppp ... you might as well stay with it :) Harri.
Would the compilation help you to make kppp better? If so, what do I have to do (apart from compiling)
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!