OK, a few fundamental things we need to work out:
1.) So you're satisfied now that colors look OK only when your MacBook Pro is hooked up to your CRT? Now, ditch the CRT, restart MacBook Pro. Are you still getting 'correct' colors?
2.) Please answer Serge's question: what monitor profile is OS X now using?
3.) To a number of the posters here: who the heck made it up in their minds that color-managed applications and non-color-managed applications are *supposed* display the same colors for a sRGB image when color management is properly set up and monitors are profiled? This is crazy, and would *only* be true if your monitor's profile, after proper hardware calibration, happened to basically be the exact inverse transform of the sRGB profile. And that would be true only if your monitor had a very 'sRGB-like response' (as Serge points out).
Non-color managed applications are not correcting for your monitor. Color-managed applications are. Why on earth would those two scenarios end up displaying the same colors? ONLY in the following two situations could one expect this:
a.) If hardware calibrators (technically, hardware 'profilers', since these devices are not adjusting any hardware on your display but, instead, adjusting the output sent from your video card so that colors look more accurate on your display) were designed to bring your monitor back to a 'sRGB-like response', then, sure... you could then expect color-managed & non-color-managed applications to display the same colors.
b.) If, upon profiling your display, the profile generated happened to roughly be the inverse transform of the sRGB profile (this would happen if your monitor had a very 'sRGB-like' response... meaning that a raw RGB value thrown at it from your OS is naturally displayed on your display as the corresponding CIE LAB color that Photoshop, or any color-managed application, would have calculated itself in taking any raw RGB value from a sRGB-tagged image and converting it to the PCS to then convert to the monitor profile).
4.) Andrew, your original colour.png image is flawed, as pure blue should be 0,0,255. In your image, it is 0,0,245. But, that's actually OK for the purposes of our tests. No big deal. The raw RGB values within a strip of blue still contain values of 0,0 for R,G respectively.
5.) When you import a sRGB image into LR, LR works with the image in the ProPhoto RGB color space. Of course, it does so 'non-destructively', so, for the sake of this discussion, let's just say LR creates a new copy of your image in memory when you go into the 'Develop' module. This will be much like opening up the image in Photoshop, and then converting the image from sRGB to ProPhoto RGB (using, e.g., relative colorimetric). This process DOES, in fact, change the raw RGB values of the image. That's why when you convert a sRGB image to the ProPhoto RGB color space, and save it in ProPhoto RGB, and then open up the image in Firefox, the image looks dull. Essentially, RGB values have been 'desaturated' because the ProPhoto RGB color profile itself 're-saturates' those dull RGB values... this is what allows it to have such a wide gamut (also why an image that is *not* ProPhoto RGB looks super-saturated if you *assign* the ProPhoto RGB profile to it).
The more important question to ask is: When converting from sRGB to ProPhoto RGB using relative colorimetric, do *pure* *primary* color values change? SHOULD they?
I have some very strange results regarding this, that I will post in a separate post (will come back to this forum and post the link).
Finally, Andrew, when I take pure blue (0,0,255) in the ProPhoto RGB color space and convert it to sRGB, the RGB values stay the same (0,0,255), yet the color on my screen changes (in Photoshop) when I assign *your calibrated profile* (that I downloaded) in OS X -- OR -- when I assign *my Eye-One Display 2 calibrated profile*. The color change is best described as blue going to bluish-purple/violet. I DO NOT see this color change when I have the canned Apple 'Color LCD' profile applied.
There is something really scary going on here.
Let me post my results regarding the changing of RGB values when converting between color spaces... it is really worrisome.