Bug 246673 - Crash on tabbing in the split transaction editor
Summary: Crash on tabbing in the split transaction editor
Status: RESOLVED DUPLICATE of bug 244962
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-04 06:26 UTC by alexander.dunaev
Modified: 2010-09-05 11:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alexander.dunaev 2010-08-04 06:26:09 UTC
Application: kmymoney (3.98.1)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-5-amd64 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

-- Information about the crash:
I have entered several entries in a split transaction and then decided to edit the entry.  I have pressed F2 to begin editing, then pressed Shift+Tab to switch focus to a previous control in the dialog.  The applicatin has crashed.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault
The current source language is "auto; currently asm".
[KCrash Handler]
#5  QWidget::focusPolicy (this=0x100000001) at kernel/qwidget.cpp:7012
#6  0x00000000006fe3d1 in ?? ()
#7  0x00007ff052982d33 in QWidget::event (this=0x97083b0, event=0x7fff549944f0) at kernel/qwidget.cpp:8073
#8  0x00007ff05292d32c in QApplicationPrivate::notify_helper (this=0x1002c40, receiver=0x97083b0, e=0x7fff549944f0) at kernel/qapplication.cpp:4302
#9  0x00007ff052934fc5 in QApplication::notify (this=<value optimized out>, receiver=0x97083b0, e=0x7fff549944f0) at kernel/qapplication.cpp:3765
#10 0x00007ff055c2f436 in KApplication::notify (this=0x1002710, receiver=0x97083b0, event=0x7fff549944f0) at ../../kdeui/kernel/kapplication.cpp:302
#11 0x00007ff05358d15c in QCoreApplication::notifyInternal (this=0x1002710, receiver=0x97083b0, event=0x7fff549944f0) at kernel/qcoreapplication.cpp:726
#12 0x00007ff0529d7d1a in QKeyMapper::sendKeyEvent (keyWidget=0x97083b0, grab=<value optimized out>, type=QEvent::KeyPress, code=16777218, modifiers=<value optimized out>, text=..., 
    autorepeat=false, count=1, nativeScanCode=23, nativeVirtualKey=65056, nativeModifiers=8193) at kernel/qkeymapper_x11.cpp:1875
#13 0x00007ff0529da291 in QKeyMapperPrivate::translateKeyEvent (this=0x103c250, keyWidget=0x97083b0, event=<value optimized out>, grab=5) at kernel/qkeymapper_x11.cpp:1845
#14 0x00007ff0529b1a04 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff549950a0) at kernel/qapplication_x11.cpp:3406
#15 0x00007ff0529dd552 in x11EventSourceDispatch (s=0x1006a50, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#16 0x00007ff04e2dc6c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#17 0x00007ff04e2e0538 in ?? () from /lib/libglib-2.0.so.0
#18 0x00007ff04e2e06ec in g_main_context_iteration () from /lib/libglib-2.0.so.0
#19 0x00007ff0535b6713 in QEventDispatcherGlib::processEvents (this=0xfe1fb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#20 0x00007ff0529dd14e in QGuiEventDispatcherGlib::processEvents (this=0x100000001, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#21 0x00007ff05358ba82 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#22 0x00007ff05358be5c in QEventLoop::exec (this=0x7fff549953c0, flags=) at kernel/qeventloop.cpp:201
#23 0x00007ff052df7e7e in QDialog::exec (this=0x49d5580) at dialogs/qdialog.cpp:546
#24 0x00000000006c6247 in ?? ()
#25 0x00000000006e095d in ?? ()
#26 0x00000000006ee61d in ?? ()
#27 0x00007ff0535a0346 in QMetaObject::activate (sender=0x2bbbbe0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x3ac5fd0) at kernel/qobject.cpp:3295
#28 0x00007ff052fca572 in QAbstractButton::clicked (this=0x100000001, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206
#29 0x00007ff052ce2a5b in QAbstractButtonPrivate::emitClicked (this=0x2bbc9b0) at widgets/qabstractbutton.cpp:546
#30 0x00007ff052ce38fb in QAbstractButtonPrivate::click (this=0x2bbc9b0) at widgets/qabstractbutton.cpp:539
#31 0x00007ff052ce3b6c in QAbstractButton::mouseReleaseEvent (this=0x2bbbbe0, e=0x7fff54996770) at widgets/qabstractbutton.cpp:1121
#32 0x00007ff052983602 in QWidget::event (this=0x2bbbbe0, event=0x7fff54996770) at kernel/qwidget.cpp:8044
#33 0x00007ff05292d32c in QApplicationPrivate::notify_helper (this=0x1002c40, receiver=0x2bbbbe0, e=0x7fff54996770) at kernel/qapplication.cpp:4302
#34 0x00007ff052933fdb in QApplication::notify (this=0x1002710, receiver=0x2bbbbe0, e=0x7fff54996770) at kernel/qapplication.cpp:3867
#35 0x00007ff055c2f436 in KApplication::notify (this=0x1002710, receiver=0x2bbbbe0, event=0x7fff54996770) at ../../kdeui/kernel/kapplication.cpp:302
#36 0x00007ff05358d15c in QCoreApplication::notifyInternal (this=0x1002710, receiver=0x2bbbbe0, event=0x7fff54996770) at kernel/qcoreapplication.cpp:726
#37 0x00007ff0529331be in QCoreApplication::sendEvent (receiver=0x2bbbbe0, event=0x7fff54996770, alienWidget=0x2bbbbe0, nativeWidget=0x16b57e0, buttonDown=<value optimized out>, 
    lastMouseReceiver=<value optimized out>, spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#38 QApplicationPrivate::sendMouseEvent (receiver=0x2bbbbe0, event=0x7fff54996770, alienWidget=0x2bbbbe0, nativeWidget=0x16b57e0, buttonDown=<value optimized out>, 
    lastMouseReceiver=<value optimized out>, spontaneous=true) at kernel/qapplication.cpp:2967
