Version: 1.2.0 (using KDE 3.1.0) Installed from: Mandrake Linux Cooker i586 - Cooker Compiler: gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) OS: Linux (i686) release 2.4.21-0.13mdk When I start kde being connected to the internet, my ppp0 status applet displays properly the input and output packets chart. If I disconnect, the "disconnected" symbol appears in the applet. But then, If I reconnect, the symbol does not disappear as it should, and the applet does not display the input and output packets chart any more.
ksysguard has a ppp applet!?
Subject: Re: ppp applet not updated on connect Hi, Sorry for my bug report, it seems that It was not clear enough. What I call "ppp applet" is in fact what I get doing this : - creating a new display on the ksysguard applet - dragging and droping on it some ppp0 information from ksysguard like the input and ouput packets numbers Denis Prost Le Jeudi 17 Avril 2003 11:07, vous avez
This bug report is a duplicate for one I reported before (bug report 49953)
FYI, I also had this problem. I was able to circumvent it by adding a sensor for a network connection that *is* always on (eth0). So now my applet has a sensor for ppp0 and eth0. After doing this, the ksysguard applet seems to properly "catch" all network enablement/disablement events including ppp0. More detail in this posting: http://groups.google.com/groups?q=renrutv+lightning+bolt&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=pan.2003.04.21.05.51.50.449621%40yahoo.com&rnum=1
*** Bug 49953 has been marked as a duplicate of this bug. ***
I've got this bug too and it nerves me!
Everything works fine now with kde 3.2.2
Nope, it doesn't work for me. It does work if I do what was suggested in comment 4 (add a network interface that is always on). But if I don't do that, if I turn off the connection, then turn it on again, the applet stays in an error status Using kde-3.2.2-4 from Fedora Core 2
Please reopen the bug, because it doesn't work here on Debian 3.2.2-1, too.
I don't think it's a good idea that I reopen the bug (if it's possible, I don't know), since it works for me and I won't be able to know when it is fixed for you. It seems simpler to me that one of you reopen a new bug.
OK, bug 81646 opened to take this place. But I think this bug reporting system is totally broken, given a) only the original reporter can reopen the bug b) the bug reporting wizard tells you not to rereport bugs Anyway we can carry on there for those who still have this problem...
It is still broken, so reopen this but please. Bugzilla here is totally broken, people should be able to reopen bugs, rather than filling new bugs for the same problem. Fixing one half of a bug that solves for one group the problem but not for the other with the same sympthoms, the bug isn't solved yet. I tested just now, and it's so easy to reproduce: Create a monitor applet and connect it (I use a Signal Plotter) via ssh to a ppp0 device transmitter/receiver on a remote host. When the device gets down, the monitor is broken and will no longer be updated until he is restarted. There is not even a function to manually restart the update nor a easy way to restart the applet itself. Killing the ssh connection has the same effect. Because the function gets totally broken with no workaround, i see this as a major bug which should be fixed.