[kmymoney] [Bug 475674] Create a Lock File when running KMyMoney
https://bugs.kde.org/show_bug.cgi?id=475674 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 474004] Display a few more information in the payee view
https://bugs.kde.org/show_bug.cgi?id=474004 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com --- Comment #4 from Jonatan Cloutier --- (In reply to Jack from comment #3) > In terms of adding columns to the payee list, real estate is limited, so I > don't think I would want to add more than one, or risk the display being too > crowded. In that case, I'm not sure that any single additional column would > actually be useful. Just adding my thought here. I actually believe all 5 data suggested would be valuable in the table. Those column should be sortable and customization like the account or category list. So maybe only one added by default (balance?) but all other could be added by the users. In terms of real estate, the list and detail pane could easily be 50/50 by default which is still easily usable on standard hd display that most people have nowadays. Finally, here are my use cases for all 5 data. it mostly turns around being able to clean up the list to merge payee (which is currently quite a cumbersome task when importing from bank accounts): - Creation date of the payee in KMyMoney or date of the earliest transaction booked on the payee => when sorted, we can look at the latest created payee to make sure they are not duplicate or more generally that all their info are correct. (Understand the 1st one is not to be expected in the short term.) - date of latest transaction booked on the payee => same as previous if we want to review recently used payee - Current number of transactions booked on the payee and current balance total of the payee => when ordered (and maybe filtered) see which payee is used more to know in which to merge the transaction. Could also be used to clean up almost unused payee (I tend to group single usage payee together, like occasional convenience store, I don't care exactly which one) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469019] Payees match on a blank field
https://bugs.kde.org/show_bug.cgi?id=469019 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com --- Comment #2 from Jonatan Cloutier --- Line feed is another one. I had a couple of payee that got imported with a line feed at some point and it does create a few issue in the ui and in the match rules. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468633] segfault when hidding reconciliated transacion
https://bugs.kde.org/show_bug.cgi?id=468633 --- Comment #4 from Jonatan Cloutier --- I confirm it's fixed, thank you -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468633] New: segfault when hidding reconciliated transacion
https://bugs.kde.org/show_bug.cgi?id=468633 Bug ID: 468633 Summary: segfault when hidding reconciliated transacion Classification: Applications Product: kmymoney Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- Application: kmymoney (5.1.80-) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.8-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: When on the ledger with reconciled. If I got on the view menu and select "hide reconcilated transaction" (my own translation) KMyMoney crash. This is using the master from today The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault [KCrash Handler] #4 0x55ec99af17d8 in LedgerViewSettings::hideTransactionsBefore() const (this=0x55eca32c16a0) at /build/kmymoney/views/ledgerviewsettings.cpp:130 #5 0x55ec99add021 in ::operator() (__closure=0x55eca2f01760, __closure=0x55eca2f01760) at /build/kmymoney/views/ledgerviewpage.cpp:126 #6 QtPrivate::FunctorCall, QtPrivate::List<>, void, LedgerViewPage::initModel():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #7 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #8 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55eca2f01750, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #9 0x7f4b430bea71 in () at /usr/lib/libQt5Core.so.5 #10 0x7f4b430bea71 in () at /usr/lib/libQt5Core.so.5 #11 0x7f4b430c0fcf in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #12 0x7f4b430b1b56 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7f4b43d78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f4b4308df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f4b430d84b3 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #16 0x7f4b430d8aaa in () at /usr/lib/libQt5Core.so.5 #17 0x7f4b40b0f53b in g_main_dispatch (context=0x7f4b2ee0) at ../glib/glib/gmain.c:3460 #18 g_main_context_dispatch (context=0x7f4b2ee0) at ../glib/glib/gmain.c:4200 #19 0x7f4b40b6c219 in g_main_context_iterate.constprop.0 (context=0x7f4b2ee0, block=1, dispatch=1, self=) at ../glib/glib/gmain.c:4276 #20 0x7f4b40b0e1a2 in g_main_context_iteration (context=0x7f4b2ee0, may_block=1) at ../glib/glib/gmain.c:4343 #21 0x7f4b430d8c6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #22 0x7f4b430866ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x7f4b43091219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #24 0x55ec9982443d in runKMyMoney(QUrl const&, bool, QApplication&) (file=..., noFile=noFile@entry=false, a=...) at /build/kmymoney/main.cpp:384 #25 0x55ec9981e6a7 in main(int, char**) (argc=, argv=) at /build/kmymoney/main.cpp:293 [Inferior 1 (process 3813812) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #20 from Jonatan Cloutier --- > In addition, closing and then opening the file in this state shows the delay > when first displaying the ledger. Forgot to mention that behavior, I believe the first ledger tab get rendered even if we go straight to another account(ie from the home page), which I guess is fine if really quick, but not quite necessary. With the current issue, it create the delay even if opening a small amount that is not affected. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 Jonatan Cloutier changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #17 from Jonatan Cloutier --- I found a small account that show the performance issue on a small scale so I was able to do a bunch of (not quite scientific) tests, I still did all of them twice in a row to confirm, unless noted, reverted the previous change: original settings (as in above attachment): 11 sec nothing checked in settings -> ledger -> display: 11 sec Hiding reconciled transaction: 18 sec *note 1* settings -> ledger -> display -> Don't show reconciliation entries : instant settings -> ledger -> display -> Show last reconciliation entry... : instant original was settings -> ledger -> display -> Show all reconciliation entries... : 11sec *note 2* settings -> ledger -> display -> Show last reconciliation entry... and Hiding reconciled transaction : instant settings -> ledger -> filter -> by type first: 6 sec, although it does remove the header by definition settings -> ledger -> filter -> by payee first: 6sec, which also remove the header by definition * note 1: when switch the settings from the view menu while in the ledger, I get a segfault, I could open a new issue if info needed * note 2: weirdly, if I'm on the ledger and I "apply" change to the "show reconciliation header" setting, which ever I choose including "all" update instantly in the back. Let me know if some other settings config could be useful. It's quite easy now to the the performance on that account, which to be clear isn't one of the original account I raise the issue, but still 11-18 sec to open the ledger is still an issue. > Yes, those corrections were made. The headers should not show up in red > anymore. I still have red reconciliation header in that account I was able to test. I was trying to find distinction with others similar account that didn't had issue. And this might be the biggest difference. Although my checking account (the original large account) do not have red reconciliation header -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #14 from Jonatan Cloutier --- Added a few maybe related settings, including the sort config. The specific account ledger use the default settings. Also maybe related, I use a lot scheduled transaction and display the next 30 days in the ledger as well as display past schedule at the planned date. I'll test the various sort settings on my side but might take a few hours -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #13 from Jonatan Cloutier --- Created attachment 157959 --> https://bugs.kde.org/attachment.cgi?id=157959=edit display-settings -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #12 from Jonatan Cloutier --- Created attachment 157958 --> https://bugs.kde.org/attachment.cgi?id=157958=edit sort-settings -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #11 from Jonatan Cloutier --- Created attachment 157957 --> https://bugs.kde.org/attachment.cgi?id=157957=edit filters-settings -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #8 from Jonatan Cloutier --- While working on my document (still with old version) I notice I got a lot of error of this type: * Sum of splits in transaction 'T023881' posted on 2022-10-27 is not zero. Account: Passif:, Amount: (13,79 $) Those are all transaction I haven't yet setted a category which explain the error (although, being notified on every save is a bit annoying, but that's another issue) I have 290 of those error currently, and it might match the accounts that are getting very slow (obviously it's the account with more transaction that take more time for me to properly cleanup) At least two of them are concerned -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #6 from Jonatan Cloutier --- Thanks for the info. Quickly looking at my file I don't see what filtering could make this happen. Currently on the the f3b33e9 commit I can't see any "empty" reconciliation. Only possible filter would be the "hide reconciliation transaction" option, but as it is off by default, I did try with it both enabled and disabled with the same result. One thing that might be related thought is that my account was opened in 2013 and It appear I did my first reconciliation in 2019 (I kind of doubt about it but cannot be certain, it does match the number I had in a backup from 2020. maybe the file format changed and only last reconciliation was saved at one point?) So that first reconciliation would span 2013 to 2019. The other thing is I havent properly done all my reconciliation in the last year. This specific account I'm looking at has last reconciliation a year ago, with probably a ~100 transaction after it. Looking at the transaction count, I have "only" 2087 in that specific account. I'm not properly setup to debug, but I could add logs if you see something that could be helpfull. Let me know if I can investigate anything else -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #3 from Jonatan Cloutier --- I only waited a few minutes, 3 or 4 at most. I know it's master and don't expect support on it but if isolated better raise it sooner than just before release -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] New: ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 Bug ID: 468108 Summary: ledger freeze on large account Classification: Applications Product: kmymoney Version: git (master) Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- Created attachment 157810 --> https://bugs.kde.org/attachment.cgi?id=157810=edit backtrace while freezed SUMMARY When trying to display any account ledger that has a large amount of transaction (1k+) cpu goes to 100% and KMyMoney freeze and has to be killed. Maybe I wasn't patient enough and it would have respond back, but more than a few minutes would still make no sense. Also, I'm guessing it related to the amount of transaction since it only happen on a few of my larger account, but maybe some specific transaction that are more likely to happen there or more reconciliation. The culprit seems to be arround this: #13 0x55b452bc in SpecialLedgerItemFilterPrivate::filterAcceptsRow(QModelIndex const&, QModelIndex const&, int) const (rowCount=977, source_parent=..., idx=..., this=) at /build/kmymoney/models/specialledgeritemfilter.cpp:288 #14 SpecialLedgerItemFilterPrivate::filterAcceptsRow(QModelIndex const&, QModelIndex const&, int) const (this=, idx=, source_parent=..., rowCount=) at /build/kmymoney/models/specialledgeritemfilter.cpp:217 and caused by https://github.com/KDE/kmymoney/commit/281c9759045f2a7929264accb58638ed250cf418 or later (did rollback to f3b33e9 and it work, haven't try forward reproducing the issue. STEPS TO REPRODUCE 1. open ledger on any large account, either from the account page or the ledger itself switching to another tab OBSERVED RESULT freeze EXPECTED RESULT display the ledger SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) 5.104.0 KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.18 Built statically through the docker compose provided, but ran locally on my arch ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 458479] For mapped investment accounts, show date of last online update
https://bugs.kde.org/show_bug.cgi?id=458479 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452451] Split transaction editor erase negative value when editing
https://bugs.kde.org/show_bug.cgi?id=452451 --- Comment #1 from Jonatan Cloutier --- Might not be directly related, but apparently the calculator result doesn't get set either for negative value. I could open a different issue if needed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452451] New: Split transaction editor erase negative value when editing
https://bugs.kde.org/show_bug.cgi?id=452451 Bug ID: 452451 Summary: Split transaction editor erase negative value when editing Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- SUMMARY When editing split transaction where the value is negative (e.g.: adjusting the interest paid on loan payment) the value disappears when trying to edit it. For positive numbers, it stays there as expected. The main issue coming from that is that I mostly edit that value to adjust some miscalculation on the interest paid on a loan and it's very easy to just take the actual number + the difference between the current amount in the bank account and in kmymoney. (ps, the miscalculation is certainly coming from a misconfig or a misunderstanding of the parameter of my loan, not from kmymoney) STEPS TO REPRODUCE 1. Create a new transaction 2. go in the split editor 3. set a category 4. set a negative amount (e.g.: -10.00) 5. Validate the input 6. double click on the amount to edit it OBSERVED RESULT The amount is empty when editing it EXPECTED RESULT Like for a positive amount, it should stay when editing the value SOFTWARE/OS VERSIONS archlinux Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452392] New: give flexibility on how to match a scheduled transaction
https://bugs.kde.org/show_bug.cgi?id=452392 Bug ID: 452392 Summary: give flexibility on how to match a scheduled transaction Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- My bank is really making great effort to make importing and matching transaction unsuccessful. Currently I believe the main way scheduled transaction get match is through the payee, but as my imported file is filled with transaction having "payment" as payee, sometime the memo would be more useful to do the match (the memo actually sometime contain the shop name see #452386) FEES SHOP NAME But in other cases it just says "transfer". In that case the amount would be the ideal matching field, as most of the time it's the automated transfer to saving accounts Transfer Transfer W3 - 1245 And one last case that gives me headaches is the payroll. In itself it's fine because I just have to match "PAIE/PAYROLL" to my job payee. The issue is that I manage both my account and my wife’s account in the same kmymoney file as they are too many accounts and assets in common. So in this case I'd like the transaction in my account to match the scheduled transaction for my pay, and the one in my wife account to match her, then the payee would be updated following the scheduled transaction payee instead of the payee matching rule. That would also greatly improve the two other cases. PAIE/PAYROLL PAIE/PAYROLL I understand that it might be quite complex to do that both in terms of code and of ux, so if I can help bouncing ideas feel free to ping me. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452391] New: ofx import account selection buttons are broken/misleading
https://bugs.kde.org/show_bug.cgi?id=452391 Bug ID: 452391 Summary: ofx import account selection buttons are broken/misleading Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- SUMMARY When importing many accounts from one ofx file, it does happen frequently that I want to skip an account entirely. The obvious way to do that is to click on the "skip" button. But then I get a message "You must select an account, create a new one, or press the Abort button". Since I do have an account selected and don’t want to create a new one, I'm left with the choice to abort. Which leads to the question, What’s the purpose of the skip button if it only seems to be able to trigger that warning. Then to start being confused, clicking on abort, actually skip only one account. I would have thought it would have cancelled the whole import. But fine, "abort" seem to mean "skip", so I'll use that. Finally reaching the end of my import, click on the last account "OK" and I get a "Importing process terminated unexpectedly" error followed by an import summary that seems to include everything and after checking and reconciliating the imported data everything is good. So what was unexpected? STEPS TO REPRODUCE 1. import an ofx file with many account 2. skip and abort at least one of them OBSERVED RESULT confusing button, popup and error EXPECTED RESULT - The skip button actually skip an account - The abort button actually abort the import - no error at the end - no popup saying a button is useless SOFTWARE/OS VERSIONS archlinux Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452389] New: Give the option not to prompt for scheduled found
https://bugs.kde.org/show_bug.cgi?id=452389 Bug ID: 452389 Summary: Give the option not to prompt for scheduled found Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- I use a lot the scheduled transaction for both forecast and helping the transaction import from my bank, but when doing the import I end up just clicking yes about a dozen times without looking at the information because it's easier to unmatch them afterward in the ledger view with the whole information in context than through that popup. Also, I barely ever need to unmatch one when reviewing. So in the end, that popup is just annoying for me ( I understand other might feel otherwise). A configuration to be able to automatically register the scheduled transaction is matched would be great. Could even be asked in the import itself instead of a global config as a "yes to all" or "always and forever yes" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452386] New: Payee should be able to be matched on memo
https://bugs.kde.org/show_bug.cgi?id=452386 Bug ID: 452386 Summary: Payee should be able to be matched on memo Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- When importing using ofx file, as bank formats are all mixed up and sometimes even in a single file. It would be helpful to be able to match a payee on either the "name" or the "memo" field. I currently have in a single account transaction that looks like. FEES SHOP NAME ... INTERETS 10.00 I know there is the option when manually importing an ofx file to select the payee field, but as I need both in the same import, it doesn't really help. Furthermore, I almost never manually import it using "webconnect" and having kmymoney open from the downloaded file which doesn't let me choose that value. As a side suggestion, when importing using memo field, the name field should be saved as memo otherwise we sometimes lose an information. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452385] New: Category get automatically assigned even if no default category in the payee.
https://bugs.kde.org/show_bug.cgi?id=452385 Bug ID: 452385 Summary: Category get automatically assigned even if no default category in the payee. Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- SUMMARY When importing transaction througth ofx file, the imported transaction is correctly matched against a payee, but a category is also automatically affected to that imported transaction based on a previous unrelated transaction (actually 2 year old, and amount is more than 30% different). I do have "no Autofill" configured STEPS TO REPRODUCE 1. Have an existing file with previous transaction for the matched payee 2. Import an ofx file containing a transaction for that payee OBSERVED RESULT See that the category was automatically assigned EXPECTED RESULT The transaction should stay unassigned The main reason being that my bank is getting dumber every year and now all direct payment have a payee name of "payment" and I need to assign the correct category, having it already assigned to a most of the time wrong category create more error that good. SOFTWARE/OS VERSIONS archlinux Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 431166] New: Impossible to change loan payment date
https://bugs.kde.org/show_bug.cgi?id=431166 Bug ID: 431166 Summary: Impossible to change loan payment date Product: kmymoney Version: 5.1.1 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- SUMMARY I had to change my mortage scheduling payment with my bank. I stay with the same payment schedule (every two weeks) but instead of being in even weeks it now needs to be on odd week. I can’t find a way to do that modification. Last time I had to do a similar change, I did it in the xml file directly, but now with gzip encoded file it becomes cumbersome at least. I believe the next payment date should be easily configurable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.76 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430047] Feature request: Budgeting based on cash flow
https://bugs.kde.org/show_bug.cgi?id=430047 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424507] Wish : Joint bank account
https://bugs.kde.org/show_bug.cgi?id=424507 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com --- Comment #7 from Jonatan Cloutier --- I've been dreaming of that feature for a few years. The two main purpose for me is to be able to split (%) of accounts or loan in the report. Mainly the net worth and the expense/budget report. The second is to improve the budget management. Currently I have to create 3 budget and 3 matching budget report: personal, SO personal and join. Which in the end is a pain to manage and understand. I always and up merging them in a spreadsheet. If the proposed ratio was implemented, it would be down to one budget per persons which would be a great improvement. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 Jonatan Cloutier changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #11 from Jonatan Cloutier --- Thanks, it did solve the issue. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 --- Comment #7 from Jonatan Cloutier --- Created attachment 128290 --> https://bugs.kde.org/attachment.cgi?id=128290=edit mars qfx file -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 --- Comment #9 from Jonatan Cloutier --- Hello, It took a bit of work to reproduce this on a vanilla file. 1. I started with a new data file, created 2 accounts and importing a first ofx file (for March). 2. Both transactions were imported but not matched automatically (I don’t know if I messed up the qfx file or some kmymoney setting or it's another bug, but it doesn't really matter here). So I linked them manually and created a recurring transaction from them ( right click -> create recurring...) 3. I imported another qfx file for the April month result: the transaction was imported and matched in the second account, but I have 2 transactions in the first one. I upload both qfx file, the startup kmy file I produce and the result kmy file to make sure you have all the info. To quickly reproduce you can start with the init kmy file and import April qfx file. Thank you for looking into that. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 --- Comment #8 from Jonatan Cloutier --- Created attachment 128291 --> https://bugs.kde.org/attachment.cgi?id=128291=edit april qfx file -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 --- Comment #5 from Jonatan Cloutier --- Created attachment 128288 --> https://bugs.kde.org/attachment.cgi?id=128288=edit init kmy file -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 --- Comment #6 from Jonatan Cloutier --- Created attachment 128289 --> https://bugs.kde.org/attachment.cgi?id=128289=edit result kmy file -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 Jonatan Cloutier changed: What|Removed |Added Version|5.0.7 |5.0.8 --- Comment #1 from Jonatan Cloutier --- Still present on 5.0.8 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 288844] KMymoney gives a wrong loan payment (auto-calculated) for a specific type of mortgage
https://bugs.kde.org/show_bug.cgi?id=288844 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418329] New: Matching transaction incomplete on transfers with scheduled transaction.
https://bugs.kde.org/show_bug.cgi?id=418329 Bug ID: 418329 Summary: Matching transaction incomplete on transfers with scheduled transaction. Product: kmymoney Version: 5.0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: cloutier...@gmail.com Target Milestone: --- SUMMARY I use a lot scheduled transaction for my forecast and thus I have many scheduled transactions that map to transfer between account (let say my weekly saving money transfert from my checking account). After that, when I import my bank transaction using ofx web connects the first transaction imported (checking account) match against the scheduled one, but the reverse (from saving account) doesn't get matched since the first one is already in "matched" state. STEPS TO REPRODUCE 1. Create a scheduled transaction of a transfer between two accounts 2. Have that transfer happens between the two real account 3. Import the bank ofx file containing both account transactions OBSERVED RESULT The first transaction is matched against the scheduled one, the second duplicate the transaction. EXPECTED RESULT The 3 transaction should be matched at once or the scheduled one shouldn't get in the way The work around currently is to accept the first match and then manually match the second one, but this crate a lot of research to find all the duplicate transaction on each import. SOFTWARE/OS VERSIONS: 5.0.7 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405383] Add python3 support for weboob plugin
https://bugs.kde.org/show_bug.cgi?id=405383 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 395821] Custom reports accumulate
https://bugs.kde.org/show_bug.cgi?id=395821 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397468] Reports covering historical reports should list closed accounts in use in that period
https://bugs.kde.org/show_bug.cgi?id=397468 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397750] Budgeted vs Actual do not include scheduler transfers and operations
https://bugs.kde.org/show_bug.cgi?id=397750 Jonatan Cloutier changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com --- Comment #5 from Jonatan Cloutier <cloutier...@gmail.com> --- I get this problem as well, just to add precision on when it happens. I found out that it does crash when opening directly from Firefox and kmymoney is already running. When kmymoney is lunched from the Firefox download the import complete successfully. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 382718] New: Dragging snapshot to a mail client generate wrong filename
https://bugs.kde.org/show_bug.cgi?id=382718 Bug ID: 382718 Summary: Dragging snapshot to a mail client generate wrong filename Product: Spectacle Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: cloutier...@gmail.com Target Milestone: --- I use spectacle a lot to send screenshot by email and with any mail client I've done it (gmail, outlook365, zimbra in both chrome and firefox and Thunderbirds), the attachment gets named like "Spectacle.U22108.png" The "save as" setting should be used to name the file when doing drag and drop, or simply to name the temporary file directly from this setting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382138] Feature request: save existing panel as "template" - then available in "Add Panel" menu
https://bugs.kde.org/show_bug.cgi?id=382138 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom
https://bugs.kde.org/show_bug.cgi?id=371199 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365968] scrolling is unusable slow with libinput in dolphin places and folders panel
https://bugs.kde.org/show_bug.cgi?id=365968 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355410] the scroll speed of QML scroll area is too slow with Libinput
https://bugs.kde.org/show_bug.cgi?id=355410 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 291835] KIO very slow when copying from network through smb
https://bugs.kde.org/show_bug.cgi?id=291835 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 252550] Dolphin is very slow when listing SMB folders
https://bugs.kde.org/show_bug.cgi?id=252550 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com --- Comment #14 from Jonatan Cloutier <cloutier...@gmail.com> --- I do also have this issue on archlinux Dolphin Version 16.08.0 KDE Frameworks 5.25.0 Qt 5.7.0 (built against 5.7.0) it's a maters of minutes to list a share that contain 60 subfolder folder, konqueror take about 10 secondes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Jonatan Cloutier <cloutier...@gmail.com> changed: What|Removed |Added CC||cloutier...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
