mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
qbittorrent won't start in any ways #7773
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#7773
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 @Rickardlem on GitHub (Sep 18, 2018).
Please provide the following information
If on linux, libtorrent and Qt version
3.3.1updated to 4.1.2What is the problem
Qbittorrent doesn't start by any means. Even by shell, it returns an error message.
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot write to torrent resume folder.
What is the expected behavior
To qBittorrent to be on and operating
Steps to reproduce
Just try to get qBittorrent on
Extra info(if any)
The complete stack of the generated informations is:
/lib/x86_64-linux-gnu/libc.so.6 : gsignal()+0x38 [0x7f819218c428]
/lib/x86_64-linux-gnu/libc.so.6 : abort()+0x16a [0x7f819218e02a]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __gnu_cxx::__verbose_terminate_handler()+0x16d [0x7f8192acf84d]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d6b6 [0x7f8192acd6b6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d701 [0x7f8192acd701]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d919 [0x7f8192acd919]
qbittorrent : BitTorrent::Session::initResumeFolder()+0x226 [0x519676]
qbittorrent : BitTorrent::Session::Session(QObject*)+0x1e4 [0x51b734]
qbittorrent : BitTorrent::Session::initInstance()+0x37 [0x51c5c7]
qbittorrent : Application::exec(QStringList const&)+0x34 [0x4bf5a4]
qbittorrent : main()+0x492 [0x4b6ec2]
/lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xf0 [0x7f8192177830]
qbittorrent : _start()+0x29 [0x4bae09]
@zeule commented on GitHub (Sep 18, 2018):
The error message is generated if the app can not open for writing
session.lockfile in~/.local/share/data/qBittorrent/BT_backup/. Please check permissions. Also, your version is tool old and unsupported.@Rickardlem commented on GitHub (Sep 18, 2018):
Upgraded to the 4.1.2 but no progress.
Even as "su", it starts, but doesn't get any torrents, and the shell returns this message:
(qbittorrent:5082): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
@zeule commented on GitHub (Sep 18, 2018):
Please don't run it as root. Did the error message change after upgrade or did you solve the file problem. What's happening now?
@Rickardlem commented on GitHub (Sep 18, 2018):
No, the message error didn't change. I always get this:
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot write to torrent resume folder.
Please file a bug report at http://bug.qbittorrent.org and provide the following information:
qBittorrent version: v4.1.2
Caught signal: SIGABRT
Stack trace:
/lib/x86_64-linux-gnu/libc.so.6 : gsignal()+0x38 [0x7f72abe88428]
/lib/x86_64-linux-gnu/libc.so.6 : abort()+0x16a [0x7f72abe8a02a]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __gnu_cxx::__verbose_terminate_handler()+0x16d [0x7f72ac7cb84d]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d6b6 [0x7f72ac7c96b6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d701 [0x7f72ac7c9701]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d919 [0x7f72ac7c9919]
qbittorrent : BitTorrent::Session::initResumeFolder()+0x246 [0x533c16]
qbittorrent : BitTorrent::Session::Session(QObject*)+0x1ea0 [0x535b10]
qbittorrent : BitTorrent::Session::initInstance()+0x37 [0x538037]
qbittorrent : Application::exec(QStringList const&)+0x38 [0x4fe6f8]
qbittorrent : main()+0x3ea [0x4f151a]
/lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xf0 [0x7f72abe73830]
qbittorrent : _start()+0x29 [0x4f9a49]
It simply doesn't start.
@zeule commented on GitHub (Sep 18, 2018):
So... Have you checked the permissions? Free space?
@Rickardlem commented on GitHub (Sep 18, 2018):
I'm the only user, and never changed any of the permission, so it seems strange to me. Do you know the exact line to use for the check?
About the free space, I've got plenty of that.
@zeule commented on GitHub (Sep 18, 2018):
OK, please share output from:
stat ~/.local/share/data/qBittorrent/BT_backuptouch ~/.local/share/data/qBittorrent/BT_backup/session.lockdf -h ~/.local/share/data/qBittorrent/BT_backup[ -w ~/.local/share/data/qBittorrent/BT_backup/session.lock ] && echo "writeable" || echo "write permission denied"@Rickardlem commented on GitHub (Sep 18, 2018):
Ok, then (thanks in advance for your time).
First output:
File: '/home/rickard/.local/share/data/qBittorrent/BT_backup'
Dim.: 4096 Blocchi: 8 Blocco di IO: 4096 directory
Device: 803h/2051d Inode: 393156 Coll.: 2
Accesso: (0775/drwxrwxr-x) Uid: ( 1000/ rickard) Gid: ( 1000/ rickard)
Accesso : 2018-09-18 18:05:25.819538959 +0200
Modifica : 2018-09-18 18:05:25.815538921 +0200
Cambio : 2018-09-18 18:05:25.815538921 +0200
Creazione: -
Second output:
touch: impossible do touch di '/home/rickard/.local/share/data/qBittorrent/BT_backup/session.lock': Permission denied
Third output:
File system Dim. Used Dispon. Usage% Mounted on
/dev/sda3 29G 7,6G 20G 28% /
Fourth output:
write permission denied
@zeule commented on GitHub (Sep 18, 2018):
You see, you don't have write permission for that file. Maybe you somehow ran qBt for with root permissions and your ${HOME} and it created the file writable by root only. You can test that with
stat. Try to remove that file and launch qBt. If that does not help, you might have another security layer on top of the basic Linux filesystem security subsystem and it blocks you. In that case I can't help you. Try to figure that out with your distribution.@Rickardlem commented on GitHub (Sep 18, 2018):
Ok, I'll try. Thanks a lot for the help!