Leopard may be the sixth release of Mac OS X, but it's important to remember that it's also a dot-zero release, the first version of a major update of the operating system. There are bound to be some incompatibilities and fixes that Apple is aware of but didn't get a chance to fix before the discs had to be pressed, or that have cropped up since hundreds of thousands of people started running it.
Here's a rundown of some current important issues with Leopard.
Login and Keychain Update 1.0 -- This update [1] resolves an issue caused by using an account that was created in Mac OS X 10.1 or earlier, which used a different login authentication method. It also addresses connecting to some 802.11b/g wireless networks and changing the password of an account with FileVault enabled. The update is available via Software Update or as a 10 MB download [2].
Application Enhancer and Blue Screen After Installation -- Many people who run Unsanity's Application Enhancer utility are ending up stuck with a blue screen after performing an upgrade installation. Apple has posted an article with recommendations [3] on how to recover from the problem (though your best bet is to make sure all of your utilities are disabled before upgrading as Joe recommends in "Take Control of Upgrading to Leopard [4]," and that's especially true of system-level "haxies" like this). Unsanity claims the problem stems from people using versions of
Application Enhancer earlier than 2.0.3 [5], and that they're working on ensuring Leopard compatibility. (Most third-party developers didn't receive their final release versions of Leopard until after the retail copies shipped on Friday, which puts some of the blame for incompatibilities squarely on Apple's shoulders.)
Back to My Mac Security Warning -- Alan Oppenheimer and Open Door Networks are cautioning Leopard users to turn off the Back to My Mac feature [6] due to a security vulnerability that enables anyone with access to your .Mac account password to control your Mac remotely. Back to My Mac is located in the .Mac preference pane, and is enabled by default. [Open Door has now posted more details [7].]
They write: "The problem came in when we selected the server Mac in the client's sidebar. Instead of either connecting to that Mac's File Sharing as a guest, or asking us for that Mac's password, Back to My Mac automatically connected to the server Mac's File Sharing as that Mac's owner without ever asking for the owner's name and password. Worse yet, the same thing happened when then clicking on 'Share Screen...' giving us full remote control of the Mac without ever entering its password."
Aperture and Time Machine -- Apple is advising users of its professional photography software that the Aperture database could become inconsistent [8] if the program is running during a Time Machine backup (which occurs every hour). Apple's wording is interesting: "If you use Time Machine with Leopard, be sure to set your computer up so that Time Machine only does manual backups." Presumably this refers to being able to customize the Time Machine backup schedule, a feature Apple demonstrated but which didn't appear in the released version. Or, I could be reading it wrong and Apple just means that you manually switch Time Machine on in the Time
Machine preference pane to trigger a backup.
Speaking of Aperture, Apple has also released Aperture 1.5.6 Update [9] (a 130.6 MB download [10]), which provides Leopard compatibility and addresses issues with iPhoto, the iLife Media Browser, and recovering an Aperture Library from a Vault.
Stability Updates from Apple -- Each of the following Apple software updates provide improved stability and compatibility with Leopard (and don't mention much else): iLife Support 8.1.1 [11] (6 MB), iDVD 6.0.4 [12] (6.5 MB), GarageBand 3.0.5 [13] (14.4 MB), and Backup 3.1.2 [14] (6.3 MB).
FileMaker Pro Has Known Glitches -- FileMaker Inc. has posted an article in their knowledge base [15] on FileMaker's compatibility with Leopard. The company says FileMaker Server 9 and FileMaker Server 9 Advanced don't currently "deploy properly on Leopard," and they're working on a compatibility update. FileMaker Pro 9 and FileMaker Pro 9 Advanced "generally run on Leopard," with two known issues:
The company says it has not tested versions of FileMaker prior to FileMaker 9 under Leopard, and has no plans to update earlier versions.
We'll write more if and when other notable problems arise.
[1]: http://docs.info.apple.com/article.html?artnum=306804
[2]: http://www.apple.com/support/downloads/loginkeychainupdate10.html
[3]: http://docs.info.apple.com/article.html?artnum=306857
[4]: http://www.takecontrolbooks.com/leopard-upgrading.html?14@@!pt=TB902
[5]: http://www.unsanity.org/archives/haxies/leopard.php
[6]: http://www.isfym.com/site/blog/Entries/2007/10/27_DonÆt_go_Back_to_My_Mac.html
[7]: http://www.isfym.com/Site/Blog/Entries/2007/10/29_More_about_Back_to_My_Mac.html
[8]: http://docs.info.apple.com/article.html?artnum=306853
[9]: http://docs.info.apple.com/article.html?artnum=306387
[10]: http://www.apple.com/support/downloads/aperture156update.html
[11]: http://www.apple.com/support/downloads/ilifesupport811.html
[12]: http://www.apple.com/support/downloads/idvd604.html
[13]: http://www.apple.com/support/downloads/garageband305.html
[14]: http://www.apple.com/support/downloads/backup312.html
[15]: http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/enduser/std_adp.php?p_faqid=6649