This problem is now fixed on my machine (when I removed the workaround specified above). I now have version 2.4.9-2 of the package but I am not 100% sure whether it was fixed by the new version of this particular package or something else.
Thus, you can close the bug. Thanks, Martin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
