Leopard upgrade experience

I just upgraded my MacBook Pro laptop to Leopard (aka OS X 10.5). Here are my experiences so far:
  • I ran a full backup first (doesn't everyone?), then performed the default upgrade procedure.
  • On first Leopard boot, Spotlight started re-indexing both my startup drive, and my backup (external FireWire) drive, even though I had previously disabled Spotlight on the external volume. I had to disable it again. I then unmounted the external drive. Spotlight continued to index my internal drive, but starting reporting something ridiculous like -5234923 hours to go. Sure enough, next morning it had still not completed (it said 28% done by then - this is on a 120GB disk with 100GB used). I rebooted, and Spotlight finished indexing in about 10 minutes.
  • My login keychain was messed up. Apparently it didn't like that my keychain had the name of my userid; it insisted on using the keychain named "login", which was empty. Running Keychain First Aid (under the Keychain Access menu) solved the problem, migrating all my keychain data over.
  • 1passwd didn't work initially. Turns out I had an older version installed. When I upgraded to 2.5.0, it started working again. Others are apparently still having problems, see here.
  • X11 is now installed by default. It noticed I had a custom ~/.xinitrc file and warned me about it, asking me what to do (I said to leave it alone). But there are problems. There is now an X11.app in /usr/X11/. The Tiger version was in /Applications/Utilities/, and remained there after the upgrade. There also seems to be some detritus left over in /usr: in addition to the directories /usr/X11/ and /usr/X11R6/ (a symlink to /usr/X11/), there is also a /usr/X11R6 1/, which contains its own include, lib & man subdirs.
    When launching X11, I now wind up with _two_ X11 icons in my Dock. One of them blinks for a long time, then shows "Application Not Responding" when ctrl-clicking the dock icon; it can't be killed (though it goes away when I quit the original X11).
    Plus there are two other mysteries: it takes two clicks of the dock icon to switch to an X11 window (and Cmd-Tab to X11 doesn't do the right thing either). Worst of all, three button mouse emulation doesn't work correctly. In Tiger, option-click emulated middle-click and Cmd-click emulated right-click. Now, option-click emulates right-click, and Cmd-click emulates Meta-middle-click. There seems to be no way to emulate a simple middle-click. Since that's how you paste in X11, this is a real problem. This works fine with a real mouse.
  • Mail Act-On & MailTags plugins are both incompatible with Leopard. Actually, Mail Act-On can be re-enabled, look here for details.
  • The Cisco VPN client we use to login to Sun's network works fine under Leopard. This is the first time a major OS X upgrade has not also required a new VPN client. I have heard there are conflicts with the "Back to My Mac" functionality of .Mac, so I went ahead and disabled it as a precaution.
  • Mail.app no longer breaks long URLs for other mail clients by adding gratuitous spaces. Hallelujah!!
  • iCal now has a preference to set an alarm on new appointments by default. No more need for third party solutions like iCalFix.
  • Quicksilver (web page currently not responding) always displays its icon in the dock, even if I tell it not to. Also, the two items it puts into the system-wide Services menu disappeared for quite some time (including through a couple reboots and rerunning of the Quicksilver setup), but they eventually returned.

    UPDATE 1: An new version of quicksilver which addresses the dock icon issue can be found here.

  • Spaces is great. I was tired of VirtueDesktop's memory leaks & crashing. I just wish it allowed more hotkey options for activating its multi-desktop view (one non-obvious tip: you can set a corner to activate Spaces, but you do it from the Exposé Pref. pane). I also wish I could name the spaces (at least for the menubar pull-down).
  • I haven't played with Time Machine; it looks to be useless for me (and perhaps most laptop users), as it requires a second drive to be attached at all times.
  • UPDATE 2: I can now with confidence state that the AirPort connection/stall problems plaguing me since upgrading to 10.4.10 are completely resolved in Leopard!! This has been a long, frustrating problem for many laptop users since 10.4.10 came out. Although I'm annoyed at Apple for how long they let this drag on, I'm glad it's over for me, and hope they release a fix for those 10.4.10 users not planning to upgrade.
    One interesting change: now when I press the AirPort menubar icon (which is what used to be needed to get the AirPort connection to start up again with this problem in 10.4.10), instead of a delay before anything happens, the menu drops down immediately, with the top line initially saying: "AirPort: Scanning..." for a second or two (in a greyed-out font), before switching to "AirPort: On".
  • UPDATE 3: Salling Clicker stopped working for me; it said Bluetooth wasn't available. There is a preliminary 3.5.1 update available which solved the problem for me.

Time Machine doesn't require an external drive all the time; it will catch up when you "dock".

These are useful tips. Thanks. See also my experiences at http://geoffarnold.com/?p=1771

One thing I found the hard way: unplug all external drives before doing the upgrade!

Posted by Geoff Arnold on October 27, 2007 at 08:11 PM EDT #

Thanks for that clarification Geoff. Still, I presume it's not as robust as the hourly snapshots Time Machine takes when the external drive is attached.

Luckily, I did not have the AirPort problems you encountered; as mentioned above in my latest update, I've been suffering with AirPort issues since upgrading to 10.4.10. Now that it's working fine again, I am actually hesitant to install the recently posted login & keychain update until I hear from folks who had suffered with the 10.4.10 issues that this update does not cause problems for them.

I will continue to post updates to this entry as I learn new things.

Posted by Eric Sharakan on October 28, 2007 at 07:43 AM EDT #

Support for Leopard is much better now in 1Password 2.5.2. We had performed all our testing with the developer previews of Leopard, but the final retail version of Leopard changed quite a bit which caused a few hiccups.

If you have any problems like disappearing buttons in Safari or missing support in OmniWeb, give 2.5.2 a try.

So far we have had 3 releases in one week. Leopard is keeping us on our toes!

Dave Teare
Co-author of 1Password

Posted by David A Teare on October 29, 2007 at 04:23 AM EDT #

Thanks for the note David! Although I had gotten things working under 2.5, I went ahead & updated to 2.5.2. Lots of developers seem to be scrambling; it wasn't nice of Apple not to give you guys an advanced copy of the final retail version.

One thing that tripped me up was the switch to the new keychain. Even tough I went through the dialog box when upgrading to 2.5, that was in the throes of getting Leopard up & running, so I missed the minor detail of the keychain name change. I only figured this out today when I noticed I had both 1passwd and 1password keychains, started scratching my head, and went back to your website for details.

It turns out I had manually put some of my own private keys (for signing email) into the 1passwd keychain, which were not migrated over. I'm glad I closely compared the two keychains before doing anything drastic. Is there a supported way of adding things like private keys to the 1password keychain?

Also, for some reason, two of my private keys show up in 1passwd in the Trash folder. My other keys don't show up in 1passwd at all.

Posted by Eric Sharakan on October 29, 2007 at 06:49 AM EDT #

Don't you think it's a little weird how Apple threw in a space in the path

/usr/X11R6 1/

MacPorts now barfs when I install something that needs X11.

Posted by guest on October 29, 2007 at 02:34 PM EDT #

I assume this is the result of a similar mechanism that comes into play if you accidentally download the same file from Safari twice: the second copy gets a "-1" appended to its name. Why in this case did it get a " 1" instead of a "-1"? Who knows...

I think I'm going to try to remove all remnants of X11 & reinstall it from the Leopard DVD tonight. I'll report my findings here.

Posted by Eric Sharakan on October 30, 2007 at 10:00 AM EDT #

I did this with xmodmap to make x11 happy emulating 3 buttons. The issue is if Meta_L is part of Mod2 that wins over emulate 3 buttons.

clear Mod2
keycode 71 = Meta_R
add Mod2 = Meta_R

Posted by Derrick on October 31, 2007 at 01:32 AM EDT #

has anyone found the solution for the option-click no longer working for X11 pasting? I am using a laptop with no external mouse.

Posted by mara on November 05, 2007 at 01:47 AM EST #

Mara, there is an updated version of the Xquartz server that solves this (and several other) nagging problems with the one Apple shipped in Leopard. Look here:


Posted by Eric Sharakan on November 05, 2007 at 01:37 PM EST #

Post a Comment:
Comments are closed for this entry.

I work on the Oracle VM Server for SPARC (nee LDoms) team.

View Eric Sharakan's profile on LinkedIn


« July 2016