[kmymoney] [Bug 475666] New: Running Balance and Reconciliation balance do not match

2023-10-15 Thread Jesse via KMyMoney-devel
https://bugs.kde.org/show_bug.cgi?id=475666

Bug ID: 475666
   Summary: Running Balance and Reconciliation balance do not
match
Classification: Applications
   Product: kmymoney
   Version: 5.1.2
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-devel@kde.org
  Reporter: jesgei...@outlook.com
  Target Milestone: ---

Created attachment 162326
  --> https://bugs.kde.org/attachment.cgi?id=162326&action=edit
Reconciliation Balance Screenshots

SUMMARY
***
Running same file on both Win 10 x64 and Debian 12 x64. Only 1 account out of
many (like 50) has this problem. I have searched for an extra $3 transaction
somewhere, but that would then throw off the correct balance. The account
settings do not have any values for balance or limits. There are numerous
transfers to and from other accounts, but they all add up correctly and all
other accounts reconcile perfectly.

The running balance for this account is correct, but when I start the
reconciliation wizard it is off by $3.00, and the cleared balance does not
match the running balance for the end of the statement period. Screenshots in
attached Word doc.

I have also moved ALL transactions for this account to a new account, but the
problem still exists.  I will continue to try other things (I've been playing
around for months) but thought it was time to see if you ran into this before.
***

STEPS TO REPRODUCE
1. No idea except to send my file.

OBSERVED RESULT
1. In screenshots, wizard starting balance does not match previous reconciled
balance for this one account.
2. Reconciliation wizard cleared balance does not match running balance for
statement period.

EXPECTED RESULT
balances should match in the appropriate areas.

SOFTWARE/OS VERSIONS
Edition Windows 10 Pro
Version 22H2
OS build19045.3570
Experience  Windows Feature Experience Pack 1000.19052.1000.0
KMM: Version 5.1.2-99be6bdb1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 475674] New: Create a Lock File when running KMyMoney

2023-10-15 Thread Brendan via KMyMoney-devel
https://bugs.kde.org/show_bug.cgi?id=475674

Bug ID: 475674
   Summary: Create a Lock File when running KMyMoney
Classification: Applications
   Product: kmymoney
   Version: git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-devel@kde.org
  Reporter: 3...@coupe7.com
  Target Milestone: ---

I use KMM on multiple systems. My data file is shared between my various Linux
systems and several backup servers via Synthing.

When I forget to close KMM before opening it on a different system, I can end
up with 2 versions of the KMM data file.

I have created a workaround with a script that starts KMM (kmymoney.sh). It
checks to see if there is a lock file present at the designated path. If the
lock file is present, I use Zenity to display a message that file is already
open on a different system and I display the name of the system where KMM is
already running.

If the lock file is not present, I create the lock file which has the same name
as the KMM data file that I am trying to open plus .lock. The lock file has the
name of the host that is running KMM. Synthing syncs this file to my backup
systems and any system that is online immediately. If I put a system to sleep
without closing KMM, the lock file is still present. If I then wake up or boot
up a different system, it will receive the lock file and prevent me from
running KMM with the same data file.

It would be ideal if KMM handled all of this internally. By default i think the
lock file should be stored in the same path as the data file but it might make
sense to make it configurable. The home directory would not work for my setup
since I do not sync my entire home directory with Syncthing.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 475675] New: Budgeting Reports Need current month and year-to-date option.

2023-10-15 Thread Manfred via KMyMoney-devel
https://bugs.kde.org/show_bug.cgi?id=475675

Bug ID: 475675
   Summary: Budgeting Reports Need current month and year-to-date
option.
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-devel@kde.org
  Reporter: sbrog...@gmail.com
  Target Milestone: ---

SUMMARY

The Budget report section has Budgeted vs Actual This Year.  Users would be
greatly served by having this data for Current month and Year-to-date.  If the
range is changed to current month, the "Actual This Year" is also restricted to
current month. Should be actual year-to-date.

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 475108] New Transaction Crashes App

2023-10-15 Thread Bug Janitor Service via KMyMoney-devel
https://bugs.kde.org/show_bug.cgi?id=475108

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are the assignee for the bug.