Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13889 - Deluge, stuck in an infinite loop when started up
Attached to Project:
Arch Linux
Opened by Martin Peres (MuPuF) - Friday, 20 March 2009, 19:28 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 21 March 2009, 21:51 GMT
Opened by Martin Peres (MuPuF) - Friday, 20 March 2009, 19:28 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 21 March 2009, 21:51 GMT
|
DetailsDescription:
The last update of deluge seems to be broken. I don't know if the problem is mainstream or if it is because of the packaging but when I'm starting it up, it seems to be stuck in an infinite loop. What I tried : - Re-install - mv ~/.config/deluge ~/.config/deluge2 Both have been unsuccessful. I searched the internet but I seem to be the only one to have this problem. Does anyone has an idea ? Additional info: * package version(s) : 1.1.5 Steps to reproduce: # pacman -S deluge $ deluge 1.1.5 |
This task depends upon
maybe can provide more info? for example, do a "ps axl" and see the status, o better do a strace -p pid-of-deluge and deluged
under gnome, xfce4, kde, fluxbox, etc?
I'm using gnome.
$ ps axl|grep deluge
0 1000 32037 32008 20 0 40740 22224 - R+ pts/1 0:11 /usr/bin/python /usr/bin/deluge
strace deluge :
setsockopt(7, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(7, {sa_family=AF_INET, sin_port=htons(48907), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address)
close(8) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 8
setsockopt(8, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(8, {sa_family=AF_INET, sin_port=htons(53635), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address)
close(7) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 7
setsockopt(7, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(7, {sa_family=AF_INET, sin_port=htons(61176), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address)
close(8) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 8
setsockopt(8, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(8, {sa_family=AF_INET, sin_port=htons(57293), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address)
close(7) = 0
It goes on and on with the same errors but with different ports.
I haven't any deluged proccess.
I checked, I have a lot of ports available to bind, so, I don't know where the problem is.
In fact, I have no loopback :s It is a bit strange, but when I do : sudo ifconfig lo up, everything works fine.
Do you have any idea why I don't have it anymore (I used to, I'm sure it was working).
Just for information, I use the testing repository.