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 754767 - error adding connection via nmcli/libnm
error adding connection via nmcli/libnm
Status: RESOLVED DUPLICATE of bug 754794
Product: NetworkManager
Classification: Platform
Component: API
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: nm-review
 
 
Reported: 2015-09-09 10:29 UTC by Jiri Klimes
Modified: 2015-09-18 13:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jiri Klimes 2015-09-09 10:29:14 UTC 
$ nmcli con add type ethernet con-name ethernet2 ifname em1 autoconnect no
(process:9772): libnm-CRITICAL **: nm_connection_get_id: assertion 's_con != NULL' failed
Connection '(null)' ((null)) successfully added.

(Substitute em1 with your actual interface name.)
Comment 1 Jiri Klimes 2015-09-09 10:30:21 UTC 
Posted a libnm fix in jk/libnm-con-add-fix.
Comment 2 Thomas Haller 2015-09-09 10:49:43 UTC 
(In reply to Jiri Klimes from comment #1)
> Posted a libnm fix in jk/libnm-con-add-fix.

LGTM (but not high confidence)
Comment 3 Thomas Haller 2015-09-10 09:38:29 UTC 
this is a duplicate of bug 754794
Comment 4 Lubomir Rintel 2015-09-14 12:36:29 UTC 
I don't think this is a correct fix; we shouldn't announce the async-initable object before we initialize it. I believe the bug #754794 fix addresses this correctly.
Comment 5 Jiri Klimes 2015-09-14 14:31:09 UTC 
Yeah, your fix seems fine. Go ahead and commit that.

*** This bug has been marked as a duplicate of bug 754794 ***
Comment 6 Lubomir Rintel 2015-09-18 13:56:43 UTC 
I committed this one, since it works around the issue, doesn't break anything else and will do until there's a proper fix.