Deluge Forum

I have a always on download box running Ubuntu 8.04 32-bit. Since I've updated to 1.05 the daemon crashes "all the time". First, in the middle of the night. Then, now. When it is idling. I have to kill both Deluge proesses and start them again to get Deluge running again. Is this just me?

I never had any problems with old Deluge! The old Deluge (>1.0) was really stable.

Yes I fully agree. I have been giving a try at every single new 1.X deluge release, but I just can't find anything as stable as 0.5.9.4 release. On top of that, I can't get used to the new GUI (i want my damn "clear" button back ), and I haven't yet understood the point in having a user-deamon + client mode.

Well then, having access to previous releases, being able to choose, isn't that the awesomeness of free software ?

The point of the daemon is because many users have multiple computers. Some of which might even be always on dedicated back-room computers. In an environment with more than 1 computer it makes sense to have one computer dedicated to downloading and the other just clients. For example, in my case, why would I want 5 torrent servers running when I have a computer dedicated to running daemons? Also, lets say I download things that are questionable to download in my own country I might want to run the torrent daemon in another country, but I still want a nice gui to manage them.

In the next release I think the daemon will be hidden from the user in classic mode.

the daemon should already be "invisible" in classic mode, i.e. deluge will automatically start and stop the daemon according to whether or not the GUI is running.
If the daemon is constantly crashing please enable logging: http://dev.deluge-torrent.org/wiki/Faq# ... ingenabled
So that you can then paste your crash log and we will be able to identify the source of the problem.
Personally, I've had deluge running for over a month without a single crash.
As DUser points out separating UI & core makes more sense for multiple downloaders.
The great advantage of running deluge this way means you can have "thin" clients, i.e. one machine running the daemon and multiple clients which connect to it.
Personnally, I run deluged on my server and then can connect to it from linux or windows using the GTK UI. Restarting my pc doesn't affect my downloads.
When I'm away from home (as I am now) I can connect to the daemon via the Web UI, this also means that I don't have to keep my computer on all the time (just my server which is on the time all the time anyway and uses less power than my pc). In short there are lots of advantages in running deluge as a separate UI & core and seemingly no disadvantages as you can bundle them to act as a "classic" torrent program.
I should also point out that any instabilities are probably due to 1.x being a relatively new program (as it was rewritten from scratch), not because of the new split UI/core.