mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Existing configuration file gets corrupted if there is no free disk space available #11834
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#11834
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 @moonburnt on GitHub (Mar 10, 2021).
Please provide the following information
qBittorrent version and Operating System
Qbittorrent 4.3.3 (64-bit), Manjaro Linux
If on linux, libtorrent-rasterbar and Qt version
Qt: 5.15.2
Libtorrent: 1.2.11
What is the problem
Running out of free disk space cause qbittorrent's configuration file (in $HOME/.config/qBittorrent/) to break - the very next time you launch program, your settings will be reset to defaults. Doesnt seem to affect downloads - just configuration.
It kinda feels like configuration file gets autosaved each X seconds/minutes regardless if there has been any changes to it. And this process doesnt check if its possible to write data on disk. Thus, if its not - configuration is getting corrupted.
What is the expected behavior
Before saving configuration file, check if its possible to do so. If not - send error message and dont overwrite existing configuration.
Steps to reproduce
Extra info(if any)
I fully understand that this whole case is like a metaphor to shooting yourself in leg. Yet, say, firefox doesnt seem to behave like that in case of similar emergency. Thus I've considered it to be a bug
@flakyton commented on GitHub (Mar 13, 2021):
The same issue here. I'm not sure it is a disk space issue, but I've observed the configuration got reset to default after upgrading to 4.3.3. After I have updated configuration manually to match the previous one, it got reset back after the restart. The tell is that created
$HOME/.config/qBittorrent/qBittorrent_new.confis a bare bones empty configuration.@ghost commented on GitHub (Jul 23, 2022):
@Chocobo1 does https://github.com/qbittorrent/qBittorrent/pull/15419 fix this issue?
@Chocobo1 commented on GitHub (Jul 23, 2022):
No.
However qbt do have some mechanism to deal with this problem. Although I'm not sure if that (mechanism) is sufficient or reliable.