[2.4.0] Multiple Crashes in qBittorrent

Bug #637909 reported by SDERAWI
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qBittorrent
New
Undecided
Unassigned

Bug Description

*************************************************************
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
  [0x444400]
  /usr/lib/libQtCore.so.4 : QProcess::waitForStarted(int)+0x6f [0x2f23b3f]
  /usr/lib/libQtCore.so.4 : QProcess::waitForFinished(int)+0x7f [0x2f23bcf]
  /usr/lib/libQtCore.so.4 : QProcess::execute(QString const&)+0x6a [0x2f286ba]
  qbittorrent : Bittorrent::autoRunExternalProgram(QTorrentHandle, bool)+0x24f [0x812048b]
  qbittorrent : Bittorrent::readAlerts()+0xc29 [0x812198b]
  qbittorrent : Bittorrent::qt_metacall(QMetaObject::Call, int, void**)+0x185b [0x826e259]
  /usr/lib/libQtCore.so.4 : QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**)+0x3a [0x2f92c9a]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2d5 [0x2fa13d5]
  /usr/lib/libQtCore.so.4 : QTimer::timeout()+0x37 [0x2ff2aa7]
  /usr/lib/libQtCore.so.4 : QTimer::timerEvent(QTimerEvent*)+0x3e [0x2fa960e]
  /usr/lib/libQtCore.so.4 : QObject::event(QEvent*)+0x84 [0x2f9e254]
  /usr/lib/libQtGui.so.4 : QApplicationPrivate::notify_helper(QObject*, QEvent*)+0xac [0x23354dc]
  /usr/lib/libQtGui.so.4 : QApplication::notify(QObject*, QEvent*)+0x17e [0x233c05e]
  /usr/lib/libQtCore.so.4 : QCoreApplication::notifyInternal(QObject*, QEvent*)+0x7b [0x2f8da3b]
  /usr/lib/libQtCore.so.4 : ()+0x197d66 [0x2fbcd66]
  /usr/lib/libQtCore.so.4 : ()+0x194917 [0x2fb9917]
  /lib/libglib-2.0.so.0 : g_main_context_dispatch()+0x1d5 [0x71c5e5]
  /lib/libglib-2.0.so.0 : ()+0x3f2d8 [0x7202d8]
  /lib/libglib-2.0.so.0 : g_main_context_iteration()+0x68 [0x7204b8]
  /usr/lib/libQtCore.so.4 : QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x65 [0x2fb95d5]
  /usr/lib/libQtGui.so.4 : ()+0x1f5135 [0x23f5135]
  /usr/lib/libQtCore.so.4 : QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x49 [0x2f8c059]
  /usr/lib/libQtCore.so.4 : QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0xfa [0x2f8c4aa]
  /usr/lib/libQtCore.so.4 : QCoreApplication::exec()+0xaf [0x2f9069f]
  /usr/lib/libQtGui.so.4 : QApplication::exec()+0x27 [0x2335577]
  qbittorrent : main()+0x121f [0x8109ead]
  /lib/tls/i686/cmov/libc.so.6 : __libc_start_main()+0xe6 [0x7eafbd6]
  qbittorrent() [0x8103cc1]
mv: target `3/Finished' is not a directory
Segmentation fault

Revision history for this message
SDERAWI (sderawi-deactivatedaccount) wrote :

*************************************************************
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
  [0xb56400]
  /usr/lib/libdbus-glib-1.so.2 : dbus_g_proxy_connect_signal()+0x2b [0x11cbab]
  /usr/lib/libnotify.so.1 : notify_notification_show()+0xcb [0xd759ab]
  qbittorrent : GUI::showNotificationBaloon(QString, QString) const+0xd2 [0x81908ba]
  qbittorrent : GUI::finishedTorrent(QTorrentHandle&) const+0x117 [0x818a69d]
  qbittorrent : GUI::qt_metacall(QMetaObject::Call, int, void**)+0x6eb [0x8273bbd]
  /usr/lib/libQtCore.so.4 : QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**)+0x3a [0x61e4c9a]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2d5 [0x61f33d5]
  qbittorrent : Bittorrent::finishedTorrent(QTorrentHandle&)+0x3c [0x826e586]
  qbittorrent : Bittorrent::readAlerts()+0x15c [0x8120ebe]
  qbittorrent : Bittorrent::qt_metacall(QMetaObject::Call, int, void**)+0x185b [0x826e259]
  /usr/lib/libQtCore.so.4 : QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**)+0x3a [0x61e4c9a]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2d5 [0x61f33d5]
  /usr/lib/libQtCore.so.4 : QTimer::timeout()+0x37 [0x6244aa7]
  /usr/lib/libQtCore.so.4 : QTimer::timerEvent(QTimerEvent*)+0x3e [0x61fb60e]
  /usr/lib/libQtCore.so.4 : QObject::event(QEvent*)+0x84 [0x61f0254]
  /usr/lib/libQtGui.so.4 : QApplicationPrivate::notify_helper(QObject*, QEvent*)+0xac [0x12c24dc]
  /usr/lib/libQtGui.so.4 : QApplication::notify(QObject*, QEvent*)+0x17e [0x12c905e]
  /usr/lib/libQtCore.so.4 : QCoreApplication::notifyInternal(QObject*, QEvent*)+0x7b [0x61dfa3b]
  /usr/lib/libQtCore.so.4 : ()+0x197d66 [0x620ed66]
  /usr/lib/libQtCore.so.4 : ()+0x194917 [0x620b917]
  /lib/libglib-2.0.so.0 : g_main_context_dispatch()+0x1d5 [0x58e5e5]
  /lib/libglib-2.0.so.0 : ()+0x3f2d8 [0x5922d8]
  /lib/libglib-2.0.so.0 : g_main_context_iteration()+0x68 [0x5924b8]
  /usr/lib/libQtCore.so.4 : QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x65 [0x620b5d5]
  /usr/lib/libQtGui.so.4 : ()+0x1f5135 [0x1382135]
  /usr/lib/libQtCore.so.4 : QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x49 [0x61de059]
  /usr/lib/libQtCore.so.4 : QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0xfa [0x61de4aa]
  /usr/lib/libQtCore.so.4 : QCoreApplication::exec()+0xaf [0x61e269f]
  /usr/lib/libQtGui.so.4 : QApplication::exec()+0x27 [0x12c2577]
  qbittorrent : main()+0x121f [0x8109ead]
  /lib/tls/i686/cmov/libc.so.6 : __libc_start_main()+0xe6 [0x8d29bd6]
  qbittorrent() [0x8103cc1]
Segmentation fault

summary: - [2.4.0] Crash when using External Program
+ [2.4.0] Multiple Crashes in qBittorrent
Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

The second backtrace seems to be linked to on screen notification

Revision history for this message
SDERAWI (sderawi-deactivatedaccount) wrote :

3rd Crash >>> When clicking on an RSS item.

The application '<unknown>' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
*************************************************************
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
  [0x5ab400]
  /lib/tls/i686/cmov/libc.so.6 : ()+0x111e31 [0x13b9e31]
Segmentation fault

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

Regarding the first backtrace, which seems to happen on calling an external application. Could you tell me what external app you are calling?

The output
mv: target `3/Finished' is not a directory

Seems to suggest that the external program is not used properly and it may be the origin of the crash.

Revision history for this message
SDERAWI (sderawi-deactivatedaccount) wrote :

mv: target `3/Finished' is not a directory

was fixed by escaping the space before the 3 >>> "TERABYTE 3" or TERABYTE\ 3 , but the crash happened after that also.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.