I had the same problem. I tracked it down to two calls to update_checker(), one in admin.comprofiler.html.php; the other in comprofiler.class.php. Commenting these two calls allowed my test instance to work.

My test instance is located behind a corporate firewall. I noticed a long time elapsed between clicking on the Config Mgr link and the display of the Config Mgr icon. Now it makes sense that something was timing-out and the code wasn't catching the failure.

Question for developers: Is it really necessary to check for updates with every single action?

rhickers, your tha man (or tha woman)!

I did the same and indeed, the problem was gone.
Shouldn't we enlist this as a bug to the CB team?

Do you know of any other outside calls.... I too am behind a firewall and commented out the two offending calls.

However, I am still experiencing the issues.... dammit

Great find though.....