FS#53895 - [transmission-qt] Magnet links from apps are not auto-populated in pop-up

Attached to Project: Arch Linux
Opened by John-Michael Mulesa (jm2) - Monday, 01 May 2017, 02:35 GMT
Last edited by Florian Pritz (bluewind) - Thursday, 25 May 2017, 08:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: For the past several days (since the openssl 1.1 rebuild I believe), Transmission-qt has been failing to auto-populate the magnet link popup when you click a magnet link from other apps, such as a web browser.


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


Steps to reproduce:
1. Click magnet link in Chrome.
2. Observe Transmission opening a pop-up with a blank source field.
This task depends upon

Closed by  Florian Pritz (bluewind)
Thursday, 25 May 2017, 08:36 GMT
Reason for closing:  Upstream
Comment by Florian Pritz (bluewind) - Saturday, 13 May 2017, 16:31 GMT
This appears to work fine for me. Can you try running the following command and check if the download is added?

transmission-qt 'magnet:?xt=urn:btih:fe4b1cb178e17567d6c3d4d6d8cf3362958a3933&dn=archlinux-2017.05.01-x86_64.iso&tr=udp://tracker.archlinux.org:6969&tr=http://tracker.archlinux.org:6969/announce'
Comment by John-Michael Mulesa (jm2) - Thursday, 18 May 2017, 03:04 GMT
Via the cli appears to work; maybe it's a problem with the new GNOME.
Comment by Florian Pritz (bluewind) - Thursday, 18 May 2017, 08:22 GMT
Do you have any other environment you could try, like KDE, XFCE or some standalone window manager? Maybe also try another browser or try calling xdg-open with the URL as an argument.
Comment by John-Michael Mulesa (jm2) - Friday, 19 May 2017, 00:11 GMT
I did a bit more testing last night. Calling xdg-open directly with the URL resulted in the bad behavior. I initially thought it may be a bug in the latest version of xdg-utils, but downgrading to a version I'm pretty sure used to be good still had the bad behavior. I haven't tried changing DE's yet, so it may be a bad interaction between xdg-open and the latest GNOME.
Comment by John-Michael Mulesa (jm2) - Friday, 19 May 2017, 00:11 GMT
I'll try another DE and report back.
Comment by John-Michael Mulesa (jm2) - Friday, 19 May 2017, 23:56 GMT
I just tried on MATE, same behavior.
Comment by Florian Pritz (bluewind) - Sunday, 21 May 2017, 09:14 GMT
Alright. The last idea I have for now is that xdg-open doesn't get the URL as an argument when it's run by the browser. Personally, I don't use xdg-utils so I don't know too much about its features. After a bit of googling, it doesn't look like it has any kind of debugging support. You could try running the browser with `strace -fe process $browser` and see what happens when it tries to start xdg-open/transmission. Maybe pipe the output to a file so it's easier to search.

Also, did you try another browser yet or have you run all tests in chromium?
Comment by John-Michael Mulesa (jm2) - Sunday, 21 May 2017, 19:33 GMT
So, I think the problem is with xdg-open itself. If I pass the magnet link to xdg-open directly on the CLI, I see the same behavior.
Comment by John-Michael Mulesa (jm2) - Sunday, 21 May 2017, 19:35 GMT
FWIW Firefox doesn't exhibit the issue.
Comment by John-Michael Mulesa (jm2) - Thursday, 25 May 2017, 00:39 GMT
Ok, further debugging has narrowed this issue down to xdg-open calling 'gio open' (part of glib2) on MATE/GNOME which is failing to pass the URL. Since this definitely isn't a transmission bug, I'm closing this issue.
Comment by Florian Pritz (bluewind) - Thursday, 25 May 2017, 08:35 GMT
Good to know. You'll probably want to talk to either xdg-utils or glib2 devs about fixing this.

Loading...