Ok I tried "sudo fuser -v 58846/tcp," and nothing came up. I just don't think that's really the problem, because I didn't change anything that would have to do with a new program running on such a weird port... deluge just stopped opening all of a sudden :( What's a pickled file, and is th...

Um ok, I didn't have a core.conf file in /home/qwerty/.config/deluge, so I made one and specified a different port, and it didn't work, deluge didn't seem to notice the file I created. I uninstalled 1.1.1, and installed version 0.5.9.3-1 from synaptic, and that works, but it's old :( So what could b...

Deluge won't start, so how would I get into preferences?

I've tried that but it says "no process killed"

Could it have something to do with "[INFO ] 16:49:31 core:104 Daemon already running or port not available.."?

qwerty@Jerb:~$ deluged -d -L debug [INFO ] 16:49:30 daemon:36 Deluge daemon 1.1.0 [DEBUG ] 16:49:30 daemon:37 options: {'loglevel': 'debug', 'quiet': False, 'logfile': None, 'config': None, 'port': None, 'pidfile': None, 'donot': True} [DEBUG ] 16:49:30 daemon:38 args: [] [DEBUG ] 16:49:31 core:79 ...

I've been using deluge 1.10 for about a week now after installing the Ubuntu package for 32 bit from this site. All of a sudden, when I try to start deluge, system monitor shows it using up about 20-25% of my processor forever, and nothing ever happens. After doing some reading on this site and look...