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 i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I downloaded and installed Kexi from Ubuntu 12.04 Software Center. While in the process of building a table for the first time (by importing from an MDE database; nothing imported; the table could not be opened) and subsequently trying to delete the table (it would not delete). To check out more of the program, I opened and closed "Query", "Forms", and then "Report" and Kexi crashed. -- Backtrace: Application: Kexi (kexi), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb7758740 (LWP 28924))] Thread 4 (Thread 0xb61f6b40 (LWP 28927)): #0 0x00dc2d10 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libpthread.so.0 #1 0x00208634 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6 #2 0x01d0d410 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ccdf9f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x01cce56b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x02ee4134 in ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so #6 0x01cf16b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x00dbfd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #8 0x001faace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xb57ffb40 (LWP 28928)): #0 0x00dc2c70 in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0 #1 0x00208634 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6 #2 0x01d0d410 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ccdf9f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x01cce56b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x028721ba in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #6 0x01cf16b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x00dbfd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #8 0x001faace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xb0470b40 (LWP 28961)): #0 0x00ddcdcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x00863315 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #2 0x0094d226 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #3 0x0094d57a in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #4 0x0094be23 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #5 0x0094bebd in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #6 0x01ccd872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x01ccdfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x01cce201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x0094c8e7 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #10 0x0091850d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #11 0x009187a9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #12 0x0080194c in QThread::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #13 0x008f5b5d in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #14 0x00804de0 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #15 0x00dbfd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0x001faace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb7758740 (LWP 28924)): [KCrash Handler] #7 0x00e21416 in __kernel_vsyscall () #8 0x0013e1ef in raise () from /lib/i386-linux-gnu/libc.so.6 #9 0x00141835 in abort () from /lib/i386-linux-gnu/libc.so.6 #10 0x001792fa in ?? () from /lib/i386-linux-gnu/libc.so.6 #11 0x00183e42 in ?? () from /lib/i386-linux-gnu/libc.so.6 #12 0x00184525 in ?? () from /lib/i386-linux-gnu/libc.so.6 #13 0x01c4b51f in operator delete(void*) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #14 0x03d9146c in KexiDataSourcePage::~KexiDataSourcePage() () from /usr/lib/libkexiformutils.so.9 #15 0x03d91512 in KexiDataSourcePage::~KexiDataSourcePage() () from /usr/lib/libkexiformutils.so.9 #16 0x03d9359d in KexiFormPart::~KexiFormPart() () from /usr/lib/libkexiformutils.so.9 #17 0x03d93602 in KexiFormPart::~KexiFormPart() () from /usr/lib/libkexiformutils.so.9 #18 0x0092ed11 in QObjectPrivate::deleteChildren() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #19 0x00934481 in QObject::~QObject() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #20 0x0031b145 in KexiPart::Manager::~Manager() () from /usr/lib/libkexicore.so.9 #21 0x002f768d in ?? () from /usr/lib/libkexicore.so.9 #22 0x002fafa9 in ?? () from /usr/lib/libkexicore.so.9 #23 0x00142f61 in ?? () from /lib/i386-linux-gnu/libc.so.6 #24 0x00142fed in exit () from /lib/i386-linux-gnu/libc.so.6 #25 0x001294db in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6 #26 0x08048725 in _start () Possible duplicates by query: bug 302280, bug 300570, bug 299484, bug 298855. Reported using DrKonqi
Thank you for reporting this crash. Unfortunately, we can't do much with it as it is missing debug symbols, so I need to put this on hold. It would be great if you could install them, try to reproduce the crash then and post the complete backtrace here.
Hi, edemco@netonecom.net. Thanks for the report. I see many actions in the report. Could you please explain after which action the report occured, if just once? If you can repeat (reproduce) the crash, please provide the list of actions. If you have database that is causing a crash, you could attach it below too.
Created attachment 73400 [details] attachment-22111-0.html I am sorry, but I do not understand what "debug symbols" are. If they are important, why aren't they installed automatically? This is the first time I entered a bug report and only did so, because the screen prompts made it relatively painless. I'll need some help to comply. On Wed, 2012-08-22 at 19:26 +0000, Janek Bevendorff wrote: > https://bugs.kde.org/show_bug.cgi?id=305605 > > Janek Bevendorff <jbev_kdebugs_01@refining-linux.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > CC| |jbev_kdebugs_01@refining-li > | |nux.org > Resolution|--- |BACKTRACE > > --- Comment #1 from Janek Bevendorff <jbev_kdebugs_01@refining-linux.org> --- > Thank you for reporting this crash. > Unfortunately, we can't do much with it as it is missing debug symbols, so I > need to put this on hold. > It would be great if you could install them, try to reproduce the crash then > and post the complete backtrace here. >
I see that you need four additional pieces of information: 1) I see many actions in the report - As explained in the report, this was my first attempt to use Kexi. 2) Could you please explain after which action the report occurred - I described every step, ending with the point at which the program crashed. 3) If you repeat (reproduce)... - I reopened the database and could not replicate the crash, however, it crashed again as I was about to close the program. 4) If you have the database ... - I've attached the database. Additionally, I tried to install "debug symbols" from the screen prompt, but they would not load. On Wed, 2012-08-22 at 19:37 +0000, Jarosław Staniek wrote: > https://bugs.kde.org/show_bug.cgi?id=305605 > > --- Comment #2 from Jarosław Staniek <staniek@kde.org> --- > Hi, edemco@netonecom.net. Thanks for the report. > > I see many actions in the report. Could you please explain after which action > the report occured, if just once? If you can repeat (reproduce) the crash, > please provide the list of actions. If you have database that is causing a > crash, you could attach it below too. >
Created attachment 73401 [details] attachment-22111-1.dat
Created attachment 73402 [details] New_database.kexi
Under Ubuntu the package "debugging symbols for Calligra" is called calligra-dbg. It may be useful to have it installed if you plan to support the project with better report. And thanks a lot for the excellent detailed explanation and attachments, I'll analyze them :)
PS: If possible I also recommend installing Calligra 2.5.0 or 2.4.3 (if you have no access to 2.5).
I was able to install calligra-dbj, after a fashion; it did not want to install. I have not run Kexi again, but when I do (and if it crashes), do I send the bug report? If so, how should that be sent? Let me know if there is anything else I can help with. On Wed, 2012-08-22 at 21:40 +0000, Jarosław Staniek wrote: > https://bugs.kde.org/show_bug.cgi?id=305605 > > Jarosław Staniek <staniek@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEEDSINFO |ASSIGNED > Resolution|BACKTRACE |--- > Ever confirmed|0 |1 > > --- Comment #7 from Jarosław Staniek <staniek@kde.org> --- > Under Ubuntu the package "debugging symbols for Calligra" is called > calligra-dbg. > > It may be useful to have it installed if you plan to support the project with > better report. > > And thanks a lot for the excellent detailed explanation and attachments, I'll > analyze them :) >
@edemco: To get save backtrace please click Save button on the bottom right of the Developer Information tab; see also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Crash.21
Debugging symbols installation is not needed for this particular crash. Thanks for the info, the crash was reported before for bug 299484. I'll work on fix anyway. *** This bug has been marked as a duplicate of bug 299484 ***