From 19d11751da73fded31605bb80f70642faf4095c5 Mon Sep 17 00:00:00 2001
From: Perttu Pohjonen <perttu.pohjonen@nokia.com>
Date: Mon, 7 Mar 2011 08:49:00 +0200
Subject: Unsuccessful unlocking of QNetworkConfigurationPrivate mutex

Above mentioned mutex is locked twice: first in caller function and second time in called function. Called function unlocks mutex and emits signal clearly unaware that the mutex is actually still locked. I changed the mutex to be unlocked before the function is called.

Task-number: QTBUG-15108
Reviewed-by: Ville Pernu
(cherry picked from commit c15560fbe2a1762117395c5ecaaecfa5ab8dce6f)
---
 src/plugins/bearer/symbian/symbianengine.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/plugins/bearer/symbian/symbianengine.cpp b/src/plugins/bearer/symbian/symbianengine.cpp
index bcf7dd9..edf4b89 100644
--- a/src/plugins/bearer/symbian/symbianengine.cpp
+++ b/src/plugins/bearer/symbian/symbianengine.cpp
@@ -829,6 +829,7 @@ void SymbianEngine::updateStatesToSnaps()
                 discovered = true;
             }
         }
+        snapConfigLocker.unlock();
         if (active) {
             changeConfigurationStateTo(ptr, QNetworkConfiguration::Active);
         } else if (discovered) {
-- 
cgit v0.12