Upgrading to Hardy Heron
I have upgraded a couple of computers to Hardy Heron this last week. My desktop machine at work (Dell 620) went nearly flawlessly. The only hitch was weird screen resolution on one of my two monitors. That was fixed with a manual edit of my xorg.conf file.
Things didn't go quite so smoothly on my home machine (HP 1483w). The Nvidia video was fubarred, I unistalled and reinstalled the proprietary drivers, and finally got over the hump by running the nvidia-glx-new package (version 169.12+2.6.24.12-16.34) AND the nvidia-settings package. That provided me with a tool that I could use to notify my system that I had a widescreen 19" monitor. Once I did that, I finally obtained 1440x920 resolution.
More weirdness: Open Office didn't like the Java that was installed. Uninstalling/reinstalling the Java didn't help. I finally removed OO through Synaptics and downloaded the install straight from Sun. Even then I had to point it to the JRE.
Finally, I had a hard time getting VMWare back in business. It didn't survive the upgrade, and when I went to reinstall, I got compile errors.
Then I found this forum. I untarred the update (located here) and ran the script that came with it. VMWare was back!
However, my brother still has compile errors on his system (not sure what it is). He's going to wait until VMWare releases a version specifically for Hardy.
Another bit of strangeness: My second hard drive had exactly the same files on it as the first! This was resolved by editing /etc/fstab and changing it from /dev/hda to /dev/sdb1. Strange, but easy to spot and fix. Note: I was informed of a better solution, using the actual UUID of the drive. Now, its wandering is a thing of the past. Typical fstab listing: UUID=f13f7091-63a3-4d4e-b4b7-a8e7945f683f /home ext3 nodev,nosuid 0 2