Blob Blame Raw
From 8617cb20b5165de32eb56ffb63edf3193842e506 Mon Sep 17 00:00:00 2001
From: Matej Habrnal <>
Date: Mon, 8 Jun 2015 10:23:20 +0200
Subject: [PATCH] a-a-p-ccpp-analysis: use ask_yes_no_save_result instead of

We change this function because we want users have an opportunity to choose
option never upload the coredump and always generate the backtrace locally.

We do not make the migration to this new feature because we believe the user will
be ok with one more click to configure this again.
We also thing that the re-configuraton will help will help familiarize users
with the new feature.

Related to rhbz#986876

Signed-off-by: Matej Habrnal <>
 src/plugins/ | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/plugins/ b/src/plugins/
index fbcd8a1..ae8ac46 100644
--- a/src/plugins/
+++ b/src/plugins/
@@ -12,6 +12,7 @@ from subprocess import Popen
 import report
 from reportclient import (ask_yes_no_yesforever,
+                          ask_yes_no_save_result,
@@ -58,7 +59,7 @@ def run_analyze_smart(problem_dir):
-    allowed = ask_yes_no_yesforever("abrt_analyze_smart_ask_upload_coredump",
+    allowed = ask_yes_no_save_result("abrt_analyze_upload_coredump",
                 _("Ok to upload core dump? (It may contain sensitive data). "\
                   "If your answer is 'No', a stack trace will be generated locally. "\
                   "(It may download a huge amount of data)."))