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 729828 - o.fdo.NM.Device.Ip4Config and Ip6Config don't get change notifications.
o.fdo.NM.Device.Ip4Config and Ip6Config don't get change notifications.
Status: RESOLVED DUPLICATE of bug 725657
Product: NetworkManager
Classification: Platform
Component: API
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-05-08 18:17 UTC by Marius Vollmer
Modified: 2014-05-14 08:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
D-Bus signals (14.33 KB, text/plain)
2014-05-08 18:17 UTC, Marius Vollmer 		Details

Description Marius Vollmer 2014-05-08 18:17:05 UTC 
Created attachment 276186 [details]
D-Bus signals

NetworkManager-0.9.9.0-38.git20131003.fc20.x86_64

I believe this is fixed, but I couldn't find a bug report for it, so I file this one to have something to point to.

There is no change notification when the Ip4Config or Ip6Config property of a o.fdo.NM.Device interface changes away from "/".

D-Bus signal log attached for "nmcli c down ffb8c395-...".  The connection is immediately reestablished by NM.  There is a change notification when IpXConfig goes to "/" but not when it is changed to point to a real object.
Comment 1 Thomas Haller 2014-05-13 14:41:21 UTC 
This sounds to me like a duplicate of bug 725657 (?)
Comment 2 Marius Vollmer 2014-05-14 08:59:51 UTC 
(In reply to comment #1)
> This sounds to me like a duplicate of bug 725657 (?)

Yes!

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