mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Segfault on startup #10935
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#10935
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 @fsnk on GitHub (Sep 25, 2020).
Please provide the following information
qBittorrent version and Operating System
Qbittorrent 4.1.5
Linux Debian 10
If on linux, libtorrent-rasterbar and Qt version
libtorrent-rasterbar 1.1.11
Qt 4:4.8.7 / 5.11.3
What is the problem
Crashes on startup (segfault)
What is the expected behavior
Not crashing :)
Steps to reproduce
Start the program
Extra info(if any)
Computer says file bug report:
Please file a bug report at http://bug.qbittorrent.org and provide the following information:
qBittorrent version: v4.1.5
Caught signal: SIGSEGV
Stack trace:
/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x95b84 [0x7f97059e1b84]
/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x94c49 [0x7f97059e0c49]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QObject::event(QEvent*)+0xe2 [0x7f97056a6072]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplicationPrivate::notify_helper(QObject*, QEvent*)+0x81 [0x7f97062704c1]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplication::notify(QObject*, QEvent*)+0x210 [0x7f9706277970]
qbittorrent : Application::notify(QObject*, QEvent*)+0x22 [0x5637dc0f46e2]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x179 [0x7f970567c489]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x1cb [0x7f970567f46b]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0x2bc103 [0x7f97056ce103]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_dispatch()+0x2ae [0x7f9704340f2e]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : ()+0x4e1c8 [0x7f97043411c8]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_iteration()+0x2c [0x7f970434125c]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x67 [0x7f97056cd727]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)+0x13b [0x7f970567b15b]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QThread::exec()+0xb6 [0x7f97054cae76]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0xc2a67 [0x7f97054d4a67]
/lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x7fa3 [0x7f97053f8fa3]
/lib/x86_64-linux-gnu/libc.so.6 : clone()+0x3f [0x7f97050064cf]
#################################################
I was able to get past the crash-on-launch to make some of the settings changes (disabled favicon download, I don't use RSS or search plugins) suggested on #9667 by launching qbittorrent-nox and removing all the the torrents. Then the crashes stopped. (It would have been helpful to have that in #9667 because it's super hard to figure out how to adjust the settings in a program that crashes the moment you launch it. :) )
@FranciscoPombal commented on GitHub (Sep 25, 2020):
https://github.com/qbittorrent/qBittorrent/blob/master/CONTRIBUTING.md
4.1.5 is too old. If you have any issues with the latest version (at this point, 4.2.5 is too old as well and the next official release is not out yet, you are encouraged to try the latest
mastercommit instead), please open a new issue report.