summaryrefslogtreecommitdiff
path: root/libnm/nm-object.c
diff options
context:
space:
mode:
authorLubomir Rintel <lkundrak@v3.sk>2017-01-18 11:28:35 +0100
committerLubomir Rintel <lkundrak@v3.sk>2017-01-19 16:15:42 +0100
commit0822cbb032ea224bbc125861578f0eaec08dd711 (patch)
treedf22dbfe9b5bef099f34399f04c466f0018e27b8 /libnm/nm-object.c
parent1afbf948a0825300ce395adc5706e1ffdca94d24 (diff)
downloadNetworkManager-0822cbb032ea224bbc125861578f0eaec08dd711.tar.gz
libnm/object: lower the severity of the dangling object warning
The user can't do much about it and we can recover. This is a temporary measure to avoid unnecessarily bothering the user. (cherry picked from commit 7fec0755c9072dc37140a7b63b491ed02a3539cd)
Diffstat (limited to 'libnm/nm-object.c')
-rw-r--r--libnm/nm-object.c13
1 files changed, 12 insertions, 1 deletions
diff --git a/libnm/nm-object.c b/libnm/nm-object.c
index a5eccbdc34..6a47c65941 100644
--- a/libnm/nm-object.c
+++ b/libnm/nm-object.c
@@ -596,7 +596,18 @@ handle_object_property (NMObject *self, const char *property_name, GVariant *val
if (!object) {
/* This is a server bug -- a dangling object path for an object
* that does not exist. */
- g_warning ("No object known for %s", path);
+ /* XXX: We've ignored this before and the server hits the condition
+ * more often that it should. Given we're able to recover from
+ * ther error, let's lower the severity of the log message to
+ * avoid unnecessarily bothering the user. This can be removed
+ * once the issue is fixed on the server. */
+#if NM_MORE_ASSERTS
+#define __nm_log_debug g_warning
+#else
+#define __nm_log_debug g_debug
+#endif
+ __nm_log_debug ("No object known for %s", path);
+#undef __nm_log_debug
return FALSE;
}