https://bugs.kde.org/show_bug.cgi?id=404465
Bug ID: 404465
Summary: Bug report status does not remain exclusively under
the control of the report author! Problematic
behaviour of code author is not checked.
Product: bugs.kde.org
Version: unspecified
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: product/component changes
Assignee: sysad...@kde.org
Reporter: arcli...@gmail.com
CC: christo...@krop.fr
Target Milestone: ---
SUMMARY
Please clarify why as I have reported an observed bug with real negative impact
upon my system function and my personal business schedule that can be closed by
the author of the errant code without any agreement or negotiation? Where I
receive criticism from a 3rd party for reopening the bug report because it has
been prematurely closed! Where it becomes increasingly clear the author is both
unable to recognize the nature of the problem and appears unwilling to learn
from myself the observer? This situation is exacerbated by the (wrongful?)
intervention that has failed to observe the sequence of "premature" closure x2
before any due negotiation has been engaged with by the code author with myself
the report author?
STEPS TO REPRODUCE
1. Install K3b CD/DVD/Blu-Ray copier, writer suite on fresh install of Linux
Mint Cinnamon 64bit (19v1 Tessa)
2. Answer system default behaviour prompt when inserting a blank DVD with "Run
K3b"
3. Start K3b; open a fresh project to copy a DVD to x3 blank DVDs and observe
the results! Open a bug report and observe as the code author repeatedly closes
the bug report without committing to negotiate for change because the concept
of established principle and private property is unknown to the code author!
OBSERVED RESULT
at every fresh DVD insertion for the next copy operation a fresh copy of K3b is
started that proceeds to obscure the prior copy operation of K3b. Reporting
this as a bug because K3b fails to check for a prior instance of its code and
fails to offer the system owner an opportunity to confirm the validity of the
new instance with a Y/N? This causes disruption for new users and potential
delays in processing for others whose system is already committed to other
operations as a direct consequence of resource consumption by K3b. The author
does neither comprehend how their code should respect the system it is being
run in nor how the status of a bug report should only be altered by the
originator of the bug report. THE BUG REPORTING SYSTEM DOES NOT PROTECT THE
EXCLUSIVE RIGHT OF THE BUG REPORT AUTHOR TO CHANGE THE STATE OF THE BUG REPORT.
EXPECTED RESULT
K3b fails to respect it is running in an environment that is not its property
and fails to offer the "system owner" an opportunity to validate each n+1
instance of its code in principle. Reporting this bug reveals an author who
cannot comprehend their failure to appreciate their code is no longer running
on their own system. A bug report is expected to communicate until negotiation
and change for improved outcome results.
The status of the bug report should remain exclusively under the control of the
report author. This is not the case! As the code author keeps changing the
status without any comprehension or negotiation for change!
SOFTWARE/OS VERSIONS
Windows:
MacOS:
Linux/KDE Plasma: Linux Mint Cinnamon 19v1 Tessa
(available in About System)
KDE Frameworks 5.44.0
Qt 5.9.5 (built against 5.9.5)
The xcb windowing system
ADDITIONAL INFORMATION
Bug 404313 was reported 2019-02-14 02:00:40 UTC
This bug was recognised for report on Saturday 2019-02-16 17:49:43 GMT
65.0 Firefox Release January 29, 2019
--
You are receiving this mail because:
You are watching all bug changes.
