https://bugs.freedesktop.org/show_bug.cgi?id=47368
--- Comment #111 from Roman Eisele <b...@eikota.de> 2012-09-10 09:27:34 UTC ---
First of all:
*** Many many thanks to Tor ***
*** for his great debugging work! ***
*******************************
(In reply to comment #105)
> Actually it is not a good thing at all that we have this one bug report for
> several unrelated crashes (with the only relation being that they happen only
> if some accessibility tool is turned on).
You are completey right. This problem (the confused bug report) has historical
reasons: at the beginning, simple-minded QA volunteers like me thought that we
really had only one bug with some duplicates; as time went by, we realized that
more than one bug was involved, maybe a complete rat nest of bugs, but it was
already so common to mark all Mac accesibility related issues as duplicates of
this bug that no one wanted to change this procedure ...
> The bug described by case I) in comment #93 is now fixed (in master), to tbe
> best of my understanding. But case II) is not. No idea about all the other
> unrelated crashes that this bug might be about.
IIRC many of the Mac accesibility bug reports show similar stack traces,
therefore I still hope that we don’t have 30 or more different Mac accesibility
related bugs, but a small number of bugs, each of them with many duplicates.
But to find out about this, and to make it easier to fix the remaining issues,
it seems necessary that we QA folks follow Rainer’s suggestion:
(In reply to comment #106)
> IMHO we should
> - Make this one (or a different one) a Task bug for tracking these problems
> - Leave those DUPs what have only a very general description
> "crashes when accessibility enabled " as DUPS of the task bug
> - Change many oft the other DUPs what have a detailed description concerning
> the roots of the crashes from "DUP of" to "Blocks Task Bug", so that we
> have a separate Bug report for each bug causing such a crash.
Having already spent much time with all these different Mac accesibility
related issues, and therefore knowing most of them,
I can take this job, if
a) I get some approval to do so (we should not have two people do the same job
at the same time ;-), and
b) we are willing to wait some days -- browsing all the related bug reports
and sorting them will take quite some time ...
Should I begin?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
