https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #1 from lp.allar...@gmail.com ---
Running version 4.6.4 on Linux mint 17.3 (ubuntu based)
Installed from stock repos.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #2 from lp.allar...@gmail.com ---
I just performed another payment to the credit card account (from my chequing
account) which consists in a simple transfer, and while the memo's content of
the transaction is FINE in the transaction in the ch
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #3 from Thomas Baumgart ---
Can you try to upgrade to a more recent version (e.g. 4.7.2) and see if the
problem persists?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #4 from lp.allar...@gmail.com ---
I am not off to a good start. First I downloaded the sources of 4.7.2 then
followed the instructions of the README.cmake file which mentions that I should
run "sudo apt-get build-dep kmymoney" since I am on
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #5 from allan ---
On 26/03/16 15:55, via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360938
>
> --- Comment #4 from lp.allar...@gmail.com ---
> I am not off to a good start. First I downloaded the sources of 4.7.2 then
> foll
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #6 from lp.allar...@gmail.com ---
Well.. I added the PPA you suggested and upgraded KMM to 4.7.2. First thing I
noticed, it crashes hard when I perform a consistency check. I am storing my
data on a MySQL backend, with about 7800 transactio
https://bugs.kde.org/show_bug.cgi?id=360938
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
|
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #8 from lp.allar...@gmail.com ---
I did a few tests:
created a new flat file (.kmy) and consistency check does not crash with
4.7.2..good
created a new database file with 4.7.2, consistency check does not crash
either. good
Consisten
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #9 from Jack ---
I'm pretty much guessing here, but if you can capture the 27 errors that were
fixed in the smaller version, can you make those corrections manually on the
larger version? If so, you might get farther in then saving the large
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #10 from lp.allar...@gmail.com ---
Hello Jack, I was too quick on the "OK button" and did not have time to
carefully read what was fixed when saving to a flat file.
I'd like to try to manually fix whats wrong in the large database but w
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #11 from lp.allar...@gmail.com ---
I just noticed: the tables "kmmKeyValuePairs" are 64kb in the copied DB, and
2MB in the original DB, and tables "kmmSplits" are 4.9MB in the original DB and
4MB in the copied DB...
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #12 from Jack ---
Well, if you don't have a backup copy of the small database before fixing, then
capturing the fixes is no longer an option.
Different sizes of databases containing the same content does not surprise me
too much - there are
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #13 from lp.allar...@gmail.com ---
Jack, I managed to copy my "production" DB to a "testing" copy and performed a
check for consistency. For whatever reason, it worked, and the output is
rather scary:
* Opening date of Account 'Opening B
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #14 from lp.allar...@gmail.com ---
Then I did another CC on the DB and this time it reported identical output but
at the bottom:
Finished: 0 problems corrected. 111 problems still present.
Im not sure how to proceed from there... Why so muc
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #15 from Jack ---
On 4/2/2016 1:14 PM, via KDE Bugzilla wrote:
> Then I did another CC on the DB and this time it reported identical output but
> at the bottom:
>
> Finished: 0 problems corrected. 111 problems still present.
That is not real
https://bugs.kde.org/show_bug.cgi?id=360938
lp.allar...@gmail.com changed:
What|Removed |Added
Version|unspecified |4.7.2
Severity|critical
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #16 from lp.allar...@gmail.com ---
OK I managed to fix most of the errors CC threw at me. There are still some
errors (6) which is much better than 120...
Another thing, theres a "Equity" account with a sub-account named "Opening
balances".
https://bugs.kde.org/show_bug.cgi?id=360938
lp.allar...@gmail.com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #1 from lp.allar...@gmail.com ---
Running version 4.6.4 on Linux mint 17.3 (ubuntu based)
Installed from stock repos.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #2 from lp.allar...@gmail.com ---
I just performed another payment to the credit card account (from my chequing
account) which consists in a simple transfer, and while the memo's content of
the transaction is FINE in the transaction in the ch
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #3 from Thomas Baumgart ---
Can you try to upgrade to a more recent version (e.g. 4.7.2) and see if the
problem persists?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #4 from lp.allar...@gmail.com ---
I am not off to a good start. First I downloaded the sources of 4.7.2 then
followed the instructions of the README.cmake file which mentions that I should
run "sudo apt-get build-dep kmymoney" since I am on
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #5 from allan ---
On 26/03/16 15:55, via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360938
>
> --- Comment #4 from lp.allar...@gmail.com ---
> I am not off to a good start. First I downloaded the sources of 4.7.2 then
> foll
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #6 from lp.allar...@gmail.com ---
Well.. I added the PPA you suggested and upgraded KMM to 4.7.2. First thing I
noticed, it crashes hard when I perform a consistency check. I am storing my
data on a MySQL backend, with about 7800 transactio
https://bugs.kde.org/show_bug.cgi?id=360938
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
|
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #8 from lp.allar...@gmail.com ---
I did a few tests:
created a new flat file (.kmy) and consistency check does not crash with
4.7.2..good
created a new database file with 4.7.2, consistency check does not crash
either. good
Consisten
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #9 from Jack ---
I'm pretty much guessing here, but if you can capture the 27 errors that were
fixed in the smaller version, can you make those corrections manually on the
larger version? If so, you might get farther in then saving the large
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #10 from lp.allar...@gmail.com ---
Hello Jack, I was too quick on the "OK button" and did not have time to
carefully read what was fixed when saving to a flat file.
I'd like to try to manually fix whats wrong in the large database but w
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #11 from lp.allar...@gmail.com ---
I just noticed: the tables "kmmKeyValuePairs" are 64kb in the copied DB, and
2MB in the original DB, and tables "kmmSplits" are 4.9MB in the original DB and
4MB in the copied DB...
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #12 from Jack ---
Well, if you don't have a backup copy of the small database before fixing, then
capturing the fixes is no longer an option.
Different sizes of databases containing the same content does not surprise me
too much - there are
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #13 from lp.allar...@gmail.com ---
Jack, I managed to copy my "production" DB to a "testing" copy and performed a
check for consistency. For whatever reason, it worked, and the output is
rather scary:
* Opening date of Account 'Opening B
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #14 from lp.allar...@gmail.com ---
Then I did another CC on the DB and this time it reported identical output but
at the bottom:
Finished: 0 problems corrected. 111 problems still present.
Im not sure how to proceed from there... Why so muc
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #15 from Jack ---
On 4/2/2016 1:14 PM, via KDE Bugzilla wrote:
> Then I did another CC on the DB and this time it reported identical output but
> at the bottom:
>
> Finished: 0 problems corrected. 111 problems still present.
That is not real
https://bugs.kde.org/show_bug.cgi?id=360938
lp.allar...@gmail.com changed:
What|Removed |Added
Version|unspecified |4.7.2
Severity|critical
https://bugs.kde.org/show_bug.cgi?id=360938
--- Comment #16 from lp.allar...@gmail.com ---
OK I managed to fix most of the errors CC threw at me. There are still some
errors (6) which is much better than 120...
Another thing, theres a "Equity" account with a sub-account named "Opening
balances".
https://bugs.kde.org/show_bug.cgi?id=360938
lp.allar...@gmail.com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
36 matches
Mail list logo