This was fixed when I upgraded to Natty Natwhal.
At the time I investegated a little more and found I could resolve the problem by reverting a networking configuration change that I had added to work around a previous bug.
It was strange (and annoying at the time) that the non-standard configuration broke with the update, but it was probably not a kernel bug.
This was fixed when I upgraded to Natty Natwhal.
At the time I investegated a little more and found I could resolve the problem by reverting a networking configuration change that I had added to work around a previous bug.
It was strange (and annoying at the time) that the non-standard configuration broke with the update, but it was probably not a kernel bug.