https://bugs.kde.org/show_bug.cgi?id=325224
--- Comment #89 from Erik Quaeghebeur <k...@equaeghe.nospammail.net> --- (In reply to Muck from comment #88) > Bug 325224 has been reported 2013-09-24, got 429 votes and has 47 users on > the CC List. Now it's marked as duplicate of Bug 386985, which has been > reported 2017-11-16, got only 60 votes and only 10 users on CC. Is it best > practice to close the "origin bug" (Bug 325224) or should it be the other > way round? I understand your reaction. But I have my reasons, which I hope you can sufficiently agree with: * This bug report contains a mix of different issues, some fixed, some not. There is no overview and focus. The most recent ones and most persistent ones all point to the issue treated with more focus in the newer report. * The newer report contains links to an actual patch that fixed the issue, but which was reverted by developers when that patch caused an issue for their server. That patch is still the best starting point to fix the issue. > The 47 users from Bug 325224 will they be added to Bug 386985 > automatically? No, it seems not. Each user will have to do this themselves. It is also an opportunity to test the current situation and report back at the bug report this report is now a duplicate of. Please do not comment if you have no information to add (e.g., reporting that a certain server does or does not exhibit the issue is useful, but only saying that it is a disgrace the bug hasn't been fixed yet isn't). Of course, please vote again if you are still affected by this issue. -- You are receiving this mail because: You are watching all bug changes.
