This happens in OS X 10.6 and above according to my tests. Using the [Command]+[`] key combination with 2 spreadsheets open in Calc ends up in a "Libre Office quit unexpectedly" dialog box. Here's what I do to trigger the crash: 1) Open Libre Office 2) Open 2 existing spreadsheets (both in ODS in my case) 3) Type anything in a cell of spreadsheet 1 4) [Command]+[`] in order to switch to spreadsheet 2 5) Type anything in a cell of spreadsheet 2 6) [Command]+[`] in order to switch back to spreadsheet 1 7) Now, simply trying to navigate within the spreadsheet being with the mouse or the keyboard instantly results in Libre Office becoming unresponsive with the cursor turning into the beach ball of death and then everything closes with the "quit unexpectedly" dialog 8) The crash may not always be triggered on the first [Command]+[`] attempt but sometimes the ones after This happens from Libre Office 4.2.5.2 (not previous versions) all the way to the latest stable as of this day (4.3.5).
Not reproducible on Version: 4.5.0.0.alpha0+ Build ID: 6143a7eeabea394133c54e97e3690bdf40b98247 Locale: fr_ OSX 10.10.2 You have reported against LO 4252. Please test against a current production release of LO and specify your OS version. When you write "on OSX 10.6 and above" do you mean that you've tested this on more recent versions of OSX ? if so, which ones ? The 4.2.x series is end of life. The 4.3.x series is the last for which 32bit builds will be released. LO 4.4.x builds are all 64bit and are not intended to be run on OSX 10.6, as that baseline is no longer supported for the 4.4.x series. Setting to NEEDINFO. Please report back with your test details and reset to UNCONFIRMED
Thank you for the feedback. I originally did my tests with OS X 10.6.8, 10.7.x and 10.9.x machines with only "stable" releases. Since then, I've had the opportunity to do more tests with OS X 10.10 and the latest Evolution version (as of this writing). Under OS X 10.10.2 with latest stable (4.3.5), the bug still occurs. Under OS X 10.10.2 with latest Evolution (4.4.0), the bug is gone. So, I guess our 10.6.8 users will have no choice except reverting back to an older version of LO or finding a way to make them migrate to OS X 10.8 at least (not a big deal since only one of our users was using [Command]+[`] actively). (In reply to Alex Thurgood from comment #1) > Not reproducible on > > Version: 4.5.0.0.alpha0+ > Build ID: 6143a7eeabea394133c54e97e3690bdf40b98247 > Locale: fr_ > > OSX 10.10.2 > > You have reported against LO 4252. > Please test against a current production release of LO and specify your OS > version. > > When you write "on OSX 10.6 and above" do you mean that you've tested this > on more recent versions of OSX ? if so, which ones ? > > The 4.2.x series is end of life. > The 4.3.x series is the last for which 32bit builds will be released. > LO 4.4.x builds are all 64bit and are not intended to be run on OSX 10.6, as > that baseline is no longer supported for the 4.4.x series. > > Setting to NEEDINFO. Please report back with your test details and reset to > UNCONFIRMED
Per comment 2, setting as wfm
It is unfortunate for your 10.6 user, yes, but 4.3 is nearly end of life anyway (May 2015). Perhaps the fix that allows it to work in 440 will also make (have made) it into LO 436/7 ?
That's a good suggestion. I finally did a test with 4.3.6.2 under OS X 10.6.8 and indeed the bug doesn't occur. So, I'll stick to that temporary solution before starting migrating our users to OS X 10.8 (it is planned, as OS X 10.6.8 is getting old and the number of non-working programs may increase over time). I'm glad in all that the bug disappeared staring from 4.3.6 and didn't reappear with later releases. Thank you for the feedback.