Custom Query (2447 matches)
Results (412 - 414 of 2447)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2286 | Duplicate | Add "Trackers" tab to gtkui and webui. | ||
Description |
I really enjoy using deluge gtkui at home and the webui on my server. But since deluge supports multiple trackers now, I was thinking it would be nice if they had their own tab like in other popular bittorrent clients. Maybe have details about the tracker in said tab, like: announce status, time until next announce, seeds/peers scraped from the tracker. Perhaps move the adding/removing trackers feature from the Options tab into this new tab too. Would this be a possibility for a future release? |
|||
#2292 | Duplicate | Can't add trackers when creating torrents | ||
Description |
I use Deluge git master branch on Arch Linux Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/deluge/ui/gtkui/createtorrentdialog.py", line 439, in _on_button_add_clicked dialog.set_transient_for(self.dialog) AttributeError: 'NoneType' object has no attribute 'set_transient_for' |
|||
#2294 | Duplicate | [LINUX] "Apply to all" in add dialog moves files to user home folder instead of selection | ||
Description |
I am trying to place multiple downloads in the same folder. I will add multiple torrents to the "Add Torrents" dialog and click on a single file and then choose the destination folder. Then I press "Apply to all" to get all the other files to be placed in the same folder. Upon clicking the "Add" button Deluge will start downloading the files but all of the files (including the one that I specifically assigned to a different destination) will be placed in the users home folder instead of the selected destination folder. Expected results: The selected destination folder is applied to all torrents in the "Add Torrents" dialog and subsequently placed in the selected folder. Actual results: All of the torrents in the "Add Torrents" dialog will be placed in the users home folder (/home/[user]/) without confirmation and have to be moved manually. This problem has been with me since at least 1.3.5 |