| Summary: | Multiple symptoms of possibly one underlying issue after upgrading to 5.27 | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Szczepan Hołyszewski <rulatir> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CLOSED NOT A BUG | ||
| Severity: | normal | CC: | kde, nate, nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Szczepan Hołyszewski
2023-02-18 11:31:27 UTC
Please read https://community.kde.org/Get_Involved/Issue_Reporting before reporting further bugs. In particular https://community.kde.org/Get_Involved/Issue_Reporting#Remember_your_manners and https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket (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 [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. I agreee that this is not a bug. It is a disaster. And this is not a bug report, it is a disaster report. Unfortunately there is no separate disasters tracker available at disasters.kde.org, so all I can do is report it here. There is also no official guideline document on reporting disasters, so the report is kind of free-form. Bug reports need to be about one specific actionable issue. This is not an actionable issue as it reports four different, unrelated issues. Please submit four bug reports, one per issue, as each of these issues will have a different root causes. And in each of those bug reports, please try your best to be calm and respectful, so we can avoid arguments and hurt feelings, and also to maximize the change that developers feel like helping out. Thanks! |