To extend the arguments here, the only *supported* platform is Windows then.

The code base for linux is a source-only release. All the "installers" on the download page are from external groups who have re-packaged the source for their respective native platform(s).

Has anyone tried to install 1.3.0 yet? I removed 1.2.3 and updated to the latest version but can't get it to work correctly. :( The first problem was that the .egg files in "deluge/plugins" wasn't created after python setup.py install. I tried to create them myself and then move the .egg'...

A tiny issue with both v. 1.2.1 and 1.2.3 that I noticed is that the download of a torrent often stops at 99.97% or something close to that and won't finish until a restart of deluge. Anyone else have that problem? I've had that problem once or twice, but not consistently. Sometimes a "Force R...

@fancyclown - your error has nothing to do with the hicolor theme. The "can't find hicolor icon" error is innocuous, and Deluge will run in spite of it if properly configured. The pertinent part of your error is Fatal Python error: Interpreter not initialized (version mismatch?) which typi...

Your path does not include /opt/local/bin in precedence before /usr/bin, therefore you are running OSX gcc instead of MacPorts gcc.

export PATH=/opt/local/bin:$PATH

should fix your problem.

Allright, I followed xml's instructions and had the same problem as Gravey did in my old thread. sudo install_name_tool -change /System/Library/Frameworks/Python.framework/Versions/2.6/Python /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Python /opt/local/lib/libboost_python-mt.dylib f...

"mkvirtualenv deluge" isn't working for me. There doesn't seem to be any such executable even after easy_install'ing it. That generally means the executable is not in your path. Check to make sure "echo $PATH" contains /opt/local/Library/Frameworks/Python.framework/Versions/2.6/...

I got nothin' then. Sorry. I haven't used this method to install yet.

It *looks* to me like a 32/64 bitness issue. Like you're running 64-bit Snow kernel and the py26 compile is trying for i386 (32-bit) mode. What's the output of "uname -a" (from a terminal prompt) look like? If it ends in x86_64, try rebooting and holding down the "3" and "2&...

have you done a "workon deluge"?