[NetworkShadow]

They just started locking-up on me, I'd only notice because my clock's time was the same as when I logged-in and my MenuMeters CPU and ram stats wheren't loading... So I tried to reinstall both the MenuExtra Enabler and APE, they come back to life as soon as I reinstall MenuExtra Enabler but when I log-out and back in they are locked-up again. I don't know if it's SS related or directly related to APE, any ideas? I'm running Ashen, but I first noticed it with some other theme. What's going on?

Edit: And I'm getting "Menu Extra Could Not Load For instructions on enabling third-party menu extras please see the documentation." Error messages when I try and re-enable my MenuMeters.

[FB Eye]

I had a similar problem running MenuMeters, it would not load at startup. The culprit is MenuCracker, something that resides in some apps that display stuff in the menu bar. With MenuMeters, I was also runnning DeskShade Plus which had an outdated version of MenuCracker.

I flushed DeskShade Plus and problem was gone. I suggest you check your running apps and see inside their packages if any of them use MenuCracker.

Hope this helps!!!

PS. The MenuCracker hint was given to me by the author of MenuMeters.

[Rosyna]

I would sadly have to agree. If menu cracker is installed, it will log to the console that it failed to load and give the path to it.

Also, check /Library/InputManagers and make sure that MagicMenu Enabler isn't installed.

And if you have the keychain access menu item in the menu bar, make sure you are running Menu Extra Enabler 1.0.1. Or else 3rd party menu extras will be wiped out.

[NetworkShadow]

Originally posted by FB Eye:
I flushed DeskShade Plus and problem was gone. I suggest you check your running apps and see inside their packages if any of them use MenuCracker.

Hope this helps!!!

PS. The MenuCracker hint was given to me by the author of MenuMeters.

Thanks. I'll look into it, but I'm not really running a lot of true menu extras... You think that apps like iPod2Go and ProsessWizard could be using MenuCracker?

[NetworkShadow]

Originally posted by Rosyna:
I would sadly have to agree. If menu cracker is installed, it will log to the console that it failed to load and give the path to it.

Also, check /Library/InputManagers and make sure that MagicMenu Enabler isn't installed.

And if you have the keychain access menu item in the menu bar, make sure you are running Menu Extra Enabler 1.0.1. Or else 3rd party menu extras will be wiped out.

No sign of MagicMenu, and I'm running the latest Menu Extra Enabler.

Edit: Found the console log!

Setting Quick Sync menu
MenuCracker
see http://sourceforge.net/projects/menucracker
MenuCracker is now loaded. Ready to accept new menus. Ignore the failure message that follow.
2004-06-16 14:06:09.196 SystemUIServer[371] failed to load Menu Extra: NSBundle </Library/PreferencePanes/MenuMeters.prefPane/Contents/Resources/MenuCracker.menu> (loaded)

Edit: I removed MenuCracker.menu and everything seemed to load smoothly this time. Thanks for your help guys.

[smeger]

We get a lot of tech support mail about this issue and the culprit seems to be MenuCracker. (I say "seems to be" because I haven't personally checked it out).

My understanding is that you can remove MenuCracker and use Menu Extra Enabler instead (Rosyna can probably provide more details here).

This is nothing to do with APE, btw.

For those who have no clue what I'm talking about, there are two types of Menu Extras - ones that live inside of SystemUIServer (and can be command-dragged to change location) and NSStatusItems. The first are not officially supported by Apple, but lots of devs use them anyway. MenuCracker and Menu Extra Enabler are two different ways a developer can use to hack their unsupported menu extra into SystemUIServer.

[NetworkShadow]

Originally posted by smeger:
This is nothing to do with APE, btw.

I didn't think so, if anything I thought maybe Menu Extra Enabler.

[Rosyna]

Originally posted by NetworkShadow:
I didn't think so, if anything I thought maybe Menu Extra Enabler.

Nah. For what its worth, MEE hasn't had a single bug. People that think they have a "bug" (you know, removing MEE stops the behaviour they are seeing) usually have a buggy menu extra installed. Not exactly something I can respond to..