It looks like this bug is still present in Debian 5.0. I ran into it last night and applied dmitry's fix successfully -- no need to reboot. Thank you!
It looks like this bug is still present in Debian 5.0. I ran into it last night and applied dmitry's fix successfully -- no need to reboot. Thank you!