to run
it--currently return invalid.
Stuart
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Bugs-with-Backtrace-but-Not-Reproduced-tp4142359p4142406.html
Sent from the QA mailing list archive at Nabble.com
@Joel,
Think you need to share that query list for us to be able to run
it--currently return invalid.
Stuart
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Bugs-with-Backtrace-but-Not-Reproduced-tp4142359p4142406.html
Sent from the QA mailing list
Le 06/03/2015 16:00, Joel Madero a écrit :
There doesn't seem to be a backtrace with bug 89628, or did I miss
something ?
Alex
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
Le 06/03/2015 16:00, Joel Madero a écrit :
No backtrace on bug 89844 either ?
Alex
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
,
not by QA.
Just my 2 cents.
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Bugs-with-Backtrace-but-Not-Reproduced-tp4142359p4142374.html
Sent from the QA mailing list archive at Nabble.com.
___
List Name
Hi All,
I'm curious if anyone has any thoughts about bugs that have backtraces
but QA has been unable to repro. Should these just be pushed to NEW ?
Currently there are 8 UNCONFIRMED crashers - at least one or two of
those have backtraces but have had other members of QA say they cannot