#39 0x00007ff0529b303b in QETWidget::translateMouseEvent (this=0x16b57e0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4380
#40 0x00007ff0529b19ac in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff54996ef0) at kernel/qapplication_x11.cpp:3513
#41 0x00007ff0529dd552 in x11EventSourceDispatch (s=0x1006a50, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#42 0x00007ff04e2dc6c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#43 0x00007ff04e2e0538 in ?? () from /lib/libglib-2.0.so.0
#44 0x00007ff04e2e06ec in g_main_context_iteration () from /lib/libglib-2.0.so.0
#45 0x00007ff0535b6713 in QEventDispatcherGlib::processEvents (this=0xfe1fb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#46 0x00007ff0529dd14e in QGuiEventDispatcherGlib::processEvents (this=0x100000001, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#47 0x00007ff05358ba82 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#48 0x00007ff05358be5c in QEventLoop::exec (this=0x7fff54997210, flags=) at kernel/qeventloop.cpp:201
#49 0x00007ff053590aeb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#50 0x000000000045ca58 in _start ()

This bug may be a duplicate of or related to bug 244962.

Possible duplicates by query: bug 244962.

Reported using DrKonqi
Comment 1 Alvaro Soliverez 2010-08-04 11:38:25 UTC
I can't reproduce it here. This appears to have been fixed in the meantime. A lot of fixes have gone into that area since the latest release.
Can you try with the latest SVN revision?
Comment 2 alexander.dunaev 2010-08-09 13:06:11 UTC
Great news about the fixes--how soon will the Debian repository be updated?  I use the testing branch.

How to try the latest SVN revision?  I use the binary package from the official repository, and I use the program for my home accounting, so I'd like to be sure that I don't mess things playing with the SVN version.

(I'm sorry for a delay with the reponse.)
Comment 3 Thomas Baumgart 2010-08-09 14:44:32 UTC
SVN is currently in feature freeze (and soon in total freeze) for the stable release coming up next weekend. Chances are very low that this will screw up your data. So if you are desperate enough to run 3.98.1 (which is an unstable release) you should be on the safer side to use SVN HEAD at the moment. Keeping backups of the data file is always a good idea 

You can obtain the KMyMoney sources from the KDE SVN repository via

  svn checkout svn://anonsvn.kde.org/home/kde/trunk/extragear/office/kmymoney

You may want to consult the README.cmake file to get more details on how to build the project.
Comment 4 Alvaro Soliverez 2010-08-29 17:01:31 UTC
You should have the latest version in Debian testing already. Can you check whether this still happens?
Comment 5 Cristian Oneț 2010-09-05 11:00:27 UTC

*** This bug has been marked as a duplicate of bug 244962 ***