From 766b6b3e52478abd22a54fdcfe569e8dcca534e7 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel <dirk@hohndel.org>
Date: Fri, 29 Nov 2013 11:39:36 -0800
Subject: [PATCH] Don't call deleteLater on ui elements

I'll admit that I don't fully understand this part of Qt.
But commenting out the deleteLater (like we already do for another one)
fixes the crash - and shouldn't do more than add a potential small memory
leak.

Fixes #309

Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
---
 qt-ui/subsurfacewebservices.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qt-ui/subsurfacewebservices.cpp b/qt-ui/subsurfacewebservices.cpp
index 6d44d8c5b..7362255c3 100644
--- a/qt-ui/subsurfacewebservices.cpp
+++ b/qt-ui/subsurfacewebservices.cpp
@@ -91,7 +91,7 @@ void SubsurfaceWebServices::buttonClicked(QAbstractButton* button)
 			// we may want to clean up after ourselves, but this
 			// makes Subsurface throw a SIGSEGV...
 			// manager->deleteLater();
-			reply->deleteLater();
+			// reply->deleteLater();
 			ui.progressBar->setMaximum(1);
 			break;
 		case QDialogButtonBox::HelpRole: