If "Human" icons are selected, likely in the case of someone upgrading, the NetworkManager Applet will have an ugly black icon representing an ethernet connection. Note that the new 9.10 theme is called "Humanity" which uses a much nicer and smaller connection icon. To use the latter in the place of the former:

Canonical have taken all of the fun out of gdmsetup, reducing it to just two options. All other customisation aside, I can't stand the "Face Browser" at the login screen. At least there's still a way to get rid if that:

The gnome-settings-daemon doesn't appear to be at all tested with remote logins. Currently there's another new bug, in a long line of bugs, that causes the daemon to crash when using the desktop remotely. This has been fixed, but the fix is currently sitting in the "proposed" queue. The solution in the meantime is to disable the xrandr plugin by running gconf-editor and unchecking the following:

It appears that Firefox 3.5 doesn't respect the font rendering set by the user in their system wide settings. I was really annoyed by this, and as a result managed to gather together the following information. This problem will only annoy those people who have selected settings that differ from those already set in the file respected by Firefox. This file is "/~.fonts.conf". My copy of this file had four settings within it: rgba, hinting, hintstyle and antialias. The settings hinting and antialias are boolean, whilst the other two have the following options:

My file was set to: rgba none, hinting true, hintstyle hintfull and antialias true.

Within my gnome font rendering settings I select the standard "LCD" setting. This equates to: rgba rgb, hinting true, hintstyle hintslight and antialias true.

The contents of /~.fonts.conf then becomes:

I just purchased Adobe CS4 Design Premium and have had trouble installing it on a fresh install of Snow Leopard (10.6.1). Whilst everything appears to be fine, the CPU would sit on 60% with every application closed. As soon as I uninstalled CS4 the CPU would drop back to 1-2%. I conducted this test twice—that is installed CS4 on a fresh Snow Leopard twice over.

To be clear this isn't resolved by restarting, as is the solution to one known bug mentioned in the CS4 Read Me.

In my desperation I made the mistake of calling tech support. The tech support guy wasn't very helpful. Even though I told him that I had re-installed both CS4 and Snow Leopard, he had me run the Adobe cleaning utility thingy and reinstall again. After three hours of reinstalling (for the third time) and another 700MB of updates (from my precious download quota) I was exactly back to where I had started.

Then when the updates for Version Cue and Adobe Drive failed to install, it got me thinking. Looking at the box it states that Java is needed for Version Cue Server. That being a unique requirement and the update for that particular program failing, sent me on the search. I eventually found the directory containing Version Cue Server and moved it. I next planned to restart but I didn't have to, the instant I moved the directory my CPU usage plummeted from 60% to 1%.

I've been working on this for days and all I had to do was move the folder "Server" out of "/Library/Application Support/Adobe/Adobe Version Cue CS4/".

*sigh*

Recently the hard drive on which I had Vista installed began to behave erratically. But I wasn't worried as I had been using Vista's "Complete PC Backup"! What could go wrong? However, try as I might, and I tried a lot, I wasn't able to get the recovery to work. It always gave the same error message, "There are too few disks on this computer or one or more of the disks is too small."

My trouble was caused by the fact that I wanted to replace my drive. The "Complete PC Recovery" works if all you want to do is to rollback to an earlier backup. It seems that Vista's "Complete PC Backup" is not designed to help if your hard drive dies.

I cobbled together this fix after reading a thread in the Microsoft Technet Forum.

Notes:

When I fired up Vista's WMC (Windows Media Center) for the first time it defaulted to using, to what I consider to be, my secondary monitor. (Windows insists that the monitor is the primary, but is alone in that assessment as Ubuntu and the POST screens use the other monitor.) In order to switch monitors I entered into WMC's setup. Upon reaching the appropriate section, selection of another monitor fails, giving a message like "display not in use". The setup process stops there and doesn't even offer a clue as to how to fix the problem. As it turns out, the fix is quite simple.

To move WMC from one monitor to another, use the mouse to press the "unmaximise/maximise" button (the middle one on the top right) and then drag the WMC window to the other monitor, and then press the same middle button again. Note that the move is remembered the next time WMC starts.