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 768189 - [RFE] team: talk to teamd directly through D-Bus instead of using libteamdctl
[RFE] team: talk to teamd directly through D-Bus instead of using libteamdctl
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:
Blocks:
 
 
Reported: 2016-06-29 14:40 UTC by Beniamino Galvani
Modified: 2020-11-12 14:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Beniamino Galvani 2016-06-29 14:40:06 UTC 
At the moment the team support in NM requires libteamdctl, which is
used to interact with the teamd instance. Since we didn't want to have
the additional libteamdctl dependency in the main package, team support
was split into a plugin that can be packaged separately.

Also, all the functions provided by libteamdctl are synchronous and NM
may risk to block if the teamd instance stops responding.

teamd has a simple D-Bus interface [1]; NM could use it directly to
drop the dependency on libteamdctl and to have an asynchronous
mechanism to control teamd.

[1] https://github.com/jpirko/libteam/wiki/Infrastructure-Specification#teamd-control-api
Comment 1 André Klapper 2020-11-12 14:34:24 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).