Arch Linux

Please read this before reporting a bug:

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#26072 - [transmission-qt] does not put torrents in trash

Attached to Project: Arch Linux
Opened by Raul Castillo (Anonymo) - Monday, 19 September 2011, 20:19 GMT
Last edited by Gaetan Bisson (vesath) - Monday, 15 October 2012, 23:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture x86_64
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


There is an option to put .torrent files in trash after they have been loaded onto the program in transmission-qt. With that option selected, it does not send them to trash, just keeps them in the downloads folder. It does load the .torrent file and start downloading the files correctly, the problem is in removing the .torrent file. This feature does work in transmission-gtk.

Additional info:
* package version(s)
* config and/or log files etc.

Steps to reproduce:
Go to Edit menu > Preferences > Click Move .torrent file to the trash.
Hit close
Try to download a torrent. The .torrent file will stay in your downloads folder.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Monday, 15 October 2012, 23:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  in newer transmission-qt releases
Comment by Ionut Biru (wonder) - Monday, 19 September 2011, 20:30 GMT
please report this issue upstream to transmission
Comment by Raul Castillo (Anonymo) - Monday, 19 September 2011, 20:41 GMT
Submitted to:

Thank you for submitting a new ticket ("transmission-qt does not send .torrents to trash").
Your submission has been routed to a moderator for approval. We make every effort to review submissions within one working day.

Looks like they are saying it might be a problem with Firefox or Dolphin. Can't be Firefox, since I'm using Chromium.

KDE bug report: