![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
On 03/27/2016 09:34 AM, ianseeks wrote:
I was interested in finding out if it was possible to find out if the long standing bugs were "unseen" or "seen" without any status being changed.
If you have a bug found in one release, it will be ignored as a subsequent release is produced, UNLESS you go back, test it again, and update the bug report to report it still has the problem. Basically, if you don't care enough to revisit the bug, they won't care enough to even look at it. I recently was able to shame the Baloo developers into fixing a hack they put in the file extraction routine back in 2014 which prevented the indexing of plain text files unless the extension was .txt. This pretty well eliminated the usefulness of Baloo, because tons of stuff evalutates as plain/text but does not have an extension of .txt. I had to find the exact line in the program that caused this error, and I updated the bug report with every single point release of baloo pointing out that the bug still existed. This went on for a long time before someone noticed. Of course their eventual fix still hasn't made it to Opensuse update Repositories, which is yet another problem. And on any major release, such as moving to Plasma from KDE4, ALL bugs are considered closed, but simply abandoned in the open state. The various bugzillas really do need an Auto-Closed-pending-Reopen status, imposed by some daemon, or triggered by a new release, Which would at least notify the submitter(s) that the bug needs to be re-opened by the original submitter(s) after they verify it still exists. When so many developers are simply volunteers, (and young ones at that), its hard to impose any sense of responsibility, or even pride in workmanship. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org