Summary: | Crash when categorizing multiple transactions [Q3TableHeader::isSectionStretchable, Q3Table::hideRow, KMyMoneyRegister::RegisterItem::setVisible] | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Christian Schmitt <chrschmitt> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, inga.herber, Regnaron |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christian Schmitt
2010-01-09 16:21:14 UTC
From bug 222832: -- What I was doing before the crash occured: - I had a (recurring) scheduled transaction that was due be booked on the 18th. - I entered it using the shortcut of the "upcoming transactions". - I then cleared the transaction in the account. - I changed the date of the (now cleared) transaction from the 18th to the 15th (today). - Upon hitting enter to confirm my modifications, kmymoney crashed with the backtrace below -- Backtrace: #5 0x00007f5b5bfda21d in Q3TableHeader::isSectionStretchable (this=0x312eb00, s=0) at itemviews/q3table.cpp:7243 #6 0x00007f5b5bfdfccf in Q3Table::hideRow (this=0x312cba0, row=0) at itemviews/q3table.cpp:5604 #7 0x0000000000788bf2 in KMyMoneyRegister::RegisterItem::setVisible (this=0x3b3eb20, visible=<value optimized out>) at /home/oliver/kmymoney-3.95.0/kmymoney/widgets/registeritem.cpp:99 #8 0x000000000078befb in KMyMoneyRegister::Transaction::setVisible (this=0x312eb00, visible=false) at /home/oliver/kmymoney-3.95.0/kmymoney/widgets/transaction.cpp:808 #9 0x00000000007479f7 in KMyMoneyRegister::RegisterSearchLine::itemAdded (this=0x34e7e20, item=0x3b3eb20) at /home/oliver/kmymoney-3.95.0/kmymoney/widgets/registersearchline.cpp:234 *** Bug 222832 has been marked as a duplicate of this bug. *** Can you check if the problem still persists? I made some changes due to bug 222927 which seem to be related. It looks like a (display) filter had been setup and the crash happened when the filter hit upon reloading the register. The filter though was not mentioned in any of the descriptions and it could be that it is why I was not able to duplicate the problem. If we have positive confirmation that this bug is gone, we can mark it as a duplicate to bug 222927. The original poster confirmed the fix on IRC. *** This bug has been marked as a duplicate of bug 222927 *** *** Bug 227989 has been marked as a duplicate of this bug. *** |