Blame SOURCES/0001-network-Do-not-use-timestamp-to-identify-connections.patch

b97e22
From 95550e5a90d65b049dabcd31b7168612c9802327 Mon Sep 17 00:00:00 2001
b97e22
From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuellner@gnome.org>
b97e22
Date: Mon, 4 Nov 2013 20:09:45 +0100
b97e22
Subject: [PATCH] network: Do not use timestamp to identify connections
b97e22
b97e22
Connections have UUIDs to uniquely identify connections, bringing
b97e22
in timestamps just messes things up unnecessarily (and was dropped
b97e22
upstream in 3.10).
b97e22
Patch by Dan Williams.
b97e22
---
b97e22
 js/ui/status/network.js | 4 +---
b97e22
 1 file changed, 1 insertion(+), 3 deletions(-)
b97e22
b97e22
diff --git a/js/ui/status/network.js b/js/ui/status/network.js
b97e22
index bfd07fd..0a8871c 100644
b97e22
--- a/js/ui/status/network.js
b97e22
+++ b/js/ui/status/network.js
b97e22
@@ -231,9 +231,7 @@ const NMConnectionBased = new Lang.Class({
b97e22
         if (exists) {
b97e22
             let existing = this._connections[pos];
b97e22
 
b97e22
-            // Check if connection changed name or id
b97e22
-            similar = existing.name == connection.get_id() &&
b97e22
-                existing.timestamp == connection._timestamp;
b97e22
+            similar = existing.name == connection.get_id();
b97e22
         }
b97e22
 
b97e22
         if (exists && valid && similar) {
b97e22
-- 
b97e22
1.8.4.2
b97e22