@Markus, *
Looks like we can "Custom Search" search on the "Crash report or crash
signature" for an "is not empty" value, so only advantage to having a
keyword set would be to identify the BZ as being generated from the CR
portal on review rather than by a user when the CR is submitted.
Would
Since LO now has a crash report then there is no need to do backtraces,
right?
When I reproduce a crash, how can I link the crash report to the bug report
in the tracker?
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-no-subject-tp4187667p4187714.html
On Fri, Jul 1, 2016 at 6:06 PM, Pedro wrote:
> Since LO now has a crash report then there is no need to do backtraces,
> right?
>
>
So the crash reporter only works in official TDF builds. So currently in
the 5.2.0.0 beta2 build, the 5.2.0.1 build and any following beta, rc