After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 645690 - [PATCH] Update netmonitor code to talk to a recent NetworkManager
[PATCH] Update netmonitor code to talk to a recent NetworkManager
Status: RESOLVED DUPLICATE of bug 363662
Product: xchat-gnome
Classification: Other
Component: general
0.26.x
Other Linux
: Normal normal
: .30
Assigned To: xchat-gnome maintainers
xchat-gnome maintainers
Depends on:
Blocks:
 
 
Reported: 2011-03-25 23:11 UTC by Dan Williams
Modified: 2011-08-25 15:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Update net monitor code to recent NM API (4.70 KB, patch)
2011-03-25 23:11 UTC, Dan Williams
none Details | Review

Description Dan Williams 2011-03-25 23:11:57 UTC
Created attachment 184251 [details] [review]
Update net monitor code to recent NM API

It seems the existing net monitor code is really, really old and was written for NM 0.5 or earlier, which hasn't been current since 2006.  Fix up the code to work with NM 0.6 and later (including the new API in NM 0.9).

One question: it doesn't seem like the code grabs the initial network state at all.  Can we grab that and update the state in the plugin init code, or is that too early?  If it's too early could an idle handler be scheduled to grab state after a second or two?
Comment 1 Ritesh Khadgaray ( irc:ritz) 2011-08-10 15:49:26 UTC
right now, this is done by a plugin. the best bet would be to merge this into core, given that nm is basic requirement across almost all distro.
Comment 2 Ritesh Khadgaray ( irc:ritz) 2011-08-10 15:53:25 UTC

*** This bug has been marked as a duplicate of bug 363662 ***