Change connection options - exits abruptly

[Jaime Sánchez]

After changing some connection options (download speed...) the program terminates abruptly, no error on screen, simply terminates.

Qbittorrent 1.5.2
Ubuntu karmic
kernel 2.6.31-10
kde 4.3.1

[Christophe Dumez (hydr0g3n)]

Did you run qbittorrent in a term? A backtrace should be output in the term whenever qBittorrent crashes. I will try to reproduce but having the backtrace would be helpful if I cannot reproduce.

[Jaime Sánchez (jskartman)]

ok, i found what happens. I have my folder watching pointing to
nonexistent directory, and this is the cause, when i correct this
option to an existing directory all works fine.

The output when folder watching is pointing to nonexistent directory is:

QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed:
No such file or directory
QFileSystemWatcher: failed to add paths: /mnt/data/torrents-linux
Warning: Local domain socket was not closed cleanly, deleting file...

*** NOTE qbittorrent opens ok now , but when u change connection options: ***

*************************************************************
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
  [0x118400]
  qbittorrent : bittorrent::enableDirectoryScanning(QString)+0x5e [0x81178ce]
  qbittorrent : GUI::configureSession(bool)+0x2f6 [0x8092b96]
  qbittorrent : GUI::OptionsSaved(bool)+0x137 [0x8095fe7]
  qbittorrent : GUI::qt_metacall(QMetaObject::Call, int, void**)+0x52a
 [0x81975ea]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*, int, int,
void**)+0x233 [0x851253]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*,
QMetaObject const*, int, void**)+0x52 [0x851eb2]
  qbittorrent : options_imp::status_changed(bool) const+0x3b [0x8197e5b]
  qbittorrent : options_imp::qt_metacall(QMetaObject::Call, int,
void**)+0x2c2 [0x8198122]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*, int, int,
void**)+0x233 [0x851253]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*,
QMetaObject const*, int, void**)+0x52 [0x851eb2]
  /usr/lib/libQtGui.so.4 :
QDialogButtonBox::clicked(QAbstractButton*)+0x43 [0x140fef3]
  /usr/lib/libQtGui.so.4 [0x14100dc]
  /usr/lib/libQtGui.so.4 :
QDialogButtonBox::qt_metacall(QMetaObject::Call, int, void**)+0xf6
[0x1411e66]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*, int, int,
void**)+0x233 [0x851253]
  /usr/lib/libQtCore.so.4 : QMetaObject::activate(QObject*,
QMetaObject const*, int, int, void**)+0x58 [0x8516c8]
  /usr/lib/libQtGui.so.4 : QAbstractButton::clicked(bool)+0x51 [0x16b3911]
  /usr/lib/libQtGui.so.4 [0x13dc249]
  /usr/lib/libQtGui.so.4 [0x13ddea4]
  /usr/lib/libQtGui.so.4 :
QAbstractButton::mouseReleaseEvent(QMouseEvent*)+0x91 [0x13de131]
  /usr/lib/libQtGui.so.4 : QWidget::event(QEvent*)+0x762 [0x107bf92]
  /usr/lib/libQtGui.so.4 : QAbstractButton::event(QEvent*)+0x3e [0x13dc0ee]
  /usr/lib/libQtGui.so.4 : QPushButton::event(QEvent*)+0x3d [0x148634d]
  /usr/lib/libQtGui.so.4 :
QApplicationPrivate::notify_helper(QObject*, QEvent*)+0xb4
[0x1026f44]
  /usr/lib/libQtGui.so.4 : QApplication::notify(QObject*,
QEvent*)+0xb43 [0x102f023]
  /usr/lib/libQtCore.so.4 : QCoreApplication::notifyInternal(QObject*,
QEvent*)+0x7b [0x83b6bb]
  /usr/lib/libQtGui.so.4 :
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*,
QWidget*, QWidget**, QPointer<QWidget>&)+0xde [0x102df5e]
  /usr/lib/libQtGui.so.4 [0x109c6e0]
  /usr/lib/libQtGui.so.4 :
QApplication::x11ProcessEvent(_XEvent*)+0x19bb [0x109bb6b]
  /usr/lib/libQtGui.so.4 [0x10c83f2]
  /lib/libglib-2.0.so.0 : g_main_context_dispatch()+0x1f8 [0x2b10e...

[Christophe Dumez (hydr0g3n)]

Good, this is a bug :p I will fix this really soon. Thanks for the report.

[Christophe Dumez (hydr0g3n)]

This is fixed in SVN, thanks!