Bug 156811 - kexi crashes on importing mdb database.
Summary: kexi crashes on importing mdb database.
Status: CLOSED DUPLICATE of bug 240343
Alias: None
Product: KEXI
Classification: Applications
Component: General (show other bugs)
Version: 1.1.3 (KOffice 1.6.3)
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Jarosław Staniek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-27 23:07 UTC by Raúl
Modified: 2016-01-29 19:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
.xsession-errors excerpt with info on the crash. (35.83 KB, text/x-log)
2008-01-27 23:10 UTC, Raúl
Details
Valgrind log of the crash. (64.46 KB, text/x-objcsrc)
2008-01-27 23:11 UTC, Raúl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raúl 2008-01-27 23:07:32 UTC
Version:           1.1.3 (KOffice 1.6.3) (using 3.5.8, Debian Package 4:3.5.8.dfsg.1-6 (lenny/sid))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.24-rtoi-rc5

I was reviewing Debian bugs and I found this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412435

This is a crash when trying to import a .mdb file.The reporter was using 1.6.1, but it's 100% reproducible on 1.6.3, when trying to reproduce I got SIGABRT but also SIGSEGV. Unfortunately something should be broken on my system, so I couldn't get an up to date backtrace, hence I reproduce the one from the original reporter.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
...
[Thread debugging using libthread_db enabled]
[New Thread -1241748608 (LWP 18644)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#9  0xb5ad3b52 in mdb_read_indices () from /usr/lib/kde3/keximigrate_mdb.so
#10 0xb5acb8d5 in KexiMigration::MDBMigrate::getPrimaryKey ()
   from /usr/lib/kde3/keximigrate_mdb.so
#11 0xb5acd39c in KexiMigration::MDBMigrate::drv_readTableSchema ()
   from /usr/lib/kde3/keximigrate_mdb.so
#12 0xb5aa643a in KexiMigration::KexiMigrate::performImport ()
   from /usr/lib/libkeximigrate.so.2
#13 0xb5aadc2a in KexiMigration::ImportWizard::import ()
   from /usr/lib/libkeximigrate.so.2
#14 0xb5ab04c3 in KexiMigration::ImportWizard::next ()
   from /usr/lib/libkeximigrate.so.2
#15 0xb6e371cc in QWizard::qt_invoke () from /usr/lib/libqt-mt.so.3
#16 0xb738c53b in KWizard::qt_invoke () from /usr/lib/libkdeui.so.4
#17 0xb5ab0273 in KexiMigration::ImportWizard::qt_invoke ()
   from /usr/lib/libkeximigrate.so.2
#18 0xb6a7ad4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb6a7b7e0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb6e0cde7 in QButton::clicked () from /usr/lib/libqt-mt.so.3
#21 0xb6b17cf6 in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#22 0xb6ab16f0 in QWidget::event () from /usr/lib/libqt-mt.so.3
#23 0xb6a12c26 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#24 0xb6a14dc9 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#25 0xb71c3e0e in KApplication::notify () from /usr/lib/libkdecore.so.4
#26 0xb69a6495 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#27 0xb69a512f in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3
#28 0xb69a36b0 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#29 0xb69b9d02 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#30 0xb6a2d179 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#31 0xb6a1473d in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3
#32 0xb6c2e181 in QDialog::exec () from /usr/lib/libqt-mt.so.3
#33 0xb7c18cc5 in KexiMainWindowImpl::showProjectMigrationWizard ()
   from /usr/lib/libkeximain.so.2
#34 0xb7c1957c in KexiMainWindowImpl::startup () from /usr/lib/libkeximain.so.2
#35 0xb7c19a31 in KexiMainWindowImpl::create () from /usr/lib/libkeximain.so.2
#36 0xb7f3d9d2 in kdemain () from /usr/lib/libkdeinit_kexi.so
#37 0x08048512 in ?? ()

I'm also sending the .xsession-errors excerpt with some info about the crash and also a valgrind session output.

The original reporter used a (C) file, so he can make it publicly available, but I have it and he told me that he sent it to J. Staniek. Anyway you can find his e-mail address on debian bug report.

HTH
Comment 1 Raúl 2008-01-27 23:10:47 UTC
Created attachment 23317 [details]
.xsession-errors excerpt with info on the crash.
Comment 2 Raúl 2008-01-27 23:11:25 UTC
Created attachment 23318 [details]
Valgrind log of the crash.
Comment 3 Raúl 2008-01-27 23:27:27 UTC
BTW, I would appreciate some comment as this bug is from kexi its own or the mdb plugin.

Thanks.

Comment 4 Biswajit Dutta Baruah 2008-02-03 14:16:32 UTC
I would suggest the following. Though this applies to ubuntu, I would think the same would apply to debian as well depending on from where the error originated.

Just uninstall the kexi-mdb-plugin and install kexi-mdb-driver. That should solve the problem of crash. Also if you are trying to import an access 07 db, then better to save it as an access 03 or 97 db before an attempt at importing.
Comment 5 Jarosław Staniek 2009-09-19 20:42:41 UTC
Please also see bug #151462 for updated plugin. If you miss plugin, reading report #145429 could help.
Comment 6 Jarosław Staniek 2011-07-17 22:29:11 UTC

*** This bug has been marked as a duplicate of bug 240343 ***