Bug 81646 - ppp applet not updated on connect
Summary: ppp applet not updated on connect
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-15 19:22 UTC by David Fraser
Modified: 2019-04-11 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
fix for Linux (1.75 KB, patch)
2006-11-07 08:55 UTC, Ivan Todoroski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Fraser 2004-05-15 19:22:36 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    RedHat RPMs
OS:                Linux

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. 

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. 

Note: this was bug 57265 but the original reporter was unwilling to reopen it
Comment 1 Oliver Grimm 2005-04-12 23:46:35 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 lexual 2005-04-19 04:22:19 UTC
Definitely an issue for me on 3.4.0.
Everytime I reconnect I have to remove the ksysguard and then add it again for it to work.
Also, if I disconnect from the net while downloading stuff, the ksysguard display is frozen at the state at the time of disconnection.
So you can look at the applet and think that you are currently downloading stuff when you have been offline for hours.
Comment 3 Ivan Todoroski 2006-11-07 08:55:42 UTC
Created attachment 18454 [details]
fix for Linux

Yesterday, I got annoyed by this more than 4-year old bug for the last time!
So, I bit the bullet and fixed it. Patch is against KDE 3.5.5 - it's a fairly
simple fix, so should be easy for you to review quickly and finally put this
issue to rest.

Notes:

* I took the liberty of removing the print_error("RECONFIGURE") call from
Linux/netdev.c, and instead I have set the ReconfigureFlag so that Command.c
can detect this condition and call print_error() from the proper place in its
event loop.

* Problem is fixed for Linux only. From what I could see Solaris, Irix and
Tru64 might have this problem too, since they also don't register the
checkNetDev() callback in modules.h. As I don't have access to these platforms,
I could neither verify nor try fixing it for them.
Comment 4 Oliver Grimm 2008-12-07 14:48:58 UTC
I'm not using PPP anymore.
Does somebody know if Ivan's patch has been applied?
Comment 5 Richard Llom 2019-03-12 21:12:32 UTC
I'm not using PPP either.
Is this issue still present in current version of ksysguard?
Comment 6 Bug Janitor Service 2019-03-27 04:33:09 UTC
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!
Comment 7 Bug Janitor Service 2019-04-11 04:33:10 UTC
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!