I went to try and downgrade that package, but it doesn't appear that I even have that package... # yum info libssl* Loaded plugins: auto-update-debuginfo, fastestmirror, langpacks, presto, refresh-packagekit Loading mirror speeds from cached hostfile * fedora: mirror.cogentco.com * fedora-debuginfo:...

I'll give that a try, finally stopped the gdb and ran the backtrace, here it is if it helps anyone figure out this problem: $ gdb --args python /usr/bin/deluged -d GNU gdb (GDB) Fedora (7.5.1-38.fc18) Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http:...

What do you mean 'stopping', is deluged crashing, if so you need a backtrace. Without any more info I suspect it might be the libcrypto bug. First attempt at creating backtrace, but in doing so, it never seemed to actually crash where I could issue the command to create the backtrace... $ gdb --arg...

Sounds similar to the problem I'm having...

What do you have in:

~/.config/deluge/deluged.log

Even on a fresh boot, where the port should be clear, it does the same thing.

And for the record there isn't anything tying up the port already: # nmap -sT -O localhost Starting Nmap 6.40 ( http://nmap.org ) at 2013-09-18 12:33 CDT Nmap scan report for localhost (127.0.0.1) Host is up (0.00040s latency). Other addresses for localhost (not scanned): 127.0.0.1 Not shown: 990 cl...

Same problem:

deluged.log - http://pastebin.com/mZJnmmpa
core.conf - http://pastebin.com/Svxb4cEm

a