Yeah, that's got us stumped too. Something is different. It could even be a permissions difference. It's probably something small and seemingly insignificant. I'm going to do investigation on a wider group of computers and see if we can reproduce the problem.

They share some of the same preferences files, so that's probably what you're seeing.

Since server problems seem to have gotten swamped by Menu Extra issues, let me try this again.

Above is the symptom. Again, even trying to create a new event server from scratch didn't seem to avoid this. (I didn't try a new contact server.)

I don't see any useful logs -- there are no relevant console messages or system.log entries, and the server is hanging not crashing. (I could probably get it to hang again and take a snapshot with the activity monitor... I don't recall what options exist for capturing that conveniently to a file, though.)

I'll attach my system profile (zipped plain text format). Aluminum iMac 2.4Ghz, 4Gb, 10.5.1, etc...

This stuff probably isn't that useful, but it might give a hint. I saved "Sample Process" stack traces in Activity Monitor, which shows both servers have a thread blocked in select() and another doing a socket release in the main app loop. This trace seems to be repeatable any number of times but while the numbers on the trace change they all change together and I really don't know offhand what it means -- so I can't guess whether it's hanging on the leaf spinlock or just repeatedly looping through some cycle of calls.

There's a screen snap of the server manager window, too, for the heck of it.

---added.... ---

And, for the heck of it, I decided to try out the Instruments tool mentioned in the other topic. If I'm reading this right, it appears to be saying that it is indeed stuck in the _spin_lock() leaf call, because "# Self" counter is racking up in that frame and not in the others. Since the only other thread is blocked in select(), most likely either it holds the spin lock, or someone didn't release it. Whether that's eventserver itself, CoreFoundation, or CFNetwork, I couldn't begin to guess. ;-)

In fairness, this thread was started to address the issues with QC and QD not appearing in the menu, so server questions are really a "threadjack". There's another thread for Server/Leopard issues.

Well, the topic title was "NUDC 5.3.2 beta (26NOV2007) and Leopard", not "QC/QD problems", so I took the intent as more general. But, yeah, there needn't be only one 5.3.2 beta 1 topic, so, sure. ;-)

For folks reporting the QC/QD bug, please try the following:

1. Move /Library/InputManagers/Menu Extra Enabler to the trash
2. Move ~/Library/InputManagers/Menu Extra Enabler to the trash
3. Install NUDC 5.3.2b1 (this installs a new Library/InputManagers/Menu Extra Enabler)
4. Restart
5. Toggle on the QuickContact menu inside of Now Contact preferences
6. Toggle on the QuickDay menu inside of Now Up-to-Date preferences

So far we have only one report of this working.

It appears there may be either an ownership or permissions issue inside of the Menu Extra Enabler as currently installed on some people's computers. For computers that can't run our QC/QD menu extras, it looks like they also cannot run menu extras from other vendors either. (I'm looking for further information that confirms or denies the above.)

I have Synergy (the iTunes add-on) and Memeo LifeAgent, both of which put items in the menu bar, running and neither have any problems whereas QD/QC does. Neither Synergy nor LifeAgent use Menu Extra Enabler, so it's almost certainly an issue with MEE, not with menu extras per se.

You might want to see if anyone else with the problem is on the Nighthawk beta team. NH seems to cause fits with the menu extras with NUDC 5.3.2b1 (I have to uninstall NH and reinstall NUDC to get QD and QC to work).

Correct. From what we saw from the above, the problem has to do with ownership/permissions problems in the MEE bundle. Once those are corrected, menu extras that use Menu Extra Enabler also work (at least on the computers we've tested against).


That's probably because of the MEE permissions issues. That's fixed in next week's NightHawk b8 release.

Do you know what the permissions should be under Leopard? I'd be interested to see if they could be corrected manually and thereby get QC and QD to work.

Thanks.