Bug? Nothing found in search after SlskQt has been idle for several hours

Hi again, I think this time I found a real BUG. In theory, it could be related to the fact that I live in a country where I am automatically disconnected from the net after 24 hours. Description: When I leave SlskQt running for QUITE awhile ( = 8 hours doing nothing, e. g. in the night), and get up in the morning and try to re-run the search (using the handy (!) context menu entry provided), there will be ** no results at all **. The "fix" is to simply disconnect from the slsk network and reconnect again. Suddenly, my search results are filled up to the brim again.
Your rating: None
No votes yet


That's a weird one. It sounds like a dead connection to the server, which I have observed at some point on my end as well, but then I'd imagine it would disconnect you as soon as you tried to send the search to the server... puzzling. I wonder if a simple periodical pinging of the server would change the situation... I'll add that to the list of things to do once I release the next build.

Thanks, Nir

Dead connection?? Sounds plausible. And nice to hear I'm not the only one who has noticed this. Yes, pinging the server from time to time would be a good idea.

Apparently it will favor the problem if you try to search after the network got auto-disconnected *during the night*. That is, if you manually auto-disconnected at 8 PM, the problem would most probably not occur the next morning because you're still on *same IP*.
Yes it might be the dynamic IP change that gets SlskQt occasionally confused.

The next build I'm going to release later today will ping the server every five minutes. Let's see if that makes any difference :)