Bug 249038

Summary: Kexi crashes when opening Sqlite 3 file created outside
Product: [Applications] KEXI Reporter: Marcelo Escobal <marcelo.escobal>
Component: Migration/Import/ExportAssignee: Jarosław Staniek <staniek>
Status: CLOSED DUPLICATE    
Severity: crash CC: salvalemany, wb0fhu
Priority: NOR    
Version: 2.2.2 (KOffice 2.2.2)   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Marcelo Escobal 2010-08-25 21:46:19 UTC 
Application: kexi (2.2.2 (KOffice 2.2.2))
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
When I try to open a Sqlite 3 file created with sql statements from command line, kKexi crashes (no messages). File has a sq3 extension.

 -- Backtrace:
Application: Kexi (kexi), signal: Aborted
[KCrash Handler]
#5  0x00007fa91fcfaa75 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007fa91fcfe5c0 in *__GI_abort () at abort.c:92
#7  0x00007fa91fd344fb in __libc_message (do_abort=<value optimized out>, fmt=<value optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#8  0x00007fa91fd3e5b6 in malloc_printerr (action=3, str=0x7fa91fe0eab3 "free(): invalid pointer", ptr=<value optimized out>) at malloc.c:6264
#9  0x00007fa91fd44e53 in *__GI___libc_free (mem=<value optimized out>) at malloc.c:3738
#10 0x00007fa912595ab2 in ~SQLiteConnectionInternal (this=0xed93b0, __in_chrg=<value optimized out>) at ../../../../../kexi/kexidb/drivers/sqlite/sqliteconnection.cpp:58
#11 0x00007fa9125955d0 in ~SQLiteConnection (this=0xedb290, __in_chrg=<value optimized out>) at ../../../../../kexi/kexidb/drivers/sqlite/sqliteconnection.cpp:90
#12 0x00007fa91f7b425d in KexiProject::closeConnection (this=0xebdf00) at ../../../kexi/core/kexiproject.cpp:527
#13 0x00007fa91f7bc543 in KexiProject::openInternal (this=0xebdf00, incompatibleWithKexi=0x7fff72f0e1e0) at ../../../kexi/core/kexiproject.cpp:226
#14 0x00007fa91f7bcce9 in KexiProject::open (this=0x2074, incompatibleWithKexi=@0x2074) at ../../../kexi/core/kexiproject.cpp:177
#15 0x00007fa9211aa3f5 in KexiMainWindow::openProject (this=0x870120, projectData=...) at ../../../kexi/main/KexiMainWindow.cpp:1549
#16 0x00007fa9211b0e49 in KexiMainWindow::startup (this=0x870120) at ../../../kexi/main/KexiMainWindow.cpp:1503
#17 0x00007fa9211b62aa in KexiMainWindow::create (argc=<value optimized out>, argv=0x7fff72f0e678, aboutdata=<value optimized out>) at ../../../kexi/main/KexiMainWindow.cpp:285
#18 0x0000000000400918 in main (argc=8308, argv=0x2074) at ../../kexi/main.cpp:30

This bug may be a duplicate of or related to bug 247864.

Possible duplicates by query: bug 247864, bug 245030.

Reported using DrKonqi
Comment 1 Jarosław Staniek 2010-08-28 00:22:06 UTC 
It of course should not crash, but Kexi does not support sqlite3 files created on the outside. 

I set the Component to migration.
Comment 2 Jarosław Staniek 2010-08-30 22:38:40 UTC 
Just commited this improvement:

SVN commit 1170135 by staniek:

Core
*Clarify error message: when non-kexi SQLite file is opened, display "Database project '...' does not appear to have been created using Kexi and cannot be opened. It is an SQLite file created using other tools."
Comment 3 Jarosław Staniek 2010-08-30 23:30:13 UTC 
*** Bug 247864 has been marked as a duplicate of this bug. ***
Comment 4 Joe Fay 2010-09-01 16:03:07 UTC 
Created attachment 51180 [details]
New crash information added by DrKonqi

I was in Dolphin, looking at files created by Gimp (lastest version for Opensuse 11.3, 32bit).  Gimp was not loaded at the time of the incident.  I attempted to open one of the sqlite database files, and the crash immediately ensued.  All necessary files were installed that should have allowed me to view the file.
Joe
Comment 5 Jarosław Staniek 2010-09-07 23:08:23 UTC 
Please use the patch called "Possible fix for crash" attached to bug #245030 or ask creators of your distribution to apply it.

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