Description: This bug was discovered in a Chinese LO user discuss group and reproduced by three different users, but there is also one user who can't reproduce at all. Hope one of the developers can reproduce it, but if not, we can provide more information. The crash happens when the "Mininize Presentation..." wizard got its save file dialog window cancelled. Steps to Reproduce: 1. Open a blank presentation. 2. Click Tools -> Minimize Presentation..., the wizard pops out. 3. Don't change any default options. Click "Finish" button at the last step, a file chooser dialog window pops out. 4. Click "Cancel" or the "x" button on the top right corner. Actual Results: LO hangs for a while (about 10 seconds in my case), then crashes. Expected Results: The file chooser dialog disappears and the user is back to the wizard window to do more changes. Reproducible: Always User Profile Reset: Yes Additional Info: So far the three users that can reproduce are all on Windows 10, specifically: LO 6.1.5 on Win10 Home Edition LO 6.2.1 on Win10 Home Edition LO 6.2.1 on Win10 Professional Edition My "About" information is as follows: Version: 6.1.5.2 (x64) Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805 CPU threads: 2; OS: Windows 10.0; UI render: default; Locale: zh-CN (zh_CN); Calc: group threaded My locale is Chinese, but UI interface is English. The other two users are both using Chinese interface, I believe, so that shouldn't be the issue. I can also reproduce in safe mode.
> Steps to Reproduce: > 1. Open a blank presentation. I think I meant "Create a new, blank presentation." > 2. Click Tools -> Minimize Presentation..., the wizard pops out. > 3. Don't change any default options. Click "Finish" button at the last > step, a file chooser dialog window pops out. > 4. Click "Cancel" or the "x" button on the top right corner.
On win10 + LO 6.2.2.2, I could reproduce this.
I just tested with the recent releases, and can't reproduce in either 6.1.6 or 6.2.4 RC1. (Just to be sure, I could still reproduce in 6.1.5 before I upgraded.) Did someone fix this and forgot to ping this bug? Or was it a byproduct of the work done on some other front?
Duplicate of #123502, perhaps?
Let's put this one to WFM then since you don't reproduce this anymore. About how it's been fixed, don't know and don't know too if it's a dup or not.