Don't print warnings when the provider is not running.

This can happen e.g., during boot, and contextkit recovers from it
when the provider starts.

1 files changed, 5 insertions, 1 deletions

diff --git a/libcontextsubscriber/src/provider.cpp b/libcontextsubscriber/src/provider.cpp
index b889045b..5c3d8f47 100644
--- a/libcontextsubscriber/src/provider.cpp
+++ b/libcontextsubscriber/src/provider.cpp
@@ -269,7 +269,11 @@ void Provider::onPluginSubscribeFinished(QString key)
 /// warning.
 void Provider::onPluginSubscribeFailed(QString key, QString error)
 {
-    contextWarning() << key << error;
+    // Don't print a warning here; under some circumstances it is normal that
+    // the provider is not running (e.g., during boot, subscribers might start
+    // before providers).  When the provider really starts, contextkit recovers
+    // from the situation gracefully.
+    contextDebug() << key << error;
 
     signalSubscribeFinished(key);
 }