I figured out that this is somehow related to IPv6 support which was "fixed to work" in 1.6.1.1-4... I guess disabling corresponding patch will help. I found many similar reports in Google in other distributions so it looks to be the upstream bug.

Maybe you can do this way: disable IPv6 in saying 1.6.1.1-5 and turn it on back when there will be fixed upstream version?

Thanks,
Andriy



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to