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
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.
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
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!
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.
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
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:
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.