Non-default configuration directory results in failed file association

Specific support for Deluge on Microsoft Windows OS
galneon
Member
Member
Posts: 21
Joined: Mon May 18, 2015 3:24 pm
OS or Distro: Win 7/8.1

Non-default configuration directory results in failed file association

Postby galneon » Mon Dec 26, 2016 5:40 pm

I've used a non-default directory for my deluge daemon box for a long time, but just now started using the -c switch with on my client box as well. This seems to work fine, until I try to load a torrent file. Opening a .torrent file through a browser or file manager simply never sends the .torrent file to the daemon. Moving the configuration data back to the default location in appdata and removing the -c switch from my deluge shortcut means file associations work once more.

The daemon's directory polling feature or the "Add torrent" dialogue in the thin client are the only ways to load torrent files when the client is using the -c switch to specify a non-default configuration folder. This, obviously, isn't optimal since I have .torrent links set to open by default in my browser.

I'm using 1.3.13 on both boxes.

Cas
Top Bloke
Top Bloke
Posts: 3382
Joined: Mon Dec 07, 2009 6:04 am
OS or Distro: Ubuntu 16.04
Location: Scotland

Re: Non-default configuration directory results in failed file association

Postby Cas » Sun Jan 08, 2017 7:32 pm

Could you create a ticket for this please

galneon
Member
Member
Posts: 21
Joined: Mon May 18, 2015 3:24 pm
OS or Distro: Win 7/8.1

Re: Non-default configuration directory results in failed file association

Postby galneon » Sun Jan 08, 2017 8:45 pm

Here you go: http://dev.deluge-torrent.org/ticket/2955#ticket

I imagine you'll change the priority from major to minor, but given how impractical this bug makes portable thinclient setups and given the fix is probably trivial, I thought I'd give it a shot. ;)


Return to “Windows OS”

Who is online

Users browsing this forum: No registered users and 9 guests