https://bugs.kde.org/show_bug.cgi?id=454345
--- Comment #67 from Uwe Dippel <udip...@gmail.com> --- (In reply to Ric Grant from comment #65) > (In reply to Nate Graham from comment #63) > > The user-facing issue of desktop icons being re-arranged turns out to have > > multiple causes. It isn't feasible to track them all in a single bug report; > > that's not how issue tracking works. We need a separate bug report per > > discovered cause, so we can fix them individually. That's just the way issue > > tracking works, I'm afraid. > > Ignoring previous tickets for now, this ticket as its own instance was > originally opened May 2022 by William. His report was that when icons are > placed on a desktop and plasmashell is restarted, said icons scramble. This > issue, as a standalone bug, is still an issue. > > If this ticket is closed somebody is just going to open another, reporting > the same problem, and we're going to go through all of this again until it's > again closed in this utterly ridiculous cycle. > > I totally appreciate this isn't a simple fix but we can't just keep on > closing these tickets and expecting the problem to be resolved somewhere > else. Apart from anything else, opening multiple tickets for what is > essentially the same problem just makes KDE as a whole appear buggier than > it really is, in terms of number of but reports at least. > > This, and all other related tickets, should be left unresolved, grouped, and > cross referenced so that when related issues are resolved, developers can > check whether these reports are also resolved and tick them off when that > time comes, otherwise leaving them open for somebody to pick up at some > point. > > That's how bug tracking works. Not having a reputation system, I can only write 'Thumbs up!'. It would really be a pity, if this in principle great project not only had a quality controller who knows nilch about quality control, but also a bug reporting system where responsables would understand only little about bug reporting. Having been in this business for 25+ years, if I find a bug, I check the list of bugs. If my observation was 'solved' in version x.y.z some two years ago, I'd assume another bug. And file a report. Instead, a 'Won't fix' would tell me to stop, live with this bug, work around it, buy a MS licence, or whatnot. Until it get's 'closed' and 'resolved'. Then I'd check for x.y.z; and I'd know about an eventual upgrade. One COULD even create a meta-report, like "Any kind of inconsistent icon position, be it at startup, restart, monitor change, etc." And mark it as "verified" "Won't fix" and an explanation. And relate all existing, different bugs reports there. -- You are receiving this mail because: You are watching all bug changes.
