| Summary: | Kexi crash when trying to add script in new project | ||
|---|---|---|---|
| Product: | [Applications] KEXI | Reporter: | Wiktor <wikt.sztw+kdebugs> |
| Component: | Scripting | Assignee: | Kexi Bugs <kexi-bugs> |
| Status: | CLOSED UPSTREAM | ||
| Severity: | crash | CC: | adam, inksi, staniek |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 2.9.11 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Wiktor
2016-10-05 13:39:14 UTC
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. |