Bug 258974

At pivottable.cpp:555 there is this instruction:
int segment = (m_beginDate.month() - 1) / columnpitch; 
I'm suspecting that columnpitch is 0.

In this case, for columnPith to be 0, there should be something wrong with the saved report.

Does this happen with any report or only with a specific one?

Yep, it seems that the report editing went somehow wrong. Could you post the output of the following command:
zcat yourefile.kmy | grep "columntype="

Here it is:

zcat bank/banking/schunka.kmy |grep
"columntype="

  <REPORT datelock="next3months" comment="Vlastní výkaz" detail="total"
charttype="bar" tax="0" chartgridlines="1" includesprice="0"
includestransfers="1" chartdatalabels="1" investments="0" chartbydefault="0"
columnsaredays="1" includesaverageprice="0" rowtype="assetliability"
convertcurrency="1" group="Forecast" type="pivottable 1.15" id="R000003"
showrowtotals="0" includeunused="1" name="Předpověd pro následující
čtvrtletí(Přizpůsobeno)" includeschedules="1" loans="0" favorite="1"
columntype="weeks" chartlinewidth="2" includesmovingaverage="0"
includesforecast="1" includesactuals="0" >
  <REPORT datelock="next3months" comment="Vlastní výkaz" detail="total"
charttype="bar" tax="0" chartgridlines="0" includesprice="0"
includestransfers="0" chartdatalabels="1" investments="0" chartbydefault="1"
columnsaredays="0" includesaverageprice="0" rowtype="assetliability"
convertcurrency="1" group="" type="pivottable 1.15" id="R000006"
showrowtotals="0" includeunused="0" name="Předpověď čistého
jmění(Přizpůsobeno)" includeschedules="0" loans="0" favorite="0"
columntype="months" chartlinewidth="2" includesmovingaverage="0"
includesforecast="1" includesactuals="0" >
  <REPORT datelock="yeartodate" comment="Vlastní výkaz" detail="all"
charttype="pie" tax="0" chartgridlines="1" includesprice="0"
includestransfers="0" chartdatalabels="1" investments="0" chartbydefault="1"
columnsaredays="0" includesaverageprice="0" rowtype="expenseincome"
convertcurrency="1" group="Income and Expenses" type="pivottable 1.15"
id="R000008" showrowtotals="0" includeunused="0" name="Koláčový graf příjmů
a výdajů(Přizpůsobeno)" includeschedules="0" loans="0" favorite="0"
columntype="months" chartlinewidth="2" includesmovingaverage="0"
includesforecast="0" includesactuals="0" >

I don't know if it helps but I used an older version where I made this
reports (don't know exactly but some 1.something version of kmymoney) and
for like 2 months ago I installed new one, to be precise, version 4.5.0.


2010/12/6 Cristian Onet <onet.cristian@gmail.com>

> https://bugs.kde.org/show_bug.cgi?id=258974
>
>
>
>
>
> --- Comment #3 from Cristian Onet <onet cristian gmail com>  2010-12-06
> 12:17:08 ---
> Yep, it seems that the report editing went somehow wrong. Could you post
> the
> output of the following command:
> zcat yourefile.kmy | grep "columntype="
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

It seems that all your custom reports have a valid column type. Can you recall which one of these where you customizing when the crash occurred?

I think I know what that is. The budget reports don't support the weeks period anymore. 
Can you try to customize a standard report again to make it look like you want?

Anyone, whenever I customize a report. No matter if default one or
previously customized. Application crashes.

I also use cz-cs locales.

So the upgrade to newer version could not cause the trouble?

Only error popping up whenever crash happens is something aboutlist null
pointer exception.

Anyway, I'm glad for any help.

Dne 6.12.2010 22:29 "Cristian Onet" <onet.cristian@gmail.com> napsal/a:

https://bugs.kde.org/show_bug.cgi?id=258974




--- Comment #5 from Cristian Onet <onet cristian gmail com>  2010-12-06
22:30:17 ---
It seems that all your custom reports have a valid column type. Can you
recall
which one of these where you customizing when the crash occurred?

--

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail ...

Could you try switching to English and perform the same operation? Maybe it's a translation related issue.

That helps, but I noticed that stack bar type of chart didn't show any
numbers on the axis, so it's almost useless. The bar type have to be redrawn
to show them correctly. Problem of having kmymoney in english is fine for
me, if it will work, but locales are taken from environment settings. That
would mean all KDE stuff in english, which I choose not to. Is there any way
I can change translation just for kmymoney? And is there any way to fix the
translation problem so in the future I can use kmymoney in my native
language?

2010/12/7 Cristian Onet <onet.cristian@gmail.com>

> https://bugs.kde.org/show_bug.cgi?id=258974
>
>
>
>
>
> --- Comment #8 from Cristian Onet <onet cristian gmail com>  2010-12-07
> 09:28:16 ---
> Could you try switching to English and perform the same operation? Maybe
> it's a
> translation related issue.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

Try starting kmymoney from the commandline as follows:

  kmymoney --lang=C

That should do it (I have never tested it though due to the lack of a translated KDE installation). Alternatively, try --lang=en_GB

There is no need for you to switch the KDE locale for this. Now that we know
how to reproduce the problem (use the Czech translation) we can come up with a
fix for the this. Until then you can switch only KMyMoney's translation (not
locale) to English from the settings menu.

I just got to try out KMyMoney with the Czech translation and didn't succeeded to crash it by customizing reports. Since your is the only setup that is able to reproduce this any extra hints would be welcome. You've said that the same application is working fine when using the English translation, did you change only the language or also the country settings?

*** Bug 262140 has been marked as a duplicate of this bug. ***

This bug doesn't appear with option --lang=C.
Didn't occur during more hours work and many changes in reports.

*** Bug 268391 has been marked as a duplicate of this bug. ***

So this happens with Czech and Danish we have to take a look why a translation could cause a crash in that area.

SVN commit 1232929 by conet:

BUG: 258974

Prevent two different translations of an entity that is referenced by the translated string. Is something is still wrong after this fix don't crash anyway output a warning instead.

 M  +7 -7      dialogs/kreportconfigurationfilterdlg.cpp  
 M  +6 -0      reports/pivottable.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1232929

I think there's a problem in the way we handle the combo. We are comparing by the value of the translated string, instead of by an enum. We should change that to fix it for good.

(In reply to comment #18)
> I think there's a problem in the way we handle the combo. We are comparing by
> the value of the translated string, instead of by an enum. We should change
> that to fix it for good.

If we make sure that there is now way that the translated strings could differ from the two point we reference the values (combo definition vs. combo result usage) from my point of view using an enum is the same thing. I admit though that it would be a bit nicer.

*** Bug 263606 has been marked as a duplicate of this bug. ***