https://bugs.freedesktop.org/show_bug.cgi?id=77501
Terrence Enger <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from Terrence Enger <[email protected]> --- A couple of ideas, none of them very easy, I fear: (1) Use another program, perhaps Excel, to strip the confidential information from your file. (2) If the present bug happens to be a regression, and if you have enough bandwidth and disk storage, an older version of LibreOffice available through "How to Bibisect" <https://wiki.documentfoundation.org/QA/HowToBibisect> may let you open the file so that you can remove confidential information. As a happy byproduct, the process will identify approximately when the bug entered LibreOffice. I do not use Mac, so you will need to find help elsewhere if you have problems. (3) Install valgrind, run LibreOffice with command-line option --valgrind and make the crash, and attach a typescript of the terminal output. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
