I have been using Freehoo for almost a year and it used to stay logged on indefinitely. For the past few weeks, I have noticed that it disconnects after just a few minutes of inactivity (but stays connected if I am actively chatting). The program exits (automatically) with the message: The server closed the socket The actual disconnection seems to occur a few minutes before the program actually exits with the above message. I am running freehoo-3.5.3-5.20100314cvs under Fedora 12. Any ideas on what might have changed to cause this? Note my Internet connection is otherwise quite stable. Thanks
Hmm, I haven't experienced it. I'll log in on a Fedora 14 box though (normally use it on CentOS) and see if I can reproduce. You might try posting to the freehoo mailing list as well.
The freehoo mailing list I saw hasn't been active in more than a year - is there anyone upstream whom I could email to report this (I posted a bug report on the freehoo site but haven't heard from anyone and in fact the bug reporting doesn't seem to be used much either given that mine was the only bug reported) Have you been able to verify the behavior I reported? Thanks
Unfortunately, I've been unable to reproduce. I'm on the freehoo list -- did you post? Don't recall seeing it. The libyahoo2 list is probably a bit more active and has some folks who might be aware if there are issues going on with a subset of Yahoo servers. Have you been able to reproduce this on multiple machines? Any particular steps needed? I've tried on both EL5 and F14 and don't have problems...
I tried on both F12 and F14 on 2 different computers on my home network. My internet connection is rock stable and indeed the original Messenger itself stays logged in forever so it seems to be something particular to freehoo/libyahoo2. Is there any way to manually set/change the server? Alternatively is there any way to issue an automatic, regular "stayalive" command since the connection doesn't connect as long as I am actively messaging.
Ooops typo - make that "the connection doesn't automatically *disconnect* as long as I am actively messaging"
(In reply to comment #4) > I tried on both F12 and F14 on 2 different computers on my home network. My > internet connection is rock stable and indeed the original Messenger itself > stays logged in forever so it seems to be something particular to > freehoo/libyahoo2. > > Is there any way to manually set/change the server? > Alternatively is there any way to issue an automatic, regular "stayalive" > command since the connection doesn't connect as long as I am actively > messaging. Not that I'm aware of. Probably better questions for the freehoo or libyahoo2 mailing lists in any case. Don't mean to come off as disinterested --- however I am unable to reproduce this and I'm not a programmer, nor *tremendously* familiar with the internals of freehoo. I typically bring these things up with the developers directly. Actually, I'll do that now since I haven't seen you post on the list yet. We'll see if anyone has any thoughts.
FYI: http://sourceforge.net/mailarchive/message.php?msg_id=27486538 Also posted to the freehoo list, but its archives are broken unfortunately.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping