checkpoint: don't bypass settings-connection commit code on rollback

commit involves more then just replacing the setting and writing them
out. What? Dunno. It's complex.

But let's not bypass the commit-changes function. That one is supposed
to get it right.
This commit is contained in:
Thomas Haller 2017-11-30 17:07:06 +01:00
parent f73e78770e
commit d26c749ea6

View file

@ -254,10 +254,8 @@ activate:
if (need_update) {
_LOGD ("rollback: updating connection %s",
nm_settings_connection_get_uuid (connection));
nm_connection_replace_settings_from_connection (NM_CONNECTION (connection),
dev_checkpoint->settings_connection);
nm_settings_connection_commit_changes (connection,
NULL,
dev_checkpoint->settings_connection,
NM_SETTINGS_CONNECTION_COMMIT_REASON_NONE,
NULL);
}