Application: kexi (2.9.11) KDE Platform Version: 4.14.24 Qt Version: 4.8.7 Operating System: Linux 4.7.6-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I open newly created project. Then click button creating new object of type "Script". Kexi crash every time when I do it. The crash can be reproduced every time. -- Backtrace: Application: Kexi (kexi), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #6 0x0000000002051468 in ?? () #7 0x00007f0be720901f in KexiEditor::defaultContextMenu() () from /usr/lib/libkexiextendedwidgets.so.14 #8 0x00007f0bc2d060c8 in KexiScriptDesignView::KexiScriptDesignView(QWidget*, Kross::Action*) () from /usr/lib/kde4/kexihandler_script.so #9 0x00007f0bc2d02584 in KexiScriptPart::createView(QWidget*, KexiWindow*, KexiPart::Item&, Kexi::ViewMode, QMap<QString, QVariant>*) () from /usr/lib/kde4/kexihandler_script.so #10 0x00007f0be9198eed in KexiWindow::switchToViewMode(Kexi::ViewMode, QMap<QString, QVariant>*, bool&) () from /usr/lib/libkexicore.so.14 #11 0x00007f0be91a669d in KexiPart::Part::openInstance(QWidget*, KexiPart::Item&, Kexi::ViewMode, QMap<QString, QVariant>*) () from /usr/lib/libkexicore.so.14 #12 0x00007f0be918f463 in KexiProject::openObject(QWidget*, KexiPart::Item&, Kexi::ViewMode, QMap<QString, QVariant>*) () from /usr/lib/libkexicore.so.14 #13 0x00007f0be946d203 in KexiMainWindow::openObject(KexiPart::Item*, Kexi::ViewMode, bool&, QMap<QString, QVariant>*, QString*) () from /usr/lib/libkeximain.so.14 #14 0x00007f0be945577e in KexiMainWindow::newObject(KexiPart::Info*, bool&) () from /usr/lib/libkeximain.so.14 #15 0x00007f0be94713fc in ?? () from /usr/lib/libkeximain.so.14 #16 0x00007f0be7bcec50 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #17 0x00007f0be919f9a2 in KexiPart::Manager::newObjectRequested(KexiPart::Info*) () from /usr/lib/libkexicore.so.14 #18 0x00007f0be7bcec50 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #19 0x00007f0be91a487f in KexiNewObjectAction::newObjectRequested(KexiPart::Info*) () from /usr/lib/libkexicore.so.14 #20 0x00007f0be7bcec50 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #21 0x00007f0be8122082 in QAction::triggered(bool) () from /usr/lib/libQtGui.so.4 #22 0x00007f0be81233e3 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQtGui.so.4 #23 0x00007f0be84fe2f3 in ?? () from /usr/lib/libQtGui.so.4 #24 0x00007f0be84fe444 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4 #25 0x00007f0be85c3a7a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4 #26 0x00007f0be817e840 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #27 0x00007f0be8127f2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #28 0x00007f0be81305b7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #29 0x00007f0be5bf32fa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #30 0x00007f0be7bbab2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #31 0x00007f0be812e5db in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/libQtGui.so.4 #32 0x00007f0be81a9a89 in ?? () from /usr/lib/libQtGui.so.4 #33 0x00007f0be81a843c in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #34 0x00007f0be81d0db2 in ?? () from /usr/lib/libQtGui.so.4 #35 0x00007f0be3bd2e67 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0x00007f0be3bd30d0 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0x00007f0be3bd317c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #38 0x00007f0be7beaeee in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #39 0x00007f0be81d0e86 in ?? () from /usr/lib/libQtGui.so.4 #40 0x00007f0be7bb93ff in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #41 0x00007f0be7bb9765 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #42 0x00007f0be7bbf1c9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #43 0x0000000000400979 in main () Reported using DrKonqi
Hi, thanks for reporting, Wiktor. I don't see a full backtrace (here's info how to get them: https://userbase.kde.org/Asking_Questions#Reporting_KDE_Bugs), so these are only guesses: you may miss a 3rd-party KTextEditor component that implements text editor that we're using in the scripting window. The same component is used in the SQL view of the Query Designer, it would be useful to hear from you if it works for you or not. To test if you have the component, please try to run Kate or KWrite app. Of course Kexi should tell you about missing components instead of crashing, I'll look at methods to do that. (if this helps, please also note, scripting is experimental in Kexi 2 and also 2.9.11 is the last official release of Kexi 2)
> I don't see a full backtrace Unfortunately users of Arch Linux don't get pre-compiled packages with KDE debug symbols. I try to build kexi myself with them. Until then I won't be able to provide more useful output :( . > you may miss a 3rd-party KTextEditor KWrite is working and Kate is my default editor, which I use all the time.
> Unfortunately users of Arch Linux don't get pre-compiled packages with KDE debug symbols. Thanks. It would be good if the Arch maintainers know it's a misfeature/bug that a kind of stays against our rules of development process and contributions. Yes, I do recommend compiling Kexi to get frequent updates. At least until portable Kexi SNAP packages or alike are shipped. By the way, only Kexi 3 gets updates now, so it makes more sense to compile Kexi 3 from kexi.git, not Kexi 2 from calligra.git.
By the way, if you're interesting in scripting, we're planning to have a completely new Scripting module and the language will be Javascript; functionally it would still use similar editor and approach. The home page of Scripting development is https://community.kde.org/Kexi/Plugins/Scripts.
It's a know problem for years and nothings shows that Arch will gain precompiled debugging symbols. Also, I've got now Kexi 3 after today's upgrade, and now I don's see 'Scripts' button. Should I close this ticket?
(In reply to Jarosław Staniek from comment #4) > By the way, if you're interesting in scripting, we're planning to have a > completely new Scripting module and the language will be Javascript; > functionally it would still use similar editor and approach. > The home page of Scripting development is > https://community.kde.org/Kexi/Plugins/Scripts. I read yesterday on Postgres wiki that Kexi can operate on existing DB. I was searching for an app that could be used to prepare some report / visualization and checked if Kexi is OK. Then clicked 'Scripts' and it crashed so I decided to report bug.
> I read yesterday on Postgres wiki that Kexi can operate on existing DB. Answered here https://forum.kde.org/viewtopic.php?f=221&t=136624
That experimental scripting is disabled in Kexi 3. I see possibility of adding some extra checks to the GUI though, as it's probable that the same editor will be used with the new scripting feature. For 2.9 this bug can be closed as 2.9 would not receive this kind of fixes. Doing that now.