Updated from 5.4(?) to 6.0.3.2. Will not print from Writer, will print from Calc. After failure and exit, LO will not start up again, needs reboot. I installed latest JRE, no change. Can't find matching bug in bugzilla. Version: 6.0.3.2 (x64) Build ID: 8f48d515416608e3a835360314dac7e47fd0b821 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: group Printers: Brother MFC-L2740DW, Brother MFC-L2700DW, fails printing to either of them. Print to file... ALSO fails, and similarly, LO will not start up again afterwards. Note that a very similar report is at https://ask.libreoffice.org/en/question/149390/libreoffice-6-writer-wont-printother-lo-apps-will/ She is also using a Brother all-in-one on Win 10. I'm a retired programmer, happy to perform diagnostics for you.
LO is probably hanged, just kill it in Task Manager. Please test with https://dev-builds.libreoffice.org/daily/master/ both LO 32-bit and 64-bit. If you experience this on Win 10 please try also with other Windows if you can. I guess printer drivers are current? Please set https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg.
Created attachment 141607 [details] Backtrace of Writer print failing
Created attachment 141608 [details] backtrace of Calc print succeeding
Ran libo-master64_2018-04-23_23.11.16_LibreOfficeDev_6.1.0.0.alpha0_Win_x64.msi under windbg. As with 6.0.3.2, writer print fails, calc print succeeds. See comments 2,3 for traces. As before, print to file fails from writer. You were correct; a re-run hangs until killing LO in task manager. I updated the print driver from the brother site but the installed driver BRPRM13A.DLL did not change, presumably because it is current. I didn't check 32-bit on Win10. Ask if you need it. I installed 6.1.0.0.alpha0 32-bit on Win7 under VirtualBox and although I have no access to a printer, print to file worked.
Putting back to UNCONFIRMED
Automagically working again: 1. Bring HP Laserjet P3010 online 2. Print document selection to it successfully 3. Print document selection to original failing printer successfully I'm gonna blame Win10 for this.