Bug 298791 - File created with 4.5.3 crached kmy 4.6
Summary: File created with 4.5.3 crached kmy 4.6
Status: RESOLVED DUPLICATE of bug 290737
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-25 09:08 UTC by mich45tux
Modified: 2012-04-27 22:30 UTC (History)
2 users (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 mich45tux 2012-04-25 09:08:07 UTC
Application: kmymoney (4.6.1)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic i686
Distribution: Ubuntu precise (development branch)

-- Information about the crash:
- What I was doing when the application crashed: Just trying to open a kmy file created with 4.5.3 with this new 4.6 version

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb76e2740 (LWP 3036))]

Thread 3 (Thread 0xb625ab40 (LWP 3038)):
#0  0x00285416 in __kernel_vsyscall ()
#1  0x070e4380 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x02a01a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x029f406e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x029f452b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x03683134 in ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
#6  0x02a17673 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x0025ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x070f2ace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb58ffb40 (LWP 3039)):
#0  0x029f4018 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x029f452b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x03ad40ea in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#3  0x02a17673 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x0025ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#5  0x070f2ace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb76e2740 (LWP 3036)):
[KCrash Handler]
#7  0x03f7c0c4 in __gmpq_mul () from /usr/lib/i386-linux-gnu/libgmp.so.10
#8  0x00148f40 in AlkValue::operator*(AlkValue const&) const () from /usr/lib/libalkimia.so.4
#9  0x0054d57a in MyMoneyMoney::operator* (this=0x674643c, _b=...) at /build/buildd/kmymoney-4.6.1/kmymoney/mymoney/mymoneymoney.cpp:272
#10 0x081a6401 in reports::PivotTable::calculateBudgetMapping (this=0xbf897c7c) at /build/buildd/kmymoney-4.6.1/kmymoney/reports/pivottable.cpp:880
#11 0x081aaca3 in reports::PivotTable::init (this=0xbf897c7c) at /build/buildd/kmymoney-4.6.1/kmymoney/reports/pivottable.cpp:169
#12 0x081ab79c in reports::PivotTable::PivotTable (this=0xbf897c7c, _config_f=...) at /build/buildd/kmymoney-4.6.1/kmymoney/reports/pivottable.cpp:94
#13 0x0816acc5 in KHomeView::showBudget (this=0x8dc9848) at /build/buildd/kmymoney-4.6.1/kmymoney/views/khomeview.cpp:1342
#14 0x08172bd8 in KHomeView::loadView (this=0x8dc9848) at /build/buildd/kmymoney-4.6.1/kmymoney/views/khomeview.cpp:278
#15 0x08173e20 in KHomeView::slotLoadView (this=0x8dc9848) at /build/buildd/kmymoney-4.6.1/kmymoney/views/khomeview.cpp:171
#16 0x065fe6b1 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#17 0x005753b5 in MyMoneyFile::dataChanged (this=0x5e6620) at /build/buildd/kmymoney-4.6.1/obj-i686-linux-gnu/kmymoney/mymoney/mymoneyfile.moc:113
#18 0x00589061 in MyMoneyFile::attachStorage (this=0x5e6620, storage=0x94e3bc8) at /build/buildd/kmymoney-4.6.1/kmymoney/mymoney/mymoneyfile.cpp:329
#19 0x080fc923 in KMyMoneyView::readFile (this=0x8dbf560, url=...) at /build/buildd/kmymoney-4.6.1/kmymoney/views/kmymoneyview.cpp:828
#20 0x080cba5f in KMyMoneyApp::slotFileOpenRecent (this=0x8b82538, url=...) at /build/buildd/kmymoney-4.6.1/kmymoney/kmymoney.cpp:1520
#21 0x0808a506 in runKMyMoney (splash=0xbf8988a0, a=<optimized out>) at /build/buildd/kmymoney-4.6.1/kmymoney/main.cpp:269
#22 0x080889db in main (argc=<error reading variable: Cannot access memory at address 0x0>, argv=<error reading variable: Cannot access memory at address 0x4>) at /build/buildd/kmymoney-4.6.1/kmymoney/main.cpp:181

Possible duplicates by query: bug 297271, bug 296297, bug 290872.

Reported using DrKonqi
Comment 1 allan 2012-04-25 16:24:28 UTC
To try and get you working again, here's a recent suggestion on dealing with
this type of problem:-
"First, try to run kmymoney from the command line with "kmymoney -n" which will
start the program without opening a kmy file.  Then select
Settings/ConfigureKMyMoney from the menu bar.  Click on "Home" (the second
icon) on the left side, and remove the check from all the items on the right. 
Accept the changes, then open your data file.  If it opens the file, select 
Tools / Consistency Check from the menu bar.  (Hopefully you can find the
correct menu items in translation.)  The consistency check may find problems
that have managed to get into the data file - but many of them can be fixed, so
post here what the results are.
Jack "
Comment 2 mich45tux 2012-04-25 17:07:23 UTC
Le 25/04/2012 18:24, allan a écrit :
> https://bugs.kde.org/show_bug.cgi?id=298791
>
> allan<agander93@gmail.com>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |agander93@gmail.com
>
> --- Comment #1 from allan<agander93@gmail.com>  ---
> To try and get you working again, here's a recent suggestion on dealing with
> this type of problem:-
> "First, try to run kmymoney from the command line with "kmymoney -n" which will
> start the program without opening a kmy file.  Then select
> Settings/ConfigureKMyMoney from the menu bar.  Click on "Home" (the second
> icon) on the left side, and remove the check from all the items on the right.
> Accept the changes, then open your data file.  If it opens the file, select
> Tools / Consistency Check from the menu bar.  (Hopefully you can find the
> correct menu items in translation.)  The consistency check may find problems
> that have managed to get into the data file - but many of them can be fixed, so
> post here what the results are.
> Jack "
>
Thanks for the quick answer
I followed all this procedure and now ... it works
However, the consistency ckeck didn't discover any bad data, it said.
Best regards.
Michel
Comment 3 allan 2012-04-25 17:52:00 UTC
Glad you're working again.

It may have been a problem in a saved report, but at least your base data is OK.
Comment 4 Alvaro Soliverez 2012-04-27 22:30:36 UTC

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