Description: Any attempts to use tools > customize lead to crash recovery dialogue. Details below. Steps to Reproduce: 1.Open a new writer or calc document 2.Select Tools > Customize 3. Select OK (you don't even need to try to do anything) Actual Results: Dialogue closes, revealing the start of the crash recovery dialogue. You can continue with the recovery, it appears, but I didn't really bother. Expected Results: The Tools>Customize dialogue should simply close, revealing just the empty document from step 1. Reproducible: Always User Profile Reset: Yes Additional Info: I had deleted all prefs (LibreOfficeDev in App support, org.libreoffice.script.plist in prefs) so should have been a clean start. I did try making some changes to some keyboard bindings; one of them MAY have taken, not sure. Version: 6.1.0.0.alpha0+ Build ID: 8e8dd8f320a3ff59ff8a16c1a7a867888ce80700 CPU threads: 4; OS: Mac OS X 10.13.3; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-03-13_23:59:29 Locale: en-US (en_US.UTF-8); Calc: group User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/604.5.6 (KHTML, like Gecko) Version/11.0.3 Safari/604.5.6
Created attachment 140680 [details] window that comes up after closing tools > customize
Presumably this should be chained to the meta bug for tools > customize that someone pointed me to the other day, but I don't know how to do that, although this sounds like something that just happened, since it wasn't (isn't -- just rechecked) in 6.0.2.1
There was a recent crash fix: bug 116392 Can you still reproduce with a fresh daily build?
I'll let you know... I am now thoroughly confused as to where to find the most recent version! Do I look here: https://dev-builds.libreoffice.org/daily/libreoffice-6-0/ or here: https://dev-builds.libreoffice.org/daily/master/ ? One leads to master~2018-03-13_23.59.29_LibreOfficeDev_6.1.0.0.alpha0_MacOS_x86-64.dmg and the other to libreoffice-6-0~2018-03-13_10.45.37_LibreOfficeDev_6.0.3.0.0_MacOS_x86-64.dmg as the most recent version. It's the one called 6.1.0.0.alpha0 that I tested that has this bug (crash dialogue after tools/customize...) and it does have the later date. I'm in the process of downloading the 6.0.3.0.0 one. OK. 6.0.3.0.0 does not have this bug. But it does have the bug (extraneous blank window, bug 116277) in the labels feature I reported that was fixed in 6.1.0.0.alpha0. So is there some other build between those two that I haven't stumbled across? FWIW, the most recent Mac build seems to be those two listed above, which are dated 2018-Mar-14 00:49 (daily/master tree) or 2018-Mar-13 11:14 (daily/libreoffice-6-0 tree) in the file listings. (I can understand how the time stamp in the directory is a little later than the time put in the file name.)
Ah, sorry about that. I didn't check the builds and indeed the macOS builds have broken. We have to wait for them to start working again to get new ones.
This bug not present in 6.0.4.0, although the tools > customize dialogue doesn't seem to "stick" for several tries in trying to modify a setting (swapping delete left with delete right for clearing a cell in calc.) Haven't checked if there's a new build of 6.1.0.0.alpha0 (or whatever it would be called) But at least I could get it to work.
(In reply to Ted Lee from comment #6) > This bug not present in 6.0.4.0, although the tools > customize dialogue > doesn't seem to "stick" for several tries in trying to modify a setting > (swapping delete left with delete right for clearing a cell in calc.) > Haven't checked if there's a new build of 6.1.0.0.alpha0 (or whatever it > would be called) But at least I could get it to work. The particular crash regression I suspected was never committed to the 6.0 branch. The Mac builds are working again: https://dev-builds.libreoffice.org/daily/master/MacOSX-x86_64@49-TDF/current/
OK, checked the latest "master" build. Bug not present in Version: 6.1.0.0.alpha0+ Build ID: fa1db85bc3cd49407a2f1cfa44433e2718a35baf CPU threads: 4; OS: Mac OS X 10.13.3; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-03-23_04:02:46
*** This bug has been marked as a duplicate of bug 116392 ***