#3384: Libtorrent 1.2.x support issue. ----------------------------+-------------------- Reporter: mhertz | Type: bug Status: new | Priority: minor Milestone: needs verified | Component: GTK UI Version: develop | Keywords: ----------------------------+-------------------- After libtorrent 1.2.3, then tracker announcing behavior have changed, I believe because of multi-homed support added. Anyway, deluge sometimes show a tracker under error heading, even though only lo (obviously) failed(deluge logging states 127.0.0.1) and main connection announced fine. In short from Arvid: "One listen socket failing should not make the UI suggest the other announces to the tracker failed."
More info and logs in my libtorrent ticket here: https://github.com/arvidn/libtorrent/issues/4529 I tested this in win10 VM with deluge 2.0.3 and develop branch with libtorrent RC_1_2 branch builds, 1.2.3, 1.2.4 and 1.2.5. Thanks in advance. -- Ticket URL: <https://dev.deluge-torrent.org/ticket/3384> Deluge <https://deluge-torrent.org/> Deluge Project -- You received this message because you are subscribed to the Google Groups "Deluge Dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/deluge-dev/045.52be4079eceed989b94bee003b649143%40deluge-torrent.org.
