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 688817 - Properties get notified after a PropertiesChanged signal, even if they didn't change
Properties get notified after a PropertiesChanged signal, even if they didn't...
Status: RESOLVED OBSOLETE
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: 2012-11-21 16:04 UTC by Aleksander Morgado
Modified: 2020-11-12 14:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aleksander Morgado 2012-11-21 16:04:06 UTC 
The scenario is the following (from bug 681146): The network indicator in gnome-shell connects a callback to the 'notify::current-capabilities' signal of a NMDevice. This callback should only be called if the CurrentCapabilities property for the Modem device is ever updated in NM.

What seems to be happening currently is that the callback gets called whenever a PropertiesChanged signal is emitted for the DBus object, regardless of whether the specific property was updated or not. 

The 'current-capabilities' property in NMDeviceModem should only be notified whenever PropertiesChanged contains that specific property, not always.
Comment 1 Dan Winship 2012-11-26 19:44:25 UTC 
i don't see anything obvious that would cause this...
Comment 2 André Klapper 2020-11-12 14:28:41 UTC 
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).