<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - No dialog shown, still crashreport uploaded to TDF" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128255#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - No dialog shown, still crashreport uploaded to TDF" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128255">bug 128255</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>@Xisco, I think you have pretty much quashed this non issue. Per OPs <a href="show_bug.cgi?id=128255#c2">comment 2</a> "I never saw the Crash Report Dialog", meaning the OP never established they'd actually submitted a crash report, or that a Breakpad minidump was even generated on their system for submission. A lingering aspect of reporting for resolved <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED FIXED - Crash when trying to delete unused User Field" href="show_bug.cgi?id=128232">bug 128232</a> They could of course now run the the crash inducing STR from <a class="bz_bug_link bz_status_NEW " title="NEW - CRASH: deleting content" href="show_bug.cgi?id=124738">bug 124738</a>, while Wireshark or similar is running, then parse and provide results as you've done, to replicate your finding. But point is there is no cURL upload of the minidump without express user release from their system--which is the correct and expected behavior. Personally I am still interested in the BOD response to adjusting the Privacy notice(s) to cover this, but as Thorsten had adjusted the scope of this issue to be just the upload without notification, this should now be closed either 'Invalid', or 'Insufficient Data'. Stuart</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>