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 729833 - [PATCH] core: fix deactivation of assumed connections on device removal
[PATCH] core: fix deactivation of assumed connections on device removal
Status: RESOLVED DUPLICATE of bug 387832
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-05-08 19:35 UTC by Dan Williams
Modified: 2014-06-05 15:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
0001-core-fix-deactivation-of-assumed-connections-on-devi.patch (9.28 KB, patch)
2014-05-08 20:07 UTC, Dan Williams
none Details | Review

Description Dan Williams 2014-05-08 19:35:08 UTC
The following procedure leaves an NMActiveConnection around for a deactivated device, which causes errors in libnm-glib clients when they cannot create teh GObject for the non-existent device of the AC.

1) allow a device which can assume connections to be activated
2) stop NM, which should leave the device's IP configuration up
3) start NM and allow it to assume the device's existing connection
4) remove the device, either by unplugging it or 'rmmod'

The device is removed by nm-manager.c::remove_device(), but the device object is not moved to UNMANAGED state, leaving the NMActiveConnection completely unaware the device has gone away.
Comment 1 Dan Williams 2014-05-08 20:07:36 UTC
Created attachment 276198 [details] [review]
0001-core-fix-deactivation-of-assumed-connections-on-devi.patch
Comment 2 Dan Williams 2014-05-28 20:24:55 UTC
This patch has been superceded by the same (but modified) commit  in dcbw/dispatcher-blocking.

*** This bug has been marked as a duplicate of bug 387832 ***
Comment 3 Dan Winship 2014-06-05 15:40:54 UTC
*** Bug 731277 has been marked as a duplicate of this bug. ***