#4901 closed Bug (fixed)
can't add magnet links - transmission-qt.desktop issue
Reported by: | zmeYski | Owned by: | jordan |
---|---|---|---|
Priority: | Normal | Milestone: | 2.76 |
Component: | Qt Client | Version: | 2.51 |
Severity: | Normal | Keywords: | |
Cc: |
Description
Hi,
using transmission-qt 2.51 under KDE 4.8.3 I can't add magnet links from Firefox. The browser correctly suggests transmission-qt as an application to open the magnet link with but choosing it opens a new instance of transmission-qt without adding anything to it. A new instance is started even if transmission-qt was already running. The problem seems to be in transmission-qt.desktop where we have:
Exec=transmission-qt %F
should be:
Exec=transmission-qt %U
with this change things work just fine. The GTK client uses the same option %U. Also the desktop file spec mentions that %U is the correct option for programs that can handle URL's
Regards
Attachments (1)
Change History (8)
comment:1 Changed 10 years ago by gabrielcossette
comment:2 Changed 10 years ago by stuart
I've attached a patch for trunk/qt/transmission-qt.desktop in the source tree.
Summary:
--- a/qt/transmission-qt.desktop +++ b/qt/transmission-qt.desktop @@ -2,7 +2,7 @@ Name=Qtransmission Bittorrent Client GenericName=BitTorrent Client Comment=Download and share files over BitTorrent -Exec=transmission-qt %F +Exec=transmission-qt %U Icon=transmission-qt Terminal=false Type=Application
comment:3 Changed 10 years ago by jordan
Stuart you used %Q and the OP suggested %U. Which is correct?
Changed 10 years ago by stuart
comment:4 Changed 10 years ago by stuart
%U is correct. I'm not sure how that %Q typo got there, I thought I made the patch from my live fixed file.
I've edited the comment and patch accordingly.
comment:5 Changed 10 years ago by jordan
- Milestone changed from None Set to 2.80
- Status changed from new to assigned
comment:6 Changed 10 years ago by jordan
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in r13679
comment:7 Changed 10 years ago by jordan
- Milestone changed from 2.80 to 2.76
I confirm this bug is still present in version 2.73.
Thanks!