Panels have PDF frozen into place since 2.6

Hi,

I have 2.5 on my MacBook and 2.6 on iMac (both Yosemite). My MacBook runs my files no problems; however, 2.6 - each time I load a file and navigate to a pdf; the pdf remains in view no matter what part of the document I click on. I am therefore unable to edit anything, I have tried Was working just fine on my Mac this morning before I updated to 2.6.

I have tried deleting the ui.plist, rebooting Mac, reinstalling 2.6 etc etc

Anyone else got this issue?

Hmm, this sounds like another issue I’ve been keeping tabs on, where someone has described a similar issue with the editor display locking to a particular PDF. In their case, the editor header bar appears to be “stuck” in the drag and drop dark grey colour that you get when dragging a Binder item to the header bar. Are you seeing anything like that?

Are you getting anything on the console when this happens? I’d also try an application preference reset—I don’t see how that would impact anything, but you may as well try it.

Hi,

Thanks for the reply. My editor displays are both the ‘normal’ grey, not as if I’ve dragged and item to turn it dark. The window does allow to scroll and view what ever is in it, but, I cannot change to a different item. Odd how it worked just fine right up until 2.6 went on.

The only other thing I’ve done with the files is share them from MBP to Mac via dropbox. The same fines work fine on the 2.5 MBP but freeze item in editor on 2.6 MAC :frowning:

I have a massive amount of work to do today, luckily the same file is playing nicely on my 2.5 version on my MBP…I’ll keep out of the app store updates!

Please send us the Console logs, as detailed here:

viewtopic.php?f=2&t=29286

Thanks!

A couple of other things, in addition to any console messages:

  • Go to the General preference tab and enable Show internal error alerts at the bottom of this pane. This will enable extra reporting. If an internal error happens, you’ll be presented with a window containing a text dump. Send that to us if you get one.
  • Worst case, if you’re on a deadline and this is making work impossible, you can downgrade back to 2.5 using the change log page on our site.

Exception Name: NSInvalidArgumentException

Exception Reason: -[RMTable setRowOrder:]: unrecognized selector sent to instance 0x9edc990

