Created attachment 88682 [details]
Full crash report
Using 10.6.8 on both an iMac and a MacBook Pro.
In Text, create a drawing object, e.g. rectangle. Then create another, overlapping the first.
Select the first one and from 'format' choose 'Arrange'>'Move to front'. The object moves and then LibreOffice crashes. I have found this happens consistently, but other users have reported not seeing this fault.
Full crash report attached (also downloadable from http://rfwilmut.net/share/libre_crash.txt )
Operating System: Mac OS X
Version: 184.108.40.206 rc
caolanm->tor: does this backtrace speak to you in any way. No problem under Linux and the bt looks odd to me
No crash here with LibreOffice 220.127.116.11 on OS X 10.9.
Do you have some accessibility tools active? Does the crash go away if you disable them?
(In reply to comment #2)
> No crash here with LibreOffice 18.104.22.168 on OS X 10.9.
> Do you have some accessibility tools active? Does the crash go away if you
> disable them?
Interesting. I"m using QuicKeys; I turned it off and no crash. Turned it back on - crash. So that's the conflict. I don't quite see why having QK running (not actually doing anything) should crash LibreOffice but at least I know where the conflict is.
Well, as you see in the backtrace, it is not LibreOffice code that immediately causes the crash, but code in the OS X Objective-C library (libobjc), called through a dozen of layers of OS X frameworks (CoreFoundation, Foundation, AppKit, HIServices, etc). Perhaps QuickKeys manages to mess up something so that the way LibreOffice uses the OS X APIs (which might be uncommon) causes a crash.
I'd say resolve as NOTOURBUG?
(In reply to comment #4)
> Well, as you see in the backtrace, it is not LibreOffice code that
> immediately causes the crash, but code in the OS X Objective-C library
> (libobjc), called through a dozen of layers of OS X frameworks
> (CoreFoundation, Foundation, AppKit, HIServices, etc). Perhaps QuickKeys
> manages to mess up something so that the way LibreOffice uses the OS X APIs
> (which might be uncommon) causes a crash.
> I'd say resolve as NOTOURBUG?
Certainly a conflict rather than a bug: the exact details are beyond my knowledge; this is going to be one of those problems which won't get resolved (unless the new version of QK - if it ever arrives, which seems doubtful - removes the problem).
Agreeing with Tor.
Setting to NOTOURBUG.
Roger: although this isn't really solved, maybe it's worth pinging the QuickKeys dev. Otherwise we cannot even be sure, he's aware if the issue.
I can try, but it's doubtful any good will come of it - QuicKeys hasn't been updated for two years and though they keep promising an updated version nothing has come of it so far.