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 753324 - NameOwnerChanged signal matches should be specific
NameOwnerChanged signal matches should be specific
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on: 622927
Blocks:
 
 
Reported: 2015-08-06 15:11 UTC by Daniel Mack
Modified: 2020-11-12 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Mack 2015-08-06 15:11:47 UTC 
The NetworkManager daemon currently installs matches for NameOwnerChanged signals without being specific about what to track. Such signals are sent every time a client connects to the bus, so the daemon is woken up on each occasion. That doesn't scale and should be fixed, so only peers the daemon is really interested in are tracked.

I guess the rework to GDBus needs to be finished before this can happen though.
Comment 1 André Klapper 2020-11-12 14:33:07 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).