I've been using Deluge for several weeks without a hitch, I'd even set Firefox to auto-open deluge when downloading torrent files. Yesterday, I tried to download a torrent and it did nothing. I pondered it, downloaded it again, still no deluge. Then I launch it from the Applications -> Internet -> Deluge and nothing happens.
I then reinstall it, still nothing. Then I launch it from commandline and this is what I get:
jerome@jerome-desktop:~$ deluge
no existing Deluge session
deluge_core; using libtorrent 0.11.0.0. Compiled with NDEBUG value: 1
Applying preferences
Torrent Size 891118714.0
Available Space 12496855040
Raising error:
deluge_core; using libtorrent 0.11.0.0. Compiled with NDEBUG value: 1
terminate called after throwing an instance of 'boost::filesystem::filesystem_error'
what(): boost::filesystem::default_name_check: default name check already set
Aborted (core dumped)
Anyone know how to fix this? I've had to go back to Azureus and that's no fun.
I am a newbie to Linux. After building and installing deluge 0.5.1.1, everything alright. However, when I type "deluge" to start deluge, it appears:-
Traceback (most recent call last):
File "/usr/bin/deluge", line 85, in <module>
bus = dbus.SessionBus()
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 669, in __new__
mainloop=mainloop)
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 293, in __new__
mainloop=mainloop)
dbus.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Could you please tell me how I could solve the problem? Thank you very much.
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG value: 1
terminate called after throwing an instance of 'std::length_error'
what(): basic_string::_S_create
Aborted
I have the same problem, but I have libtorrent-0.11.4 and, deluge show me the 0.13.0.0
flipe wrote:no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG value: 1
terminate called after throwing an instance of 'std::length_error'
what(): basic_string::_S_create
Aborted
I have the same problem, but I have libtorrent-0.11.4 and, deluge show me the 0.13.0.0
what I can do to solve this?
thanks!
that's not at all the same problem...and deluge uses its own libtorrent, not what you have on your system. see if removing ~/.config/deluge and rerunning it works for you. make sure you dont have any other bittorrent clients open, either.
Traceback (most recent call last):
File "/usr/bin/deluge", line 85, in <module>
bus = dbus.SessionBus()
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 669, in __new__
mainloop=mainloop)
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 293, in __new__
mainloop=mainloop)
dbus.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
it happened it 0.5. Removing ~/.config/deluge did not solve the problem. Removed deluge-torrent and installed the 5.2 .deb package - same error.
Traceback (most recent call last):
File "/usr/bin/deluge", line 85, in <module>
bus = dbus.SessionBus()
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 669, in __new__
mainloop=mainloop)
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 293, in __new__
mainloop=mainloop)
dbus.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
it happened it 0.5. Removing ~/.config/deluge did not solve the problem. Removed deluge-torrent and installed the 5.2 .deb package - same error.