Bug 1390347

Summary: drkonqi at once forbids and requests an error report.
Product: [Fedora] Fedora Reporter: Alan Schmidt <bucky>
Component: plasma-workspaceAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 25CC: jgrulich, kde-sig, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:44:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alan Schmidt 2016-10-31 18:42:09 UTC
plasma-workspace-drkonqi-5.8.1-1.fc25.x86_64

Sometimes, when an application "closes unexpectedly," drkonqi appears. The tooltip for drkonqi says to please report the error, but the error dialog expressly forbids it, with the language "you cannot report this error."

The language is confusing to me. I'm requesting at least a change of wording meaning is clearer. My best guesses are here, in no particular order.

1) The sofware is obsolete or abandoned, and there is no one who will entertain bug reports for it. This is more or less what the remainder of the message implies (e.g.: "akonadi_ical_resource does not provide a bug reporting address"). My gut tells me this message probably has some softer meaning (perhaps #2). If, truly, no-one will troubleshoot errors, let's get rid of the software entirely.

2) Drkonqi can't help. If that's the case, a one-word change would make that clear ("Drkonqi cannot report" instead of "You cannot report"). It would also help to clarify that "bug reporting address" is drkonqi's limitation, and I (the "you" of the message) shouldn't feel bound by it.

3) The error is well known, and it isn't useful for end users to report it anymore. Again, it would be best to state that directly rather than leave the user wondering ("We are aware of the error, and are working to resolve it." instead of "You cannot report this error."

Comment 1 Fedora End Of Life 2017-11-16 19:42:22 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:44:05 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.