Previous 1 2 Next 20 Replies Latest reply: Nov 13, 2007 9:18 PM by clindberg
Richard Hallas Level 1 (0 points)
Hi,

I've recently upgraded to Leopard and Aperture 1.5.6 appears to be working fine for me after a brief test (nothing exhaustive as yet).

However, if I try to access the Preferences window from the Aperture application menu, Aperture dies 100% of the time. I choose the menu option, the beachball cursor appears for a bit, and then Aperture just quits. So at present I can't alter anything in the preferences.

I haven't managed to discover whether some other software is causing this to happen or whether it's something to do with Leopard itself. Does anyone else see this behaviour?

PowerMac G5, Mac OS X (10.5), Dual 2.5GHz, Radeon X800
  • Paul Westlake1 Level 1 (120 points)
    Richard,

    Probably not what you want to hear, but Aperture 1.5.6 and Leopard on both my iMac and MBP don't have this issue.

    I can get into Preferences without problem on both machines.

    Sorry!

    Paul
  • Richard Hallas Level 1 (0 points)
    Thanks for that, Paul.

    I note that both of your machines are Intel-based. Can anyone with a PowerPC system reproduce my problem?
  • tidysteve Level 4 (2,975 points)
    does the same thing occur when using the keyboard shortcut ??? it is

    command-comma ...
  • Richard Hallas Level 1 (0 points)
    Yes, pressing the keyboard shortcut has just the same effect as choosing the menu option. Bang!
  • tidysteve Level 4 (2,975 points)
    does the same thing occur in any other application ???
  • Richard Hallas Level 1 (0 points)
    Nope. This problem is Aperture-only, which is largely why I'm asking here whether anyone else with a PPC system is suffering from it. I'd like to know whether it's a bug that other users experience, or something weird about my own setup.
  • tidysteve Level 4 (2,975 points)
    just checking ... this way we can start to rule out things ...

    i have my test box (ppc) running 1.5.6 and leopard ... i will check it to see if i can reproduce the crash ...

    can you locate the crash log and post ???

    in the meantime trash your preference file for aperture ...

    Library/Preferences/com.apple.Aperture.plist

    restart aperture and see if that cures it ...
  • MD5 Level 1 (0 points)
    Unfortunately neither deleting preference file nor reinstalling do not help in...
  • tidysteve Level 4 (2,975 points)
    please post crash logs
  • Richard Hallas Level 1 (0 points)
    Hi,

    I'm sorry to say that I can't post a crash log here. I don't know why, and I've been trying repeatedly ever since yesterday evening. Perhaps the problem is the length of the message, but Apple's server simply won't take it. I click Post Message and nothing happens. (I've tried multiple browsers, too.)

    However, what I can say is that a person from Apple has emailed me privately, and I've sent the crash log to him along with a system profile.

    Removing the preferences file was a good idea that I should have thought to try myself. However, having done it, I found that it didn't make any difference. The crashes were just the same.

    I've also since discovered that the crash affects the first two items on the Presets submenu (the one just below the Preferences option) similarly. Image Export and Web Export crash in just the same way. However, the remaining three items on the Presets submenu (Slideshow etc.) open their windows normally.
  • tidysteve Level 4 (2,975 points)
    for the life of me, i haven't been able to replicate on my ppc box ...

    that is good news that apple contacted you ... here's to hoping that they have some insight ... please let us know what they tell you ...
  • Richard Hallas Level 1 (0 points)
    It's solved!

    I suddenly realised, after spending ages looking at the Aperture crash reports and doing other testing, that I'd completely forgotten to see if there was any useful Console output when Aperture crashed. So I had a look and found a very revealing line associated with each crash, saying:

    "Custom ColorPicker class with name .DS_Store could not be loaded."

    I wouldn't have expected colour pickers to be involved when merely opening preference windows that apparently don't use them, but removing the custom pickers seemed the obvious thing to try, and did indeed cause the crash to go away. So I narrowed down the search and have identified the culprit as the RCWebColorPicker which can be obtained from here:

    http://www.rubicode.com/Software/RCWebColorPicker/

    I had version 1.0 installed and found that a 1.1 update had been issued, so I attempted to download it. It turns out that the link to version 1.1 is actually broken and just leads to a 'not found' page, but after a brief experiment in editing the URL, I found that the following works:

    http://www.rubicode.com/Downloads/RCWebColorPicker-1.1.dmg

    However, version 1.1 suffers from the same problem as 1.0 (i.e. it upsets Aperture), so I mention the above just in case anyone's interested in investigating further. Obviously I wouldn't recommend installing it at present! Source code to the picker is actually available on the site, and I'm going to email the author to let him know about the problem.

    The interesting thing is that I've had this picker running fine under Tiger since last year and it hasn't caused a problem with Aperture in the past, so the problem behaviour is new to Leopard.

    My thanks to everyone who offered help here, and to the Apple programmer who emailed me privately.
  • rjslade Level 1 (0 points)
    Thanks for the solution - I was bitten by the same issue today on a G5 Duo and Leopard.
    Initial discovery was any type of export created a program crash. Then discovered that try to choose preferences resulted in same issue! Remove RCWebColorPicker from the colour User Library/ColorPickers and the problem both are gone. You might want to pass this onto MacFixIt and other Aperture support sites. Hopefully Apple will note this issue and make the solution more prominent. - R
  • Richard Hallas Level 1 (0 points)
    I'm pleased to say that the author of the colour picker has been very helpful and responsive to the issue, now that it's been tracked down. He's sent me several test builds of the picker and has now discovered the cause of the problem, with the result that the latest test build works perfectly. An official release of an update is expected very soon.
Previous 1 2 Next