In package linux-image-3.2.0-2-amd64, version 3.2.18-1, the bug seems to be fixed. Sorry for not being able to check for it for so long a time. Grigor