id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 1931,No warning when binding to configured listening port fails,OmegaPhil,,"If deluge is configured to bind to a listening port in a fixed range, and the bind attempt fails, a random port is chosen and no user feedback is given (although you can see there is a problem as the 'no incoming connections' warning in the status bar doesn't go away). This can happen both for a valid (another program is listening on the port) or invalid reason (deluge was restarted and the network stack still considers the previous instance to hold the port??). For the latter, see notes on SO_REUSEADDR in the two following links: http://www.microhowto.info/howto/listen_on_a_tcp_port_with_connections_in_the_time_wait_state.html http://www.wlug.org.nz/EADDRINUSE For reference, with version 0.16.0.0 of libtorrent, SO_REUSEADDR can be enabled. During testing with active torrents I can trigger the latter error trivially with restarting deluge (first discovered during developing a separate change). Without feedback, the user will trust that the listening port is honoured and assume something else is broken unless they specifically check - I originally thought this meant deluge couldn't detect my real public IP address.",bug,new,minor,2.x,GTK UI,master,,,