@Michael: Use the fix suggested by Donal. To do this:
1. Open System > Administration > Synaptic and click on the Search button in the toolbar. Choose "Version" from the drop-down, and search for "2.6.20-16"
2. Click on the leftmost column header in the package list to show installed packages. I see linux-headers-_, linux-headers-_-generic, linux-image-_-generic and linux-libc-dev.
3. Select each installed package in turn and choose "Package > Force Version...". Choose the most recent, non-buggy version. On gutsy this meant ".46" instead of ".47". As Brian Buchanan suggests, on feisty it would be ".32" instead of ".33".
4. Click "Apply".
You will have to turn off unattended updates (System > Administration > Software Sources > Updates tab) so that the old packages are not automatically overwritten by the buggy ones. AFAIK the only difference between, e.g. 2.6.20-16.32 and 2.6.20-16.33 is the patch causing this error, so this shouldn't be terribly insecure.
@Michael: Use the fix suggested by Donal. To do this:
1. Open System > Administration > Synaptic and click on the Search button in the toolbar. Choose "Version" from the drop-down, and search for "2.6.20-16" _-generic, linux-image- _-generic and linux-libc-dev.
2. Click on the leftmost column header in the package list to show installed packages. I see linux-headers-_, linux-headers-
3. Select each installed package in turn and choose "Package > Force Version...". Choose the most recent, non-buggy version. On gutsy this meant ".46" instead of ".47". As Brian Buchanan suggests, on feisty it would be ".32" instead of ".33".
4. Click "Apply".
You will have to turn off unattended updates (System > Administration > Software Sources > Updates tab) so that the old packages are not automatically overwritten by the buggy ones. AFAIK the only difference between, e.g. 2.6.20-16.32 and 2.6.20-16.33 is the patch causing this error, so this shouldn't be terribly insecure.