It would be great (and vital i might say) if we could see Tracker Messages (erros etc)

:)

Made this script to update and run deluge #!/bin/bash echo "--> sudo rm ~/deluge/* -Rfv" sudo rm ~/deluge/* -Rfv echo "--> svn update deluge" svn update deluge echo "--> cd ~/deluge/" cd deluge/ echo "--> python setup.py build" python setup.py build echo "...

Cant start Deluge svn 646 (fc6) Traceback (most recent call last): File "/usr/bin/deluge", line 41, in ? import deluge, deluge.common, deluge.interface File "/usr/lib/python2.4/site-packages/deluge/interface.py", line 34, in ? import core, common, dgtk, ipc_manager, dialogs File ...

Yes i did

i just mention it because i dont think that it is right for the app to exit when the port is "busy"

i mention it mostly as a bug and not as a problem

:)

[zeppelin@Aeolus deluge]$ deluge no existing Deluge session deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG value: 1 Applying preferences Debug 1 {} [] Debug 2 0 0 ['Network Activity Graph', 'Network Health Monitor'] terminate called after throwing an instance of 'asio::system_error' w...

Its ok now,

thank you !

can you give me the output of cat /etc/issue please? [zeppelin@Aeolus deluge-0.5.0.90.1]$ cat /etc/issue Fedora Core release 6 (Zod) Kernel \r on an \m The same error on latest svn 418 and deluge-0.5.0.90.1 Im thinking to install boost from source, do you think that there would be any difference ?

These packages are installed [zeppelin@Aeolus ~]$ sudo yum list *boost* Installed Packages boost.i386 1.33.1-13.fc7 installed boost-devel.i386 1.33.1-13.fc7 installed boost-devel-static.i386 1.33.1-13.fc7 installed boost-doc.i386 1.33.1-13.fc7 installed Didnt have the same problem earlier Thank you ...

revision 410 [zeppelin@Aeolus deluge]$ python setup.py build Attempting to detect your system information 32bit x86 system detected Linux operating system detected Libraries mt running build running build_py running build_ext building 'deluge_core' extension c++ -pthread -shared build/temp.linux-i68...

Im getting this error when i do on revision 409 [Fedora Core 6].

This is weird as i didnt have an problems i until 379