The number of users affected by this bug appear to be few, but its annoying nonetheless. Kernel releases subsequent to 2.6.20-12 fix a host of other problems which do affect a great many people, which is why we cannot release 2.6.20-12. I also asked how to get the 2.6.20-12 kernel:
The number of users affected by this bug appear to be few, but its annoying nonetheless. Kernel releases subsequent to 2.6.20-12 fix a host of other problems which do affect a great many people, which is why we cannot release 2.6.20-12. I also asked how to get the 2.6.20-12 kernel:
"if they can manage to install, then they can download it from the "builds of" thing at the top left of https:/ /launchpad. net/ubuntu/ +source/ linux-source- 2.6.20/ 2.6.20- 12.20 - e.g. https:/ /launchpad. net/+builds/ +build/ 312897 -> Resulting binaries -> https:/ /launchpad. net/+builds/ +build/ 312897/ linux-image- 2.6.20- 12-generic -> http:// librarian. launchpad. net/6895136/ linux-image- 2.6.20- 12-generic_ 2.6.20- 12.20_i386. deb"
In summary, do this:
wget http:// librarian. launchpad. net/6895136/ linux-image- 2.6.20- 12-generic_ 2.6.20- 12.20_i386. deb 2.6.20- 12-generic_ 2.6.20- 12.20_i386. deb
sudo dpkg -i linux-image-