* Is this reproducible? * If so, what specific steps should we take to recreate this bug?
this happens often when wifi connecton goes away, but i can't say i can reproduce it at will. i guess it depends on how exactly connection is terminated (my guess is that it it is write that fails then it's ok, but if it happens to be in this poll, then it starts looping). description at the nabble.com link matches my symptoms exactly. and if you look at the patch it's pretty clear what's going on: reading 0 bytes only happens when connection has gone away and should be treated as an error. -- Pidgin 2.4.1 (Hardy): proper closed connection handling patch from upstream https://bugs.launchpad.net/bugs/275439 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
