Bug 305482

Summary: Kexi crashes on rename of PostGreSQL table that was renamed through pgAdmin
Product: [Applications] KEXI Reporter: mc <mateolan>
Component: KexiDBAssignee: Jarosław Staniek <staniek>
Status: CLOSED UPSTREAM    
Severity: crash CC: adam, inksi
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description mc 2012-08-20 10:18:07 UTC 
Application: kexi (2.4.0 (Calligra 2.4.0))
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-29-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Altered the name of a table that had been created through Kexi, on a postgres database. renamed the table in pgAdmin, then tried to use the new table in Kexi. Kexi didn't pickup the new name of the table, even upon Kexi restart--and crashed when tried to rename the Kexi.  Optimal behavior: Kexi writes only its ids into kexi__objects table, and joins system table to reads and reflect postgres table names...

-- Backtrace:
Application: Kexi (kexi), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f81539f1780 (LWP 4571))]

Thread 2 (Thread 0x7f8139e34700 (LWP 4575)):
#0  0x00007f8151902b03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f814e4a2036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f814e4a249a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8141bdb406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f814e4c39e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f814e96ee9a in start_thread (arg=0x7f8139e34700) at pthread_create.c:308
#6  0x00007f815190e4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f81539f1780 (LWP 4571)):
[KCrash Handler]
#6  0x00007f8151852445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f8151855bab in __GI_abort () at abort.c:91
#8  0x00007f814f38169d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f814f37f846 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f814f37f873 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f814f37f9b6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f8151d5316c in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f8151d57f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#14 0x0000000000400891 in main (argc=<optimized out>, argv=0x7fffddbcccf8) at /build/buildd/calligra-2.4.0/kexi/main.cpp:36

Possible duplicates by query: bug 305122, bug 303603, bug 303502, bug 303176, bug 302750.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-09-30 14:02:57 UTC 
Unfortunately, the backtrace doesn't contain much helpful information due to uncaught exception (not your fault). 

If you can reproduce the crash every time,  please follow the guide[1] and try to run it under gdb to get a better backtrace.  

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 2 Jarosław Staniek 2016-11-01 21:39:25 UTC 
New postgresql driver (from KDb) is in use. Please test that and let us know about any issues.