Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When webtorrent starts as a magnet-link handler, torrent is downloaded into /tmp/webtorrent/ #606

Closed
J08nY opened this issue May 30, 2016 · 2 comments
Assignees
Labels
Milestone

Comments

@J08nY
Copy link

J08nY commented May 30, 2016

What version of WebTorrent Desktop? (See the 'About WebTorrent' menu)
Version 0.5.1 (0.93.4)

What operating system and version?
Linux Armitage 4.5.0-kali1-amd64 #1 SMP Debian 4.5.3-2kali1 (2016-05-09) x86_64 GNU/Linux
kali-rolling

What did you do?
Added a torrent from a magnet link opened in firefox.

What did you expect to happen?
The torrent to be downloaded to /home/$user/Downloads/ as usual.

What actually happened?
The torrent started downloading into /tmp/webtorrent/?info-hash?/

This only happens to the first torrent(the one from the magnet link that started webtorrent). I think this is undefined behavior. Other torrents added after webtorrent starts/after manually starting webtorrent, are correctly downloaded into /home/$user/Downloads.

Is there any config/a way to set the default torrent directory in webtorrent-desktop on linux? It would be really great to have some preferences to change in webtorrent-desktop. (Default download directory, up/down speed limits, ...)

@feross
Copy link
Member

feross commented Jun 1, 2016

If you update to the latest version of WebTorrent Desktop (0.6.1) you'll get a preferences menu that let's you set the download folder.

As for the bug you're reporting, I've seen that happen occasionally. Looking into it now.

@feross feross added the bug label Jun 1, 2016
@feross feross self-assigned this Jun 1, 2016
@feross
Copy link
Member

feross commented Jun 1, 2016

PR #613

@feross feross modified the milestone: v0.7.0 Jun 1, 2016
@feross feross closed this as completed in f7acdff Jun 2, 2016
@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants