Bug 352224 - Kexi crash in forms
Summary: Kexi crash in forms
Status: RESOLVED WORKSFORME
Alias: None
Product: KEXI
Classification: Applications
Component: Forms (show other bugs)
Version: 2.9.5
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2015-09-03 14:35 UTC by minimerrill
Modified: 2018-10-27 04:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-22080-0.html (1.83 KB, text/html)
2015-09-03 16:07 UTC, minimerrill
Details

Note You need to log in before you can comment on or make changes to this bug.
Description minimerrill 2015-09-03 14:35:40 UTC
Application: kexi (2.9.5)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 4.0.0-2-amd64 x86_64
Distribution: Tanglu GNU/Linux 3 (Chromodoris willani)

-- Information about the crash:
When I am in a form and I am looking at the data view, if I select a widget and click tab, it crashes. I've done this with different widgets with a consistent crash each time.

The crash can be reproduced every time.

-- Backtrace:
Application: Kexi (kexi), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f8da47ac9bd in KexiDBForm::eventFilter(QObject*, QEvent*) () from /usr/lib/libkexiformutils.so.14
#7  0x00007f8dd381b886 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007f8dd3d4b46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007f8dd3d536f6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007f8dd189831a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#11 0x00007f8dd381b71d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007f8dd3d7f139 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007f8dd3d5377e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00007f8dd189831a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0x00007f8dd381b71d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x00007f8dd3ded353 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#17 0x00007f8dd3ded7f2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#18 0x00007f8dd3dc719f in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x00007f8dd3defed2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x00007f8dcf0a1f2d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f8dcf0a2210 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f8dcf0a22bc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f8dd384ad1d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x00007f8dd3deff96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x00007f8dd381a271 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x00007f8dd381a5d5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x00007f8dd3820059 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x0000000000400951 in ?? ()
#29 0x00007f8dd330db45 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#30 0x00000000004009b4 in _start ()

Reported using DrKonqi
Comment 1 Jarosław Staniek 2015-09-03 15:08:11 UTC
Hello!
Thanks for the report. To finish the details would you think it is possible to attach a screenshot to show what tab are you clicking?

A sample database file with form that crashes could also speed up things. 
Thanks!
Comment 2 minimerrill 2015-09-03 16:07:36 UTC
Created attachment 94375 [details]
attachment-22080-0.html

My apologies, I guess I wasn't clear. When I press the 'TAB' button on the
keyboard while a widget is selected, Kexi crashes.

On Thu, Sep 3, 2015 at 12:08 PM, Jarosław Staniek <staniek@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=352224
>
> Jarosław Staniek <staniek@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |staniek@kde.org
>              Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>             Summary|Kexi Crash                  |Kexi crash in forms
>           Component|General                     |Forms
>
> --- Comment #1 from Jarosław Staniek <staniek@kde.org> ---
> Hello!
> Thanks for the report. To finish the details would you think it is
> possible to
> attach a screenshot to show what tab are you clicking?
>
> A sample database file with form that crashes could also speed up things.
> Thanks!
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Jarosław Staniek 2015-09-03 16:14:38 UTC
What exactly type of widget is this? Text Box, Text Editor, Button, etc.?

As I wrote before, example .kexi file would be best.
Comment 4 Andrew Crouthamel 2018-09-25 21:54:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 04:09:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!