corrupt

Apple Support was able to solve this for me:

In iBooks on you Mac:

1) First go to Store -> Deauthorize this computer...

2) Then go to Store -> Log out

3) Next go to Store -> Authorize this computer...

4) Finally, go to Store -> Log In

This solved the problem.

I have just had this issue, and followed all the steps that various posts have described.

Then I tried this, and it worked.

deauthorise your iTunes account, and then reauthorise it.

Back up all data. Quit iBooks if it's running.

Hold down the option key and select Go ▹ Library from the Finder menu bar. From the Library folder, delete the following items, if they exist:

Containers/com.apple.BKAgentService

Containers/com.apple.iBooksX

Log out and log back in. Launch the application and test.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

The title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Please read this whole message before doing anything.

This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

Step 1

The purpose of this step is to determine whether the problem is localized to your user account.

Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Step 2

The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Please take this step regardless of the results of Step 1.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.

If you use FileVault 2, then before running the Installer you must launch Disk Utility and select the icon of the FileVault startup volume ("Macintosh HD," unless you gave it a different name.) It will be nested below another icon with the same name. Click the Unlock button in the toolbar and enter your login password when prompted. Then quit Disk Utility to be returned to the main Recovery screen.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.

*The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

I solve this problem weirdly

1. Open the book

2. Switch to another App fast, so the iBook application lose first responder state when the open book animation is still on going

Hope it works for you

I am having the same issue. Here is my log:

11/16/14 5:21:37.248 PM iBooks[4958]: WARN: Asking for an editor frame for something we don't know where it is.

11/16/14 5:21:37.248 PM iBooks[4958]: WARN: Asking for an editor frame for something we don't know where it is.

11/16/14 5:21:37.248 PM iBooks[4958]: WARN: Asking for an editor frame for something we don't know where it is.

11/16/14 5:21:37.248 PM iBooks[4958]: WARN: Asking for an editor frame for something we don't know where it is.

11/16/14 5:21:37.800 PM iBooks[4958]: WARN: Asking for an editor frame for something we don't know where it is.

11/16/14 5:21:40.891 PM storeaccountd[359]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f8e1c5cf1b0> connection from pid 4958 with interface <AccountServiceInterface: 0x7f8e1c5cf4f0> (PID 4958)

11/16/14 5:21:40.894 PM com.apple.CommerceKit.TransactionService[4962]: TransactionServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f8f5502a350> connection from pid 4958 with interface <TransactionServiceInterface: 0x7f8f55057ed0> (PID 4958)

11/16/14 5:21:40.895 PM storeaccountd[359]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f8e1c2d25c0> connection from pid 4962 with interface <AccountServiceInterface: 0x7f8e1c2d31e0> (PID 4962)

11/16/14 5:21:40.906 PM storeaccountd[359]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f8e1c5d2b10> connection from pid 4958 with interface <AccountServiceInterface: 0x7f8e1c5d21f0> (PID 4958)

11/16/14 5:21:41.609 PM storeaccountd[359]: ADI: {

"Cache-Control" = private;

Connection = "keep-alive";

"Content-Encoding" = gzip;

"Content-Length" = 311;

"Content-Type" = "text/xml; charset=UTF-8";

Date = "Sun, 16 Nov 2014 23:21:42 GMT";

Vary = "Accept-Encoding";

"apple-timing-app" = "221 ms";

"cteonnt-length" = 598;

"x-apple-application-instance" = 80007;

"x-apple-application-site" = NWK;

"x-apple-jingle-correlation-key" = 2OSXLANFG4OI6;

"x-webobjects-loadaverage" = 0;

}

11/16/14 5:21:41.610 PM storeaccountd[359]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f8e1c5d5800> connection from pid 4958 with interface <AccountServiceInterface: 0x7f8e1c5d5b20> (PID 4958)

11/16/14 5:21:50.846 PM sharingd[361]: 17:21:50.845 : Starting Handoff advertising

11/16/14 5:22:00.298 PM sharingd[361]: 17:22:00.298 : Starting Handoff advertising

11/16/14 5:22:02.602 PM CalendarAgent[199]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

11/16/14 5:22:02.668 PM CalendarAgent[199]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

11/16/14 5:22:08.651 PM sharingd[361]: 17:22:08.651 : Starting Handoff advertising

11/16/14 5:22:08.769 PM sharingd[361]: 17:22:08.769 : Starting Handoff advertising

11/16/14 5:22:10.773 PM sharingd[361]: 17:22:10.773 : Stopping Handoff advertising

11/16/14 5:22:12.221 PM mdworker[5108]: CoreData: error: Property 'updated' is a scalar type on class 'NSManagedObject' that does not match its Entity's property's scalar type. Dynamically generated accessors do not support implicit type coercion. Cannot generate a getter method for it.

11/16/14 5:22:12.222 PM mdworker[5108]: -[NSManagedObject updated]: unrecognized selector sent to instance 0x7f96cbc3e9d0

11/16/14 5:22:12.222 PM mdworker[5108]: ENSpotlightImporter:importFileAtPath:attributes:error: caught exception: -[NSManagedObject updated]: unrecognized selector sent to instance 0x7f96cbc3e9d0