Bug 1436277 - KCrash rethrows all crashes, bringing up BOTH DrKonqi and ABRT
Summary: KCrash rethrows all crashes, bringing up BOTH DrKonqi and ABRT
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kf5-kcrash
Version: 25
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL: https://git.reviewboard.kde.org/r/128...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-27 14:35 UTC by Kevin Kofler
Modified: 2017-04-06 02:20 UTC (History)
5 users (show)

Fixed In Version: kf5-kcrash-5.32.0-2.fc25 kf5-kcrash-5.32.0-2.fc26 kf5-kcrash-5.32.0-2.fc24
Clone Of:
Environment:
Last Closed: 2017-03-31 02:22:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Kofler 2017-03-27 14:35:59 UTC
Since version 5.29.0, KCrash defaults to not only bringing up DrKonqi, but also rethrowing crashes for downstream crash handlers:
https://git.reviewboard.kde.org/r/128437/
This means that the user gets 2 bug reporting UIs (DrKonqi and ABRT), which is really confusing. It also means the bugs can end up in the wrong place (the user can report them either upstream or downstream or both) instead of going only directly upstream (through DrKonqi).

To fix this, kf5-kcrash must be built with:
-DKCRASH_CORE_PATTERN_RAISE_DEFAULT:BOOL="OFF"
Unfortunately, this is missing in the current Fedora kf5-kcrash.spec on all branches. It should be pushed as a bugfix update to all branches ASAP.

For Fedora 24 (originally shipped with kf5-kcrash-5.22) and Fedora 25 (originally shipped with kf5-kcrash-5.27), this is a regression introduced by the kf5-kcrash-5.29 update and ought to be fixed as soon as possible.

Comment 1 Kevin Kofler 2017-03-27 14:38:23 UTC
Sorry, that should be:
-DKCRASH_CORE_PATTERN_RAISE:BOOL="OFF"
(without the "_DEFAULT" part). See:
https://cgit.kde.org/kcrash.git/tree/CMakeLists.txt#n39

Comment 2 Fedora Update System 2017-03-27 19:22:14 UTC
kf5-kcrash-5.32.0-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-97fc50ec87

Comment 3 Fedora Update System 2017-03-28 01:50:13 UTC
kf5-kcrash-5.32.0-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b7fdb92d46

Comment 4 Fedora Update System 2017-03-28 08:52:12 UTC
kf5-kcrash-5.32.0-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-d363831a5c

Comment 5 Fedora Update System 2017-03-31 02:22:37 UTC
kf5-kcrash-5.32.0-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2017-04-01 17:32:26 UTC
kf5-kcrash-5.32.0-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2017-04-06 02:20:09 UTC
kf5-kcrash-5.32.0-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.