Mori 1.6.11 crashes with my notebook

Tags ( )

I finally decided to try 1.6.11, after some previous updates didn't work here.

To exclude any interference from 'old stuff' I put Mori 1.6.11, license file, scripts folder and notebook into a test partition with a fresh install of OS X 10.4.11 (no 3rd party SW installed or run). Booted it up, and moved things where they should be.

First ran Mori; it started no problem, wanted to save default notebook as it should.
Doubleckicking license file was also successful.
Quit Mori, and doubleclicked "Getting started" notebook. Mori ran, after a few seconds the 'rebuilding search index' message came up. No problems.

Quit Mori, and doubleclicked my own notebook, which was created (and operated until now) with Mori 1.6.3.
When the notebook opened it displayed correctly, with content, columns, header, footer showing like it was set up.
Yet, when the 'rebuilding search index' message came up Mori crashed immediately.

Now what?
I've attached the crash log.

AttachmentSize
Mori.crash_.log_.zip4.71 KB

Solved?

Well, did some more tinkering. Thought of repairing the original notebook, before throwing it at 1.6.11.
When I then tried to move it into position on the 10.4.11 partition I ran into a permission problem.
Turns out a notebook is a package, which you can't see from the Get Info window.
Opened package, and corrected permissions on content.
1.6.11 now stays open, oh joy..

Does the crashlog indicate this was the problem?

Now to see about getting my custom toolbar, and if all else is OK.

Hopefully, Your Notebook Has No Future Issues

I can't say I'm happy to hear Mori doesn't properly check permissions before updating the search indices, but if your notebook is now properly handled by Mori then that's a big relief. I'll have to make sure it displays a warning if incorrect permissions are found during the search phase.

Anyway, I hope you're able to fully realize the benefits of Mori 1.6.11 now, as I'm preparing to send an alpha of 1.7 into testers' hands.

Alfonso

Take it slowly

I'll play with it for a few days, then it's vacation time (see Soldier Louie).
After that I'll drop 1.6.11 into my home folder, and see what happens.

i did compare the plists - 1.6.11 vs. 1.6.3, and found 2 xxxx.maintoolbar entries in the older version:
NSToolbar Configuration com.apokalypsesoftware.mori.MIUserInterface.maintoolbar
and
NSToolbar Configuration com.hogbaysoftware.BKUserInterface.maintoolbar.

Might cause trouble?

Safer to delete old plist, before running 1.6.11 in that account? Setting up prefs is a very minor effort, compared to isolating causes of crashes or other errors.

Extraneous Pref Settings Do No Harm

Nope. Mori isn't even aware of settings it doesn't specifically ask for. The only time defaults could've adversely affected Mori's behavior is if it were corrupted, or before I added "factory" settings to the preferences retrieval. Default settings shouldn't cause any more trouble.

Taking off for Le Festival Interceltique? Sounds like a lot of fun! Wish I could sell hundreds of Mori licenses by then to go! Quel dommage! Enjoy your time off. We look forward to your return.

Alfonso

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.