Package: deluge-torrent
Version: 0.5.8.6-1
Severity: important
--- Please enter the report below this line. ---
I have a multiuser system and while an instance of deluge was running for another user using the
ports that I have forwarded from my router, I tried to start deluge in my account.
Deluge silently failed, and I just saw bug buddy wanting to assist me when trying to start a
download. What deluge should have done, would have been to do either of:
1) test one port after another for availability in the range it was configured to use, in the hope
it will find a free port, warn the user about the issue and start;
- if all ports' tests fail, start and warn, but don't do any uploads/downloads (like a pause all
command was given)
- as a bonus, open the preferences dialog to allow changing the used port
range
2) either vocally fail to start, explaining the reason (still, it can't be fixed since there's no
way to changes the settings without entering the GUI - except modifying by hand the pickled(?)
/home/eddy/.config/deluge/prefs.state file)
Here are the messages I see on the console:
0 [EMAIL PROTECTED] ~ $ deluge
checking for ubuntu...
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
save uploaded memory
Pickling state...
Scanning plugin dir /usr/share/deluge/plugins
Initialising plugin Scheduler
Initialising plugin NetworkGraph
Initialising plugin WebSeed
Initialising plugin WebUi
Initialising plugin NetworkHealth
Initialising plugin TorrentFiles
Initialising plugin SpeedLimiter
Initialising plugin TorrentPeers
Initialising plugin DesiredRatio
Initialising plugin MoveTorrent
Initialising plugin Search
Initialising plugin EventLogging
Initialising plugin BlocklistImport
Initialising plugin TorrentCreator
Initialising plugin TorrentNotification
Initialising plugin FlexRSS
Applying preferences
Starting DHT...
No DHT file to resume
terminate called after throwing an instance of 'asio::system_error'
what(): Address already in use
"/usr/bin/deluge": not in executable format: File format not recognized
0 [EMAIL PROTECTED] ~ $ dpkg -S /usr/bin/deluge
deluge-torrent: /usr/bin/deluge
Note that the leading "0" in the prompt I use is the return value of the last ran command (i.e. $?),
which clearly shows that deluge silently fails, giving no active indication that it, indeed failed.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.24.2-bounty
Debian Release: lenny/sid
900 testing snapshot.debian.net
900 testing security.debian.org
900 testing localhost
900 testing ftp.ro.debian.org
10 unstable ftp.ro.debian.org
--- Package information. ---
Depends (Version) | Installed
=============================================-+-================
deluge-torrent-common (= 0.5.8.6-1) | 0.5.8.6-1
libboost-date-time1.34.1 (>= 1.34.1-2.1) | 1.34.1-7
libboost-filesystem1.34.1 (>= 1.34.1-2.1) | 1.34.1-7
libboost-thread1.34.1 (>= 1.34.1-2.1) | 1.34.1-7
libc6 (>= 2.7-1) | 2.7-6
libgcc1 (>= 1:4.1.1-21) | 1:4.3.0-1
librsvg2-common | 2.22.2-2
libssl0.9.8 (>= 0.9.8f-5) | 0.9.8g-4
libstdc++6 (>= 4.2.1-4) | 4.3.0-1
notification-daemon | 0.3.7-1+b1
python (>= 2.4) | 2.4.4-6
python (<< 2.6) | 2.4.4-6
python-dbus | 0.82.4-2
python-glade2 | 2.12.1-1
python-gtk2 | 2.12.1-1
python-notify | 0.1.1-2
python-pyopenssl | 0.6-2.3
python-support (>= 0.7.1) | 0.7.7
python-xdg | 0.15-1.1
zlib1g (>= 1:1.1.4) | 1:1.2.3.3.dfsg-11
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
