Summary: | Crash on table building and deleting | ||
---|---|---|---|
Product: | [Applications] KEXI | Reporter: | edemco |
Component: | General | Assignee: | Jarosław Staniek <staniek> |
Status: | CLOSED DUPLICATE | ||
Severity: | crash | CC: | kde |
Priority: | NOR | ||
Version: | 2.4.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
attachment-22111-0.html
attachment-22111-1.dat New_database.kexi |
Description
edemco
2012-08-22 14:17:36 UTC
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 *** |