Application that crashed: kexi Version of the application: 1.1.3 (KOffice 1.6.3) KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.30.5-43.fc11.i686.PAE i686 Distribution: "Fedora release 11 (Leonidas)" What I was doing when the application crashed: During editing a form, kexi crashed suddenly. -- Backtrace: Application: Kexi (kexi), signal: Segmentation fault [KCrash Handler] #6 0x03ba0417 in QVariant::operator=(QVariant const&) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #7 0x0017ad50 in updateRowDataWithNewValues(KexiDB::QuerySchema&, QValueVector<QVariant>&, QMap<KexiDB::QueryColumnInfo*, QVariant>&, QMap<KexiDB::QueryColumnInfo*, int>&) () from /usr/lib/libkexidb.so.2 #8 0x0015f51b in KexiDB::Connection::insertRow(KexiDB::QuerySchema&, QValueVector<QVariant>&, KexiDB::RowEditBuffer&, bool) () from /usr/lib/libkexidb.so.2 #9 0x001a44d5 in KexiDB::Cursor::insertRow(QValueVector<QVariant>&, KexiDB::RowEditBuffer&, bool) () from /usr/lib/libkexidb.so.2 #10 0x00897c65 in KexiTableViewData::saveRow(KexiTableItem&, bool, bool) () from /usr/lib/libkexidatatable.so.2 #11 0x00898853 in KexiTableViewData::saveNewRow(KexiTableItem&, bool) () from /usr/lib/libkexidatatable.so.2 #12 0x008797b8 in KexiDataAwareObjectInterface::acceptRowEdit() () from /usr/lib/libkexidatatable.so.2 #13 0x0087aec7 in KexiDataAwareObjectInterface::setCursorPosition(int, int, bool) () from /usr/lib/libkexidatatable.so.2 #14 0x008753ed in KexiDataAwareObjectInterface::selectRow(int) () from /usr/lib/libkexidatatable.so.2 #15 0x0087582b in KexiDataAwareObjectInterface::selectNextRow() () from /usr/lib/libkexidatatable.so.2 #16 0x0818d6ab in KexiFormScrollView::moveToNextRecordRequested() () from /usr/lib/libkexiformutils.so.2 #17 0x0020d9d6 in KexiRecordNavigator::slotNextButtonClicked() () from /usr/lib/libkexiguiutils.so.2 #18 0x0020f028 in KexiRecordNavigator::qt_invoke(int, QUObject*) () from /usr/lib/libkexiguiutils.so.2 #19 0x03b5876a in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #20 0x03b5a7f8 in QObject::activate_signal(int) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #21 0x03ef605c in QButton::clicked() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #22 0x03c01b38 in QButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #23 0x03b95d35 in QWidget::event(QEvent*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #24 0x03aefccd in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #25 0x03af1cf9 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #26 0x063d9f6c in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4 #27 0x03a8701e in QApplication::sendSpontaneousEvent(QObject*, QEvent*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #28 0x03a86ab5 in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #29 0x03a857f5 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #30 0x03a97d43 in QEventLoop::processEvents(unsigned int) () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #31 0x03b0a940 in QEventLoop::enterLoop() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #32 0x03b0a7e6 in QEventLoop::exec() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #33 0x03af03bf in QApplication::exec() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #34 0x00e60845 in kdemain () from /usr/lib/libkdeinit_kexi.so #35 0x0804853b in kdemain () #36 0x00269a66 in __libc_start_main () from /lib/libc.so.6 #37 0x08048481 in kdemain () This bug may be a duplicate of or related to bug 138613 Reported using DrKonqi
> During editing a form, kexi crashed suddenly. I'm sorry, It was a misunderstanding. When I tried to add a record by a form in kexi, kexi crashed suddenly.
Hi Yukio, thanks for the report. Could you try the sample database attached for the bug #138613? Or provide your own small test database here. It is also important to know if the crash happens only for specific usage scenario or always.
Assuming fixed since such a fundamental issue would be catched already. If you find any related issues we will reopen. Thanks a lot!