Custom Query (2447 matches)
Results (157 - 159 of 2447)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3121 | Fixed | V2 beta Peer ID blocked | ||
| Description |
Deluge 2.0.0.dev7097 peer_id=-DE2000- I'm told this is the same Peer ID that Bitlord v2 used, and that's why some trackers ban it. Suggest changing ID to something uniquely Deluge. |
|||
| #3119 | Duplicate | "Open" on "Files" tab context menu locks up GTK UI | ||
| Description |
deluge-gtk under Debian 9 with XFCE and libtorrent 1.1.1.0. Selecting a torrent, visiting the "Files" tab, right clicking on either a folder or a file in the torrent and selecting "Open" from the context menu causes the Deluge window to stop responding to input or redrawing (although the "Open" action does succeed). |
|||
| #3112 | Fixed | Setting peer TOS from deluge console is different from setting Peer TOS from WebUI | ||
| Description |
Hello, Let's say I want to set Peer TOS: 0x88 I will do it 2 different ways a) & b) see examples bellow. Why the result is not the same, one is written as hex 0x88 and other is written as 136 (same decimal value as 0x88) a) webui: When I set this from Web UI and later I read core.conf I see that same value: 0x88, also deluge console reads it like 0x88 too. deluge-console 'connect 127.0.0.1:11106 myuser myuserpass; config peer_tos' peer_tos: 0x88 b) deluge-console myuser@srv:~$ deluge-console 'connect 127.0.0.1:11106 myuser myuserpass; config -s peer_tos 0x88; config peer_tos' Setting peer_tos to 136.. Configuration value successfully updated. peer_tos: 136 Is this a problem ? If not than why don't you follow same nmber base ? Kind Regards |
|||
