Opened 9 years ago

Last modified 21 months ago

#2669 new bug

file association not set with two user accounts in win7 64 bit

Reported by: Keruskerfuerst Owned by:
Priority: trivial Milestone: 2.1.1
Component: GTK UI Version: 1.3.10
Keywords: Cc:

Description

I have Windows 7 SP1 64 Bit installed. One sysadmin account and two user accounts. Only one user account has the correct file association and the other acoounts has to be corrected manually.

Change History (9)

comment:1 Changed 9 years ago by Cas

  • Milestone changed from Future to 1.3.x

The installer will set the HKCR key but I think this may be overridden by HKCU so maybe look to modifying both torrent and magnet association for this scenario.

There is a pull request related to this but I am not completely happy with the way we determine and set the keys and feel it needs some more thought.

comment:2 Changed 9 years ago by Cas

  • Component changed from Plugin to GTK-UI
  • Milestone changed from 1.3.x to 1.3.11

comment:3 Changed 9 years ago by Doadin

I think setting both to use current user would be the best solution. It makes it easy for different users to use different clients and it also eliminates any possible permissions issues.

I also think that mering https://github.com/deluge-torrent/deluge/pull/20 and possibly going further and adding a popup if the association fails would be good too.

I think the check is good to have that way if the user has a association setup already it wont break it so it can still be used till they resolve their issue but we also need a way of informing the user it failed so they know whats going on.

Last edited 9 years ago by Doadin (previous) (diff)

comment:4 Changed 9 years ago by Doadin

I made another related pull request.

https://github.com/deluge-torrent/deluge/pull/22

comment:5 Changed 9 years ago by Cas

  • Milestone changed from 1.3.11 to 2.0

comment:6 Changed 6 years ago by Cas

  • Milestone changed from 2.0 to 2.0.0

Milestone renamed

comment:7 Changed 5 years ago by Cas

  • Milestone changed from 2.0.0 to 2.1.x

Ticket retargeted after milestone closed

comment:8 Changed 2 years ago by Cas

  • Milestone changed from 2.1.x to 2.1.0

Milestone renamed

comment:9 Changed 21 months ago by Cas

  • Milestone changed from 2.1.0 to 2.1.1

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.