From 30be6814aecdd1379f8f05e2258ed50d68e6fefa Mon Sep 17 00:00:00 2001 From: David Malcolm Date: Thu, 3 Dec 2009 13:19:01 -0500 Subject: Change component even when no backtrace is attached --- abrt-triage.py | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/abrt-triage.py b/abrt-triage.py index 86e3876..ccd1ef3 100755 --- a/abrt-triage.py +++ b/abrt-triage.py @@ -155,12 +155,19 @@ class Change(object): def get_change(bz, bug_id): bug = Bug(bz, bug_id) script = bug.get_script() + # script = '/usr/bin/deluged' + if script: + pkg = what_provides_file(script) + else: + pkg = '(unknown)' + try: bt = bug.get_backtrace() (thread, frame) = bt.get_crash_site() (newsummary, bt_blurb) = characterize_bt(bt, thread, script) except NoBacktrace, e: return Change(newsummary='Crash running %s' % script, + newcomponent = pkg, comment=('''Thank you for the bug report. Unfortunately, without a stack trace from the crash it is impossible to determine what caused the crash. Please see http://fedoraproject.org/wiki/StackTraces for more information about getting a useful stack trace with debugging symbols. Even if you cannot reproduce this crash at will, you can prepare your system now to produce a good stack trace the next time you experience the crash. @@ -182,12 +189,6 @@ You may find assistance in the Fedora community support forums or mailing list, ) ) - # script = '/usr/bin/deluged' - if script: - pkg = what_provides_file(script) - else: - pkg = '(unknown)' - comment = '''Thank you for reporting this bug. How reproducable is this problem? If you run the program from a terminal, is an error message printed? -- cgit