Description of problem: I ran transmission for the first time in a while today and added a torrent, clicking the Add button took a _long_ time, as did a couple of the next operations before the torrent started. I iniitally assumed this was some weird DNS thing, but then when I went to add another torrent the same thing happened ... at which point I started an strace and got a neverending stream of: connect(59, {sa_family=AF_FILE, path="/home/james/.beagle/socket"}, 110) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 200000000}, NULL) = 0 connect(59, {sa_family=AF_FILE, path="/home/james/.beagle/socket"}, 110) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 200000000}, NULL) = 0 connect(59, {sa_family=AF_FILE, path="/home/james/.beagle/socket"}, 110) = -1 EAGAIN (Resource temporarily unavailable) ...given how much I use beagle I just did: rm ~/.beagle/socket ... at which point transmission started responding instantly. Version-Release number of selected component (if applicable): transmission.x86_64 1.33-1.fc9 installed
Pretty odd, I can't reproduce. I have the socket beagle file too, and beagle uninstalled, yet the problem doesn't occur for me. Sounds like something went haywire in your setup, like some zombie process holding to the socket ? What is the output of "sudo lsof | grep beagle" ?
Well I think I've upgraded beagle since logging this, but: % lsof | fgrep beagle | wc -l 1338 ...is that normal? You really want all of that?
James Antill, Do you still see this problem?
No, and this is on Fedora 10, but then a quick ps shows that I'm not running beagle either.
I am going to close this for now. If you find any issues, feel free to report them back.