Description: Crash if I select file>print or press command-p Steps to Reproduce: 1. Select File, then Print 2. 3. Actual Results: Program becomes unresponvoe Expected Results: Print dialog open Reproducible: Always User Profile Reset: Yes Additional Info: Libre Office 7.0.1.2 Build 7cbcfc562f6eb6708b5ff7d7397325de9e764452
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile ? If you still reproduce this, would it be possible you retrieve extra information? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#macOS:_How_to_get_debug_information)
Please respond on Bugzilla not on my email by using: - https://bugs.documentfoundation.org/show_bug.cgi?id=137331# to comment or https://bugs.documentfoundation.org/attachment.cgi?bugid=137331&action=enter to comment and attach a file.
Yes, I tried creating the user profile but was still able to recreate the crash.
Created attachment 166245 [details] Crashes on Print
According to https://en.wikipedia.org/wiki/MacOS_Big_Sur, it's a beta version of MacOs. Just to be sure, are you able to print on other apps than LO? Alex: thought you might be interested in this one since it concerns MacOs
First of all, you guys are awesome, I've never reported a bug before. Your quick responses are impressive. Second, I know it's a beta version of MacOS. The problem with LO printing didn't come up until the most recent beta, and I am currently able to print from all other applications from which I have tried to print. Thank you!!
The main pb will be to fix this since most LO dev experts are on Linux and very few have a Mac so for MacOs beta 11.0. If you need to print, I hope you got another machine since I don't think you can expect a fix at short/middle term ; but I may be wrong of course!
Not much I can help with here, unfortunately, as I don't have BigSur, nor will I be downloading it to try it out before GA release.
@jselby : By any chance, when the soffice process hangs, is anything produced in the system log ? That might help pinpoint the issue. It might also be helpful if you get a crashlog, although it seems to me that Apple's internal crash reporter no longer gets systematically called when LO dies unexpectedly (more's the pity).
FYI - whatever developer beta apple released today (think it's dev beta 10, October 14, 2020), has made this problem go away. Command-P or file-print behaves as expected (brings out the print dialogue, no crash).
[Automated Action] NeedInfo-To-Unconfirmed
Thank you for your feedback. Let's put this one to WFM then.