Version: 0.0.1 (using KDE 4.5.3) OS: Linux When I click on a magnet link I receive the following error message: "The requested operation could not be completed Cannot Initiate the magnet Protocol Technical Reason: Unable to Launch Process Details of the Request: URL: magnet:?xt=[Link removed] Protocol: magnet Date and Time: Monday 29 November 2010 22:39 Additional Information: Unable to create io-slave: klauncher said: Fehler beim Laden von „ktorrent '%u'“ Clicking on the same link in Firefox works. Ktorrent ist started without a problem. Reproducible: Always OS: Linux (i686) release 2.6.35-23-generic-pae Compiler: cc
Still the case with KDE 4.8.3 (Gentoo sources).
(In reply to comment #1) > Still the case with KDE 4.8.3 (Gentoo sources). Can either one of you provide a link to test this against ? The magnet kio comes with ktorrent so if it does not work, then it needs to be reported against ktorrent not konqueror.
In konqueror 4.8.4 this works fine. I had trouble with this in older versions of KDE, at least the built in browser of ktorrent's seearch plugin resulted in the same error message. It could of course be caused by some weird character in the magnet uri which isn't properly passed to ktorrent when forking ktorrent. Maybe konqeror didn't shell quote the uri parameter for ktorrent ?
Aha. I'm on KDE 4.9.1, though I've had this problem with 4.8 and probably 4.7, maybe even earlier. However, if I switch the view mode from WebKit to KHTML, then magnet links work. I hadn't thought to try that any earlier. Maybe this is a problem with WebKit, then. Maybe m.wege can confirm whether s/he is also using WebKit?
Note that the built in browser of ktorrent's search plugin also uses webkit So it looks like a webkit issue.
(In reply to comment #5) > Note that the built in browser of ktorrent's search plugin also uses webkit > > So it looks like a webkit issue. Then this should be reported upstream, webkit is an external dependency we have no inlfuenc over.
https://bugs.webkit.org/show_bug.cgi?id=97004 suggests that KDE is using Webkit improperly. Either that or someone has to provide a patch. I'm not sure which.
Might not really be a webkit issue. We need to first investigate the KIO/QNetworkAccessManager bridge to make sure it is not doing anything that prevents magnet urls from working.
https://bugs.launchpad.net/lucid-backports/+bug/801665