qBittorrent
qBittorrent copied to clipboard
Displayed location in "General" tab not updated when location is changed.
qBittorrent & operating system versions
qBittorrent: 4.5.2 (64-bit) Operating system: Windows 10 Pro 22H2 (19045.2965)
What is the problem?
When downloading a torrent, if you change the location, then the "General" tab is not updated to show the new "Save Path" value. You can cause it to show the new value by selecting a different torrent and then reselecting the first one. But, if you only have one torrent in the list, I do not know a way to cause it to redraw the tab.
The issue is entirely cosmetic. The actual downloading location DOES change. It is only the data displayed "SavePath" that is not updated.
Steps to reproduce
- Start a torrent downloading. (It will default to X = whatever your default location is)
- Have the "General" tab open so you can see "Save Path: X" near the bottom.
- Right-click the torrent -> Set Location ...
- Select a new location. (Y = Someplace other than X.)
- The General tab will still say "Save Path: X". This is the issue. It should now say "Save Path: Y".
- If you have another torrent in the list, you can select it, and then go back to the original one, and it will then say "Save Path: Y", as it should.
Additional context
No response
Log(s) & preferences file(s)
And it does not seem to be dependent on preferences. I was able to repro on a first-install running in a brand new VM, without changing any preferences at all.
None of the actions to repro this bug cause any log messages to be printed.
Interesting, I am wondering why you've marked it "Can't reproduce". Does it really not happen to you? It reproduces for me in a brand new windows VM with a brand new install, and no funny business.
I am wondering why you've marked it "Can't reproduce". Does it really not happen to you?
It's updated immediately for me.
It's updated immediately for me.
Did you test it on v4.5.2?
Yep. I'm using 4.5.2. Although, to be fair, this issue has been happening for me for a very long time over many versions.
Yep. I'm using 4.5.2.
I saw it in OP. The question was to @thalieht.
Did you test it on v4.5.2?
Yes.
@rossc719g Still an issue for you in 4.6.0?
@rossc719g Still an issue for you in 4.6.0?
Actually, no! This had been an issue for me for ages, and 4.6.0 seems to have fixed it for me. Yay!