0 CoreFoundation 0x91ab2343 __raiseError + 195
1 libobjc.A.dylib 0x95151a2a objc_exception_throw + 276
2 CoreFoundation 0x91ab6ea5 -[NSObject(NSObject) doesNotRecognizeSelector:] + 277
3 CoreFoundation 0x919ee348 forwarding + 1032
4 CoreFoundation 0x919edf1e _CF_forwarding_prep_0 + 14
5 CorePDF 0x0193573e -[RMTable initWithRoot:layout:] + 118
6 CorePDF 0x01904d92 -[CPReadingModel addTable:layout:] + 71
7 CorePDF 0x01904e60 -[CPReadingModel tables:layout:] + 69
8 CorePDF 0x01904ea5 -[CPReadingModel tables:layout:] + 138
9 CorePDF 0x01904ea5 -[CPReadingModel tables:layout:] + 138
10 CorePDF 0x0190558e -[CPReadingModel buildModel:pageRange:] + 191
11 CorePDF 0x019056ff -[CPReadingModel buildModel:] + 66
12 CorePDF 0x01904c1e -[CPReadingModel initWithDocument:] + 83
13 PDFKit 0x01282f10 -[PDFDisplayView(PDFViewAccessibility) readingModel] + 115
14 PDFKit 0x01283bde -[PDFDisplayView(PDFViewAccessibility) initializeAccessibility] + 71
15 PDFKit 0x01283c4f -[PDFDisplayView(PDFViewAccessibility) accessibilityIsIgnored] + 33
16 AppKit 0x97fb8663 NSAccessibilityIsAccessibilityElementBase + 387
17 AppKit 0x98079d89 -[NSResponder isAccessibilityElement] + 25
18 AppKit 0x97fbc3c6 NSAccessibilityEntryPointIsAccessibilityElement + 283
19 AppKit 0x97ac01cc NSAccessibilityPostNotificationForObservedElementWithUserInfo + 217
20 AppKit 0x97ac00de NSAccessibilityPostNotificationWithUserInfo + 674
21 AppKit 0x97abfe36 NSAccessibilityPostNotification + 32
22 PDFKit 0x0128472e -[PDFDisplayView(PDFViewAccessibility) invalidateTextSelection] + 35
23 PDFKit 0x01280c05 -[PDFView(PDFViewInternal) internalClearSelection] + 114
24 PDFKit 0x01279d5b -[PDFView(PDFViewInternal) resetDocumentState] + 116
25 PDFKit 0x0127126a -[PDFView setDocument:] + 51
26 Scrivener 0x002385a3 Scrivener + 2323875
27 Scrivener 0x0007e700 Scrivener + 513792
28 Scrivener 0x0007ad6d Scrivener + 499053
29 Scrivener 0x0007aa82 Scrivener + 498306
30 Scrivener 0x000407f7 Scrivener + 260087
31 Foundation 0x9a6d0716 __NSFireDelayedPerform + 489
32 CoreFoundation 0x919f7b06 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 22
33 CoreFoundation 0x919f75b4 __CFRunLoopDoTimer + 1316
34 CoreFoundation 0x91a72fff __CFRunLoopDoTimers + 351
35 CoreFoundation 0x919b0121 __CFRunLoopRun + 2081
36 CoreFoundation 0x919af696 CFRunLoopRunSpecific + 390
37 CoreFoundation 0x919af4fb CFRunLoopRunInMode + 123
38 HIToolbox 0x93173178 RunCurrentEventLoopInMode + 262
39 HIToolbox 0x93172eb1 ReceiveNextEventCommon + 494
40 HIToolbox 0x93172cac _BlockUntilNextEventMatchingListInModeWithFilter + 99
41 AppKit 0x97a60f59 _DPSNextEvent + 734
42 AppKit 0x97a607a1 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 186
43 AppKit 0x97a52f6c -[NSApplication run] + 907
44 AppKit 0x97a3c4d0 NSApplicationMain + 2082
45 Scrivener 0x000355c1 Scrivener + 214465
46 Scrivener 0x00002995 Scrivener + 6549

Thanks. Are you using Accessibility - e.g. VoiceOver or another Accessibility feature - at all? I have just managed to reproduce it by turning VoiceOver on, resulting in exactly the same errors as you reported here. Unfortunately, I’ve also been able to reproduce it in a test app using Apple’s PDFKit, which I’m afraid means that it’s a bug in Apple’s PDFKit on Yosemite and not in Scrivener itself, meaning it’s not something I can fix myself. I have just reported the bug to Apple as bug ID #18754674. If you are using VoiceOver, it seems that turning VoiceOver off allows you to switch to another document in Scrivener, at which point you can turn VoiceOver back on again. Which obviously isn’t ideal. I have, however, noticed that I can’t reproduce the problem in DEVONthink or Skim.app, both of which I thought used Apple’s PDFKit, too… Although, come to think of it, the reason I can’t reproduce it there is most likely because those were built on Mavericks and not on Yosemite.

In fact, I think what I can probably do is create a build of Scrivener 2.6 on Mavericks and upload that - let’s see if that works around the problem. I’ll do that tomorrow (it’s 9.30pm here now).

I’m not using voiceover. My Mac was quite happy with 2.5 and yosemite, it’s only had this isssue since I updated to 2.6, As I’ve said before, the same file is playing nicely with my MBP/Yosemite/2.5.

Thanks for your support and time, it looks like there are a couple (atleast) caught up with this issue.

Try going through the list of applications in the Security & Privacy panel, in the Privacy tab, under “Accessibility” in the sidebar. First, check to see if you have either Parallels Access or Karabiner in the list, if so, disable them and see if the problem is gone back in Scrivener (it should be fixed immediately—you won’t even need to reload the project). If not, I would suggest disabling everything, and then going through the list one-by-one, enabling one program, testing Scrivener, and repeating until it breaks. If you find another program that causes this, let us know.

Same problem. I went through all the accessibility permissions. At first, the solution seemed to be a matter of turning off the Karabiner accessibility permission under “Privacy” in System Preferences. But now it has returned, even with Karabiner accessibility off and the utility itself closed. Below is the error message I’m getting. (It looks to me like PDFKit, unfortunately.) Let me know of sending more info would be useful!

2014-10-29 09:38:46,230 Scrivener[447]: -[RMTable setRowOrder:]: unrecognized selector sent to instance 0x1f1e860

2014-10-29 09:38:46,231 Scrivener[447]: (
0 CoreFoundation 0x99336343 __raiseError + 195
1 libobjc.A.dylib 0x97355a2a objc_exception_throw + 276
2 CoreFoundation 0x9933aea5 -[NSObject(NSObject) doesNotRecognizeSelector:] + 277
3 CoreFoundation 0x99272348 forwarding + 1032
4 CoreFoundation 0x99271f1e _CF_forwarding_prep_0 + 14
5 CorePDF 0x0196e73e -[RMTable initWithRoot:layout:] + 118
6 CorePDF 0x0193dd92 -[CPReadingModel addTable:layout:] + 71
7 CorePDF 0x0193de60 -[CPReadingModel tables:layout:] + 69
8 CorePDF 0x0193dea5 -[CPReadingModel tables:layout:] + 138
9 CorePDF 0x0193dea5 -[CPReadingModel tables:layout:] + 138
10 CorePDF 0x0193dea5 -[CPReadingModel tables:layout:] + 138
11 CorePDF 0x0193e58e -[CPReadingModel buildModel:pageRange:] + 191
12 CorePDF 0x0193e6ff -[CPReadingModel buildModel:] + 66
13 CorePDF 0x0193dc1e -[CPReadingModel initWithDocument:] + 83
14 PDFKit 0x012bbf10 -[PDFDisplayView(PDFViewAccessibility) readingModel] + 115
15 PDFKit 0x012bcbde -[PDFDisplayView(PDFViewAccessibility) initializeAccessibility] + 71
16 PDFKit 0x012bcc4f -[PDFDisplayView(PDFViewAccessibility) accessibilityIsIgnored] + 33
17 AppKit 0x97aa7663 NSAccessibilityIsAccessibilityElementBase + 387
18 AppKit 0x97b68d89 -[NSResponder isAccessibilityElement] + 25
19 AppKit 0x97aab3c6 NSAccessibilityEntryPointIsAccessibilityElement + 283
20 AppKit 0x975af1cc NSAccessibilityPostNotificationForObservedElementWithUserInfo + 217
21 AppKit 0x975af0de NSAccessibilityPostNotificationWithUserInfo + 674
22 AppKit 0x975aee36 NSAccessibilityPostNotification + 32
23 PDFKit 0x012bd72e -[PDFDisplayView(PDFViewAccessibility) invalidateTextSelection] + 35
24 PDFKit 0x012b9c05 -[PDFView(PDFViewInternal) internalClearSelection] + 114
25 PDFKit 0x012b2d5b -[PDFView(PDFViewInternal) resetDocumentState] + 116
26 PDFKit 0x012aa26a -[PDFView setDocument:] + 51
27 Scrivener 0x002383f7 Scrivener + 2323447
28 Scrivener 0x0007e5dc Scrivener + 513500
29 Scrivener 0x0007ac49 Scrivener + 498761
30 Scrivener 0x0007a95e Scrivener + 498014
31 Scrivener 0x00040191 Scrivener + 258449
32 Foundation 0x91bc3716 __NSFireDelayedPerform + 489
33 CoreFoundation 0x9927bb06 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 22
34 CoreFoundation 0x9927b5b4 __CFRunLoopDoTimer + 1316
35 CoreFoundation 0x992f6fff __CFRunLoopDoTimers + 351
36 CoreFoundation 0x99234121 __CFRunLoopRun + 2081
37 CoreFoundation 0x99233696 CFRunLoopRunSpecific + 390
38 CoreFoundation 0x992334fb CFRunLoopRunInMode + 123
39 HIToolbox 0x9a27a178 RunCurrentEventLoopInMode + 262
40 HIToolbox 0x9a279eb1 ReceiveNextEventCommon + 494
41 HIToolbox 0x9a279cac _BlockUntilNextEventMatchingListInModeWithFilter + 99
42 AppKit 0x9754ff59 _DPSNextEvent + 734
43 AppKit 0x9754f7a1 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 186
44 AppKit 0x97541f6c -[NSApplication run] + 907
45 AppKit 0x9752b4d0 NSApplicationMain + 2082
46 Scrivener 0x000023f5 Scrivener + 5109
47 ??? 0x00000001 0x0 + 1
)

Disabling Karabiner and Optimal Layout.app in Accessibility permissions resolved the issue for me.
In fact, you can leave Optimal Layout.app enabled in accessibility permissions and just ask it to ignore scrivener windows. This works as well, just that i decided to block it altogether.

Nevertheless, the Console complained of the following:

10/29/14 3:51:53.599 PM Scrivener[7242]: NSSoftLinking - The ShareKit framework’s library couldn’t be loaded from /System/Library/PrivateFrameworks/ShareKit.framework/Versions/A/ShareKit.
10/29/14 3:51:54.131 PM Scrivener[7242]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo’s operatingSystemVersion property to get correct system version number.
Call location:
10/29/14 3:51:54.131 PM Scrivener[7242]: 0 CarbonCore 0x9b6597e7 ___Gestalt_SystemVersion_block_invoke + 135
10/29/14 3:51:54.131 PM Scrivener[7242]: 1 libdispatch.dylib 0x9300a130 _dispatch_client_callout + 50
10/29/14 3:51:54.131 PM Scrivener[7242]: 2 libdispatch.dylib 0x9300a0b5 dispatch_once_f + 251
10/29/14 3:51:54.131 PM Scrivener[7242]: 3 libdispatch.dylib 0x9300b0d8 dispatch_once + 31
10/29/14 3:51:54.131 PM Scrivener[7242]: 4 CarbonCore 0x9b5ebfb8 _Gestalt_SystemVersion + 1050
10/29/14 3:51:54.132 PM Scrivener[7242]: 5 CarbonCore 0x9b5ebb69 Gestalt + 150
10/29/14 3:51:54.132 PM Scrivener[7242]: 6 Scrivener 0x002dc0b8 Scrivener + 2994360
10/29/14 3:51:55.133 PM Scrivener[7242]: Initializer-based scripting additions are no longer supported. “/Users//Library/ScriptingAdditions/List & Record Tools.osax” not loaded.
10/29/14 3:52:46.567 PM Scrivener[7242]: -[RMTable setRowOrder:]: unrecognized selector sent to instance 0x1f0a2c0
10/29/14 3:54:21.034 PM Scrivener[7242]: -[RMTable setRowOrder:]: unrecognized selector sent to instance 0xc564720
10/29/14 3:54:21.034 PM Scrivener[7242]: -[RMTable setRowOrder:]: unrecognized selector sent to instance 0xc564720
10/29/14 3:54:21.037 PM Scrivener[7242]: (
0 CoreFoundation 0x9898f343 __raiseError + 195
1 libobjc.A.dylib 0x94c4da2a objc_exception_throw + 276
2 CoreFoundation 0x98993ea5 -[NSObject(NSObject) doesNotRecognizeSelector:] + 277
3 CoreFoundation 0x988cb348 forwarding + 1032
4 CoreFoundation 0x988caf1e _CF_forwarding_prep_0 + 14
5 CorePDF 0x0196e73e -[RMTable initWithRoot:layout:] + 118
6 CorePDF 0x0193dd92 -[CPReadingModel addTable:layout:] + 71
7 CorePDF 0x0193de60 -[CPReadingModel tables:layout:] + 69
8 CorePDF 0x0193dea5 -[CPReadingModel tables:layout:] + 138
9 CorePDF 0x0193dea5 -[CPReadingModel tables:layout:] + 138
10 CorePDF 0x0193dea5 -[CPReadingModel tables:layout:] + 138
11 CorePDF 0x0193e58e -[CPReadingModel buildModel:pageRange:] + 191
12 CorePDF 0x0193e6ff -[CPReadingModel buildModel:] + 66
13 CorePDF 0x0193dc1e -[CPReadingModel initWithDocument:] + 83
14 PDFKit 0x012bbf10 -[PDFDisplayView(PDFViewAccessibility) readingModel] + 115
15 PDFKit 0x012bcbde -[PDFDisplayView(PDFViewAccessibility) initializeAccessibility] + 71
16 PDFKit 0x012bcc4f -[PDFDisplayView(PDFViewAccessibility) accessibilityIsIgnored] + 33
17 AppKit 0x9935a663 NSAccessibilityIsAccessibilityElementBase + 387
18 AppKit 0x9941bd89 -[NSResponder isAccessibilityElement] + 25
19 AppKit 0x9935e3c6 NSAccessibilityEntryPointIsAccessibilityElement + 283
20 AppKit 0x98e621cc NSAccessibilityPostNotificationForObservedElementWithUserInfo + 217
21 AppKit 0x98e620de NSAccessibilityPostNotificationWithUserInfo + 674
22 AppKit 0x98e61e36 NSAccessibilityPostNotification + 32
23 PDFKit 0x012bd72e -[PDFDisplayView(PDFViewAccessibility) invalidateTextSelection] + 35
24 PDFKit 0x012b9c05 -[PDFView(PDFViewInternal) internalClearSelection] + 114
25 PDFKit 0x012b2d5b -[PDFView(PDFViewInternal) resetDocumentState] + 116
26 PDFKit 0x012aa26a -[PDFView setDocument:] + 51
27 Scrivener 0x002383f7 Scrivener + 2323447
28 Scrivener 0x0007e5dc Scrivener + 513500
29 Scrivener 0x0007ac49 Scrivener + 498761
30 Scrivener 0x0007a95e Scrivener + 498014
31 Scrivener 0x00040191 Scrivener + 258449
32 Foundation 0x96a57716 __NSFireDelayedPerform + 489
33 CoreFoundation 0x988d4b06 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 22
34 CoreFoundation 0x988d45b4 __CFRunLoopDoTimer + 1316
35 CoreFoundation 0x9894ffff __CFRunLoopDoTimers + 351
36 CoreFoundation 0x9888d121 __CFRunLoopRun + 2081
37 CoreFoundation 0x9888c696 CFRunLoopRunSpecific + 390
38 CoreFoundation 0x9888c4fb CFRunLoopRunInMode + 123
39 HIToolbox 0x97e8e178 RunCurrentEventLoopInMode + 262
40 HIToolbox 0x97e8deb1 ReceiveNextEventCommon + 494
41 HIToolbox 0x97e8dcac _BlockUntilNextEventMatchingListInModeWithFilter + 99
42 AppKit 0x98e02f59 _DPSNextEvent + 734
43 AppKit 0x98e027a1 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 186
44 AppKit 0x98df4f6c -[NSApplication run] + 907
45 AppKit 0x98dde4d0 NSApplicationMain + 2082
46 Scrivener 0x000023f5 Scrivener + 5109
)

Have you gone through the other applications in the privacy panel? It could be there is more than one that is triggering the bug.

ga29fol: when you get this console dump, can you otherwise navigate in the software normally? Maybe try restarting the software if you haven’t.

Oh, and yes at this point I think we have everything we need from console logs and exception reports, thanks to everyone for sending those in. The problems are all addressed identically from what I’ve seen (transient conditions aside). They are unfortunately vague on anything beyond the problem originating from Accessibility through PDF Kit.

This is all really strange. I’ve tested each of the apps I have in Privacy one by one. And for each of them, allowing them to control the computer does not generate new problems, including Karabiner. But turning them off does not solve the problem with Scrivener projects that are already frozen. Even after closing them and reopening them – and even after restarting Scrivener. I’m at a loss.

One tip for anyone struggling with this: If you use a split panel, you can test opening a PDF in one panel, and as long as the other panel is not a PDF, you can then toggle the split off, with the non-PDF panel selected, and then you avoid/undo the freeze. But there are projects that are now unusable until I can get them unfrozen.

You can clear the interface settings for those projects via the instructions here to get them unstuck.