https://bugs.kde.org/show_bug.cgi?id=465992
Szczepan Hołyszewski <rula...@wp.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOT A BUG |---
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
--- Comment #3 from Szczepan Hołyszewski <rula...@wp.pl> ---
[posted prematurely, because saving the edited title apparently submits the
comment too]
(In reply to Nicolas Fella from comment #1)
> Please read https://community.kde.org/Get_Involved/Issue_Reporting before
> reporting further bugs.
TL;DR: This Is Different.
Long version: I know how to report regular bugs, and I have a record on this
bugtracker to prove it. This is not a regular bug, therefore this bug report is
not a regular bug report. This is a situation where a user logs in to a newly
updated desktop and is met with an avalanche of glitches, none of which were
present before the update. Nothing remotely like this has happened in my 15+
years with KDE. This is a never before seen situation that the document you
quoted doesn't cover?
> https://community.kde.org/Get_Involved/Issue_Reporting#Remember_your_manners
I fail to find in that document an interdiction against stating facts.
> https://community.kde.org/Get_Involved/
> Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket
I am reporting multiple _symptoms_ that manifested all at once as a result of a
single update. When something like that happens, it is quite possible that all
the symptoms are different manifestation of a single bug, but I am not able to
ascertain whether that's the case, so the next best thing I can do is report
the symptoms, and YES report them together, because their correlation and
co-occurrence may actually be something that a programmer debugging the issue
might want to know.
--
You are receiving this mail because:
You are watching all bug changes.
