Bug 71255 - EDITING: Crash on moving an object forward
Summary: EDITING: Crash on moving an object forward
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.3.2 release
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-05 10:26 UTC by Roger Wilmut
Modified: 2013-11-22 16:29 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Full crash report (45.34 KB, text/plain)
2013-11-05 10:26 UTC, Roger Wilmut
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Wilmut 2013-11-05 10:26:34 UTC
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: 4.1.3.2 rc
Comment 1 Caolán McNamara 2013-11-05 12:03:27 UTC
caolanm->tor: does this backtrace speak to you in any way. No problem under Linux and the bt looks odd to me
Comment 2 Tor Lillqvist 2013-11-05 12:14:55 UTC
No crash here with LibreOffice 4.1.3.2 on OS X 10.9.

Do you have some accessibility tools active? Does the crash go away if you disable them?
Comment 3 Roger Wilmut 2013-11-05 13:04:15 UTC
(In reply to comment #2)
> No crash here with LibreOffice 4.1.3.2 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.
Comment 4 Tor Lillqvist 2013-11-05 13:18:17 UTC
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?
Comment 5 Roger Wilmut 2013-11-05 19:49:25 UTC
(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).
Comment 6 retired 2013-11-22 14:44:35 UTC
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.
Comment 7 Roger Wilmut 2013-11-22 16:29:38 UTC
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.