Summary: | Kexi Crash on MDB Import (Linux - Debian/Ubuntu) | ||
---|---|---|---|
Product: | [Applications] KEXI | Reporter: | Daniel Hunt <daniel.hunt> |
Component: | Migration/Import/Export | Assignee: | Jarosław Staniek <staniek> |
Status: | CLOSED WAITINGFORINFO | ||
Severity: | crash | CC: | esancho, houseofbadger, mail.list.4.ag.hob |
Priority: | NOR | ||
Version: | 1.1.2 (KOffice 1.6.2) | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | backttrace report of a kexi crash when trying to import mdb database |
Description
Daniel Hunt
2007-05-14 17:56:02 UTC
Could you send me example .mdb database that the Import dialog crashes with? You can remove most of the data and tables if you want. Every mdb file I import crashes. Without fail :) Please downloading Kexi 1.1.3 and the MDB Driver from http://kexi-project.org/wiki/wikiview/index.php?Source#Kexi_1.1.3_-_within_KOffice_1.6.3 and compiling. First, uninstall previous Kexi and MDB Driver (make uninstall or unsermake uninstall -if you have the original source code). MDB Import works for many users... > Please downloading Kexi 1.1.3 and the MDB Driver from > http://kexi-project.org/wiki/wikiview/index.php?Source#Kexi_1.1.3_-_within_KOffice_1.6.3 and compiling. > First, uninstall previous Kexi and MDB Driver (make uninstall or unsermake uninstall -if you have the original source code). Thanks for the tip. I compiled kexi and koffice, with mysql drivers and patches applied, but it still crashes. For comparison, the file is sr20.mdb in this archive: http://www.nal.usda.gov/fnic/foodcomp/Data/SR20/dnload/sr20db.zip Thanks! Andrew Dougherty Created attachment 23171 [details]
backttrace report of a kexi crash when trying to import mdb database
I can confirm that the same issue troubles me as well. I love the clean look of
kexi but unfortunately I am working with a ms access db. I am unable to import
the db to kexi. kexi crashes right after selecting the structure and table
option as mentioned in the bug report.
I have not tried compiling the new kexi. I used the kexi and the
mdb-import-plugin from the ubuntu repositories. I am using kexi on a Ubuntu
Gutsy (7.10) and not kubuntu. I have installed the entire koffice to be sure
all kexi dependencies are met, but no success.
I am attaching the backtrace report for you to see.
ANd by the way, I did install the kexi demo version on another windows machine
and it worked like a charm. The import was successful, but the demo restricts
to 100 rows and I really want to use kexi on gutsy. Anything else that you
would require I will be glad to help.
Thanks Biswajit, This is either problem in Ubuntu or its compiler/linker. You have not tried compiling the new kexi - please consider doing so (SVN version branches/koffice/1.6/koffice/, with debugging turned on by --enable-debug=full option of ./configure) or report the problem to (K)ubuntu packagers. Without this effort you will constantly see Windows versions more stable. Your debugging information looks like: (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) barely usable... Dear Jaroslaw, Thanks for your advice. After your suggestion, I tried compiling the whole of yesterday and failed miserably. Then I loaded the kubuntu desktop and installed kexi and still it would not import the database. But I did something that did the trick. I installed the kexi-mdb-driver after uninstalling kexi-mdb-plugin. And then I was able to import easily. Wow! That really saved me a lot of trouble. Thanks again for your help and for working with kexi. I bet kexi is going to be the database in the linux world. I have no doubts about it. I think you can file this bug as solved/sorted. Same here, kexi is 1.1.3 OS is Debian Lenny Compiler is i486-linux-gnu Importing MDB file crashes the application. Backtrace: (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5e806c0 (LWP 15509)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb6999bbf in QObject::insertChild () from /usr/lib/libqt-mt.so.3 #7 0xb79e8898 in KexiDB::Object::clearError () from /usr/lib/libkexidb.so.2 #8 0xb58a0cf1 in KexiMigration::ImportWizard::prepareImport () from /usr/lib/libkeximigrate.so.2 #9 0xb58a3414 in KexiMigration::ImportWizard::checkUserInput () from /usr/lib/libkeximigrate.so.2 #10 0xb58a3be0 in KexiMigration::ImportWizard::arriveImportingPage () from /usr/lib/libkeximigrate.so.2 #11 0xb58a3f1b in KexiMigration::ImportWizard::pageSelected () from /usr/lib/libkeximigrate.so.2 #12 0xb58a3ffb in KexiMigration::ImportWizard::qt_invoke () from /usr/lib/libkeximigrate.so.2 #13 0xb699ab10 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #14 0xb699b061 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #15 0xb6d62c18 in QWizard::selected () from /usr/lib/libqt-mt.so.3 #16 0xb6b7ac76 in QWizard::showPage () from /usr/lib/libqt-mt.so.3 #17 0xb6b79607 in QWizard::next () from /usr/lib/libqt-mt.so.3 #18 0xb58a40bf in KexiMigration::ImportWizard::next () from /usr/lib/libkeximigrate.so.2 #19 0xb6d62b82 in QWizard::qt_invoke () from /usr/lib/libqt-mt.so.3 #20 0xb72d784b in KWizard::qt_invoke () from /usr/lib/libkdeui.so.4 #21 0xb58a3f82 in KexiMigration::ImportWizard::qt_invoke () from /usr/lib/libkeximigrate.so.2 #22 0xb699ab10 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #23 0xb699b5f5 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #24 0xb6d342f9 in QButton::clicked () from /usr/lib/libqt-mt.so.3 #25 0xb6a3856a in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #26 0xb69d1460 in QWidget::event () from /usr/lib/libqt-mt.so.3 #27 0xb692f36a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #28 0xb6931522 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #29 0xb70fab52 in KApplication::notify () from /usr/lib/libkdecore.so.4 #30 0xb68c073d in QApplication::sendSpontaneousEvent () from /usr/lib/libqt-mt.so.3 #31 0xb68bf3eb in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #32 0xb68bd858 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #33 0xb68d467c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #34 0xb694a6e4 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #35 0xb6930e91 in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3 #36 0xb6b4edc1 in QDialog::exec () from /usr/lib/libqt-mt.so.3 #37 0xb7bc5e0e in KexiMainWindowImpl::showProjectMigrationWizard () from /usr/lib/libkeximain.so.2 #38 0xb7bc90ef in KexiMainWindowImpl::startup () from /usr/lib/libkeximain.so.2 #39 0xb7bc9607 in KexiMainWindowImpl::create () from /usr/lib/libkeximain.so.2 #40 0xb7f228b4 in kdemain () from /usr/lib/libkdeinit_kexi.so #41 0x08048542 in ?? () #42 0xb7ccc450 in __libc_start_main () from /lib/i686/cmov/libc.so.6 #43 0x080484b1 in ?? () I would like to change title to : Kexi Crash on MDB Import (Linux: Debian / Ubuntu) @couannette: Please uninstall kexi-mdb-plugin and install kexi-mdb-driver and then the importing will work. If that does nto work, then save the access 07 db as access 97/XP/03 db and them try the importing with the kexi-mdb-driver. I am sure it will work. It worked for me. where can I Find kexi-mdb-driver it cannot be found in Ubumtu repository. I use ubuntu 8.04.1 Alexander, please go to http://packages.ubuntu.com/ and type 'mdb' in the search box. You should see kexi-mdb-plugin package for 8.0x. I talked about kexi-md-driver instead of kexi-mdb-plugin. In recommendation I shall remove kexi-mdb-plugin and install kexi-md-driver What can recomend me in this case Thanks Alex Just use kexi-mdb-plugin... Mentioning *-driver name was just my mistake because I have no (k)ubuntu here. *** Bug 207751 has been marked as a duplicate of this bug. *** Please also see bug #151462 for updated plugin. If you miss plugin, reading bug #145429 could help. |