Aperture 2: There was a problem connecting to .Mac

I took me less than 10 seconds to find a major bug Apple - Aperture 2.

That's a new record!

If you have a .Mac record in your keychain Aperture tries to connect to it -- even if the account is long defunct.

When that happens it displays an alert "There was a problem connecting to .Mac". You can't get the alert to go away, in fact I now have multiple floating dialogs telling me of this problem.

I'm going to try pulling my network cable next time I restart.

They ought to be ashamed, but as far as I can tell Apple is shameless.

Update: I quit, pulled the network cable, and restarted. It hung on start but after a minute or so something timed out and it did run correctly. I then restarted with the network cable and got the looping error message. I'll probably have to locate the .mac entry in my keychain and remove it.

Update 2/13/08: The fix for now is to open the .Mac preferences in your System Preferences. Remove your old username and password for the inactive account. The bug goes away.

Google now supporting Safari?

I've been pretty fed up with Firefox flakiness lately, so I took Safari 3 for a visit to Google's properties.

Gmail RTF was supported. Google Docs no longer warns of an unsupported browser.

Blogger doesn't seem as messed up when using Safari (though it uses div tags instead of the familial p tags).

The only app that warns of an unsupported browser is Google Page Creator -- which is due to be dumped "any time now".

Google is very close to full Safari support, I'm going to try switching for a while. 

I'll be happy to leave Firefox 2/Mac behind. It ain't so great on XP either these days! We need Firefox 3 ASAP.

The worst commercial web site on the net?

The Lowe Alpine web page won't render correctly in either Safari 3 or Firefox 2.

I've never seen that before.

There's a contact link, but it's broken.

I think we've got a winner.

Blackberry Pearl voice memo hack

Emily's Pearl can record -- but only for a costly "media message". Otherwise, you can't record a voice memo.

Happily, there's a workaround. Create an SMS, but save it as draft. Access it via the messages application. Click the link for more details.

My iMac screen - dark band at the top of the display

Bad news! My July 2005 20" iMac now has a dark irregular band across the top of the display - thickest on the right side. It's most conspicuous against the login screen, or the blue background used on startup:



Superficially it looks like dirt on the display, but it's inside. I suspect some sort of LCD delamination or glue defect, perhaps related to the all the heat problems the G5 iMacs were known for. At 2.5 years this machine is out of warranty -- including my credit card extended warranty.

I can't find much about this on the net, so it's probably bad luck. We have a good Apple repair facility in Minneapolis (first Tech), I could try hauling the machine out there if I get the energy.

Update: Sounds like this.

Update 6/17/11: Three years later the band is about twice as wide. This is a kid and movie machine now, and we don't notice it much.

iPhoto 7.1.2 doesn't fix video export bug

iPhoto 7.1.2 was released tonight.

I checked to see if Apple had fixed the movie export bug.

Nope.

If you export a Movie (video) as "Current" iPhoto exports a thumbnail JPEG with an .AVI extension.

Nasty bug, in some circumstances it may result in the permanent loss of important memories.

Update 3/1/2008: It's not fixed in 7.1.3 either. I finally got fed up and filed a real Apple developer bug report:

5775826 iPhoto: default video export produces defective file 100% of the time.

Update 3/4/08: My bug was flagged as duplicate of Bug ID# 5613626. So at least it's known and documented as a bug that's being currently worked on.

Update 5/19/09: iLife '09 still has the same bloody bug!! See also a thread on this bug. Apple's refusal to fix such egregious data destroying bugs smells of Kafka.

Update 7/12/09: No fix. It occurs to me that this bug is a good HR test. Describe the nature and origin of the behavior to the candidate. Explain that the app is behaving "correctly". It's exporting the file that lives in the "current" folder. Ask them what priority they give to changing this behavior. If they say something like "That's crazy. It needs to be fixed immediately." hire them. If they say "it's working correctly" run like the wind.

Bike light breakthrough? The Ixon IQ.

I used to be a real rider. One day I hope I'll be back, maybe sooner than later.

From those days I have an old NiteRider light. It cost a fortune in 1999 and came with a massive NiMH battery that's now toast. Of course it used a proprietary connector (data lock isn't really a new idea) so I'd have to buy a replacement from NiteRider -- if one exists.

So I paid attention to the bike light that saved the world, a post introducing the German IXON IQ LED light. This excellent description tells us it uses conventional or rechargeable AA batteries -- no more "battery lock" issues. The imported device (German plugs) is about $100 US - a bargain for a serious bicycle light.

... Full power setting (14 40 [see comments!] lux) gives a 6 hour run time. Low power gives about 13 hours. Run times are for fully charged NiMH batteries. Full power is adequate as a standalone headlight for most cyclists in most situations up to about 20mph. Two Ixons at full power should be more than enough for any situation except perhaps a very fast downhill, say well over 25mph. Low power is more than adequate for low speed riding, up to perhaps 10 mph on dark roads or bike paths. For urban cycling with overhead street lights, the low power setting is perfect. These are my estimates based on my own experience using this light. Everyone's night vision is different!....

Note that NiMH battery power output drops precipitously in cold weather, these numbers don't apply to MN winters. Front wheel dynamo systems weren't big when I was in the market, but I suspect they're the answer for a MN winter rider.