[M120 Migration]Fix for crash during chrome exit

As g_bluez_dbus_manager is nullptr in BluezDBusManager::Shutdown()
a crash is observed during chrome exit. By enabling
BluezDBusManager::Initialize(), g_bluez_dbus_manager value is set
to a valid value.

Reference: https://review.tizen.org/gerrit/303262

Change-Id: Ia496ca7a06fcf33b7a34a4660f7c8303e4a15e5b
Signed-off-by: Rohit Kumar <rohit.16@partner.samsung.com>

diff --git a/chrome/browser/chrome_browser_main_linux.cc b/chrome/browser/chrome_browser_main_linux.cc
index 0d3bc8c..2e65a9f 100644 (file)
--- a/chrome/browser/chrome_browser_main_linux.cc
+++ b/chrome/browser/chrome_browser_main_linux.cc
@@ -66,9 +66,9 @@ void ChromeBrowserMainPartsLinux::PostCreateMainMessageLoop() {
   // initialization depend on FeatureList, and is done elsewhere.
 #endif  // BUILDFLAG(IS_CHROMEOS)
 
-#if !BUILDFLAG(IS_CHROMEOS)
   bluez::BluezDBusManager::Initialize(nullptr /* system_bus */);
 
+#if !BUILDFLAG(IS_CHROMEOS) && !BUILDFLAG(IS_TIZEN)
   // Set up crypt config. This needs to be done before anything starts the
   // network service, as the raw encryption key needs to be shared with the
   // network service for encrypted cookie storage.