mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
WebUI Some settings don't save properly #7999
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#7999
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @polo123qwe on GitHub (Oct 30, 2018).
qBittorrent version and Operating System
Arch Linux 4.19.0
qbittorrent-nox 4.1.3-2
libtorrent and Qt version
libtorrent-rasterbar 1:1.1.10-1
qt5-base 5.11.2-1
What is the problem
In the WebUI when torrent queueing or alternative rate limits are modified, the changes don't persist a restart of the process or the system
What is the expected behavior
Changes should persist a restart of the application
Steps to reproduce
Extra info(if any)
I've checked and the file qBittorrent.conf inside .config of the qbtuser is modified once the setting is changed but the file is reset after the process starts again, I've tried to make the file read-only but it gets overwritten.
Other settings do work, like changing the default port or the username/password to access the gui.
@Piccirello commented on GitHub (Dec 18, 2018):
I'm not able to reproduce this- those settings persist after restarting the application. Can you update to 4.1.4 and see if you still face the issue?
@Piccirello commented on GitHub (Aug 14, 2019):
@polo123qwe are you still experiencing this issue?