[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #51 from jesse --- Created attachment 165114 --> https://bugs.kde.org/attachment.cgi?id=165114=edit Example of a successful update with the configs mentioned Here is an example of the success message I received with these settings. I placed a link to the location of the online forum where I found the settings. I did not come up with them myself but can say that they worked for me on Kmymoney version: Version 5.1.3-0663fcc7b (Find KMM version , Toolbar > Help > About KMyMoney) I also agree that the average user does not know about compilations, or other tools methods that developers use. I think those suggestions are offered in case the user does know but if the user does not know, then the people here are very open to helping them walk through it. I've been helped in the past and am very grateful. If the user does not want to mess with it, then usually the answer is, wait until it is fixed. (At times the user is provided a link to a newer unreleased version that may include the fix they need, if available) I think the suggestions of compiling and others are only in case the user know how to do it. Much like when the mechanic explains what needs to be done. If you ask them, they may share details on how to do it in case you want to try yourself. But to the point, most people do not want to try because they usually do not have the knowledge or the tools to try it. Not their realm of expertise. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #50 from jesse --- Created attachment 165113 --> https://bugs.kde.org/attachment.cgi?id=165113=edit Image showing the set up for YahooFinance Trying to contribute by driving conversations is fine but I do not think the approach of name calling or any other form of aggression is necessary. Software development is challenging and especially more so when the dev teams are trying to do this on their free time and as volunteers. No developer wants it to be any harder than it needs to be. I believe the team here has mentioned that perhaps the real bug is the missing the documentation on how to leverage the tool to fix the online quotes. Maybe there should be a bug ticket open on that subject. Meanwhile, I am attaching a screenshot of my set up for YahooFinance. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #47 from jesse --- I agree Brendon. I really do not think comments like this are necessary: "kmm is for freaks and developers mostly," I do like the idea of having the web page to document what regex has worked. Maybe another open source project could be stood up to work as an interface and provide functionality to all financial software. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 jesse changed: What|Removed |Added Resolution|DOWNSTREAM |FIXED --- Comment #43 from jesse --- As a fellow user for almost a decade now, I do not consider this software as you described. "kmm is not for the masses, it is an experimental tool with no visible development, non existent documentation and "mail lists". As far as I can tell the software is of high quality - the reason I came to this platform from the others you mentioned. Everyone is always open to use whatever software fits their needs though. Free or paid options are available. The paid options come with some form of guarantee or Service Level Agreements so you can base your expectations. This software is developed by volunteers, it is provided free of charge. Developers from all over the world contribute, as they have time, to its support. They are all friendly, great developers and very supportive. From what I can tell, anyone is welcomed to use it. It has served many of users for many years(like me) and I have looked at the competitors. I have tried, most of, them and still continue to prefer this software. I believe there are two things we should consider: 1. The way that the portfolio handles the issue, is behind the scenes in the code itself, which is why you feel you did not have to do anything as a user. They fixed it and you upgraded at some point in time. With this approach you rely on the developers to 'fix' the issue. Luckily, somehow they must have noticed the issue and fixed it. I am not sure what the update cadence is for that software. I am not a developer but from what I've heard in mailing list and chats, the KMyMoney software is undergoing a major update. This may have caused KMyMoney updates to be further apart than usual. 2. As stated before, KMyMoney at least gives you the option to fix the issue yourself. It is in fact more flexible than the portfolio tool. As a user, you can modify how the quote is retrieved and when a volunteer developer finds time, they can update the code and make the fix available out of the box. I will agree that as users, many times we just want it done for us. I also do not like spending hours trying to research how to change the parser to make it work. This also leads to many google searches and testing of many different suggestions from people on the internet. I also think that maybe, as a way to mitigate some of this, it would be helpful if there was a page where official documentation could be kept with the most up-to-date community known method to retrieve the quotes. In my experience, other software offers this type of documentation but, it does get out of date. Anyone who finds a solution would need to go there to update and share with the community. Thus I see KMyMoney as providing two advantages: 1. the user community is able to update the command to retrieve the text themselves, no need to wait for developers. 2. the user community can wait until a new version is released that includes the fix as a default. To me this is very impressive to have such flexibility. It does not mean frustrations will not occur when it breaks. As a user, if I expect the software to 'fix' it for me, then I will just need to wait for a solution to be provided in the form of the code,( and hopefully the software is not undergoing major changes that may delay the release of new version at the time). For reference it appears that this is the bug report for portfolio app for when the yahoo API(html scrapper) broke for them: https://github.com/portfolio-performance/portfolio/issues/3302 This was the comments in their issue log: "Something between. Yahoo’s data providers could for instance temporarily stop the delivery , Yahoo could adjust their API interface or implement a new technology to prevent content grabbing. On the other hand, you get what you paid for :wink:" -- https://forum.portfolio-performance.info/t/price-incorrect-in-statement-of-assets/23806/3 I think this shows that both software are: - pulling the data from the same place, in the same way(html scraping). KMyMoney offers two ways for it to be fixed. - experience the same issue. Just because you did not experience the issue yourself, does not mean the issue did not occur with that software. They were able to push the fix in rapidly but it still happened. - Both software are susceptible to Yahoo changing the website breaking their application. Thus, I do not agree with the statement you made. The quality and abilities of the tools are on par if not KMyMoney provides a more flexible solution allowing users to fix the issue even between releases. I am not sure how fast Portfolio-Performance responded to the issue, but they were definitely able to push the fix in to the app download package sooner. I am glad thou
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #40 from jesse --- Adding the link of where I found their solution: https://github.com/portfolio-performance/portfolio/blob/master/name.abuchen.portfolio/src/name/abuchen/portfolio/online/impl/YahooFinanceQuoteFeed.java -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431
--- Comment #39 from jesse ---
I found the source code and even where they fixed the html parser for
themselves.
Looks like this may have been done by them about 6 months ago, according to the
comment.
Either way, their solution is the same as the link I posted earlier suggest.
Their solution:
@SuppressWarnings("nls")
public String rpcLatestQuote(Security security) throws IOException
{
return new WebAccess("query1.finance.yahoo.com", "/v8/finance/chart/" +
security.getTickerSymbol())
.addParameter("lang", "en-US").addParameter("region",
"US")
.addParameter("corsDomain", "finance.yahoo.com").get();
}
You can see that they made the same update ( to change v7 to v8 and use
v8/finance/chart/%1).
I did not look at all of their code but I see that they seem to be pulling some
json objects too. Perhaps someone can dig into the code and find if they have a
public api they are calling.
As of now, it seems their solution and what the linked posted before, are
consistent.
It may just be that they got to it sooner.
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #38 from jesse --- Do you have a link to their source code? (Free and Open Source Software) If so, the team can probably replicate some of what they implemented. (In reply to KB.claim from comment #37) > (In reply to jesse from comment #36) > > I used this as a solution and it worked well to get the stock quotes. > > https://discuss.kde.org/t/kmymoney-updating-stock-mutual-fund-issue/1228/19 > > > > I think this will continue to be an ongoing issue due to the fact that Yahoo > > changes the site. Unless there is a site that provides data through a free > > API, which I have not found one, it will be difficult to ensure that this > > never breaks again. > > > > Is there any open source projects that would offer this? I doubt it as all > > programs that offer it as a service are not free-to-use. usually they come > > with a price/cost, and some of that is most likely used to pay for the back > > end services. > > Would it be worth to ping the developers of other FOSS Financial software to > > see how they are handling this? > > Excellent post. > > Indeed there is one FOSS project that works incredible well with finance > data and for many years not a single problem: Portfolio-Performance: > https://www.portfolio-performance.info/en/ -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #36 from jesse --- I used this as a solution and it worked well to get the stock quotes. https://discuss.kde.org/t/kmymoney-updating-stock-mutual-fund-issue/1228/19 I think this will continue to be an ongoing issue due to the fact that Yahoo changes the site. Unless there is a site that provides data through a free API, which I have not found one, it will be difficult to ensure that this never breaks again. Is there any open source projects that would offer this? I doubt it as all programs that offer it as a service are not free-to-use. usually they come with a price/cost, and some of that is most likely used to pay for the back end services. Would it be worth to ping the developers of other FOSS Financial software to see how they are handling this? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 479040] New: Show balance chart: should always display absolute values
https://bugs.kde.org/show_bug.cgi?id=479040 Bug ID: 479040 Summary: Show balance chart: should always display absolute values Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY I noticed that the the Show balance chart button, which is available when a ledger is opened, shows positive number scale for assets and negative number scale for liabilities. I believe it should show absolute values. Meaning, always positive values regardless if the account being displayed is a liability or asset. Or perhaps provide a toggle for users to decide how they want to show it. In my opinion, it is confusing to see the liabilities show negative values when I want to see the balance history(line trend) of the account. This however, may only be a preference and it absolutely does not hinder the usability of the application. STEPS TO REPRODUCE 1. Open a ledger of asset type 2. Press the Show balance chart button on the top bar 3. Notice the values are in positive range (assuming the account is not under) 4. Open a ledger of type Liability 5. Press the Show balance chart button on the top bar 6. Notice the values are in negative range(assuming the account is not over credited) OBSERVED RESULT See above EXPECTED RESULT Matter of opinion; seems to me that the value and chart should be based on absolute values(positive number scale) regardless of liability or asset type of account. SOFTWARE/OS VERSIONS Kmymoney: 5.1.3-33a66be8a Linux/KDE Plasma: Fedora Linux 39 (Workstation Edition) KDE Plasma Version: N/A (Gnome 45) KDE Frameworks Version: KDE Frameworks Version 5.108.0 Qt Version: Version 5.15.10 (built against 5.15.10) ADDITIONAL INFORMATION Using app image -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 478530] New: Warn users when they are adjusting transaction that will affect a time period already reconciled
https://bugs.kde.org/show_bug.cgi?id=478530 Bug ID: 478530 Summary: Warn users when they are adjusting transaction that will affect a time period already reconciled Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Consider the situation when a user has a transaction that will modify the amount for a reconciled time period. Given accounts: Asset: Bank checking Reconciled to date 11/01/23 Liability: car note not reconciled Expense: other-expenses The bank checking account is reconciled with some transactions going to other-expenses. However, one of the transactions was intended go towards the liabilities. When user is reconciling the Liabilities account, they may noticed that the transaction for the car note is missing. If they try to enter the transaction, KmyMoney will not complain even if they enter the new transaction for 10/15/2023. STEPS TO REPRODUCE 1. Create a checking account, liability and expense account. 2. reconcile the checking account to date 3. Enter a new transaction in the Liability account that will affect the checking account prior to the date of reconciliation. OBSERVED RESULT KMyMoney does not warn the user. EXPECTED RESULT KMyMoney should warn the user that the entering the transaction will cause a reconciled time period on the partner account to no longer be reconciled. KMyMoney should then un-reconcile the checking account as of the date of the new transaction. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 39 (Workstation Edition) - Gnome KDE Plasma Version: N/A - Using Gnome KMyMoney: Version 5.1.3-33a66be8a KDE Frameworks Version: Version 5.108.0 Qt Version: Version 5.15.10 (built against 5.15.10) ADDITIONAL INFORMATION It does warn when you attempt to adjust a transaction that is already in the ledger in a reconciled state. However, it does not warn if you add a new transaction into a reconciled time period. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475666] Running Balance and Reconciliation balance do not match
https://bugs.kde.org/show_bug.cgi?id=475666 --- Comment #1 from Jesse --- My apologies for the long comments. I did some troubleshooting over the past few days. My only workaround to the original issue was to create an additional checking account in the same file and move transactions 1 statement at a time and then reconcile in the new account. This worked for a while and I got past the time period shown in my first attachment, but then it appeared again later but for a different amount ($323.52). At a loss, I scrolled through the transactions and noticed that a few were "bold" and realized that they were not marked as cleared. (Yes, you can start laughing/mocking this guy for something simple). Once marked as cleared the balances matched up and I could continue the reconciliation. Though I am quite sure that I marked them as cleared before reconciling. I'm getting old. However, back to the original problem, how can this be addressed for other users that won't recreate and reprocess and entire bank account (hey, I am doing this for my primary account from 2008 until today)? Somewhere I missed a $3 transaction but processed the reconciliation. - I couldn't add a fake transaction as it would throw off the real running balance - I couldn't adjust the reconciliation balance as it wouldn't match - If the $3 transaction was later reconciled, it wasn't affecting/correcting the balance - I saw another user Wish for the ability to change the starting balance in the wizard, but agree with you that that is not a good idea as it means that something is wrong. I was also considering improvements to the reconciliation wizard input box, like the preloaded ending balance that only sums transactions that are already marked as Cleared instead of the entire statement period, but in thinking about it, it makes complete sense. If they don't match up, something is wrong. Thanks for listening, and unless you want/need to address the issue above, we can mark this as closed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475666] New: Running Balance and Reconciliation balance do not match
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-de...@kde.org Reporter: jesgei...@outlook.com Target Milestone: --- Created attachment 162326 --> https://bugs.kde.org/attachment.cgi?id=162326=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 watching all bug changes.
[kmymoney] [Bug 468959] Context menu move transaction selector window too small
https://bugs.kde.org/show_bug.cgi?id=468959 --- Comment #5 from jesse --- I think this is a great step forward! I also agree that it should be dynamic based on the longest entry but I don't know all the ins and outs of it. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 474005] Display a few more information in the category view
https://bugs.kde.org/show_bug.cgi?id=474005 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #3 from jesse --- +1 I would like the feature or ability to see which payees have the category as a default category. Knowing when it became the default; I am not sure how useful it would be to me. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #21 from jesse --- (In reply to Pete from comment #20) > If you could give me the number of KMM users affected by this bug, it might > raise its priority with Yahoo Finance tech support. I wonder if there is a way to know the number of users. Also, not all users may be users of this particular issue. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 470971] Credit card - incorrect balance in ledger, incorrect net worth report
https://bugs.kde.org/show_bug.cgi?id=470971 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #8 from jesse --- I think this is a good reason to show both debits and credits(accounting terms) rather than use positive and negative values. Then the values could be absolute and never negative. Standard double accounting, but it will be a little more difficult for those not familiar with double accounting. >From the user post, I do not think the result failed, rather it did not show what the user expected. Negatives vs positive values rather than absolute values. Maybe give an option to switch between both views? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468936] Home Page and Reports display completely black - Cannot Read
https://bugs.kde.org/show_bug.cgi?id=468936 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #8 from jesse --- I am using Gnome with Wayland and it does not display that way. I know that in the past, when I had both Plasma and Gnome installed, if I set the KDE Plama theme to dark, then came to Gnome, Kmymoney will show as dark themed. Basically the problem you are reporting. Did you set any settings for KDE anywhere? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469881] Animation Curve Issues on Resize
https://bugs.kde.org/show_bug.cgi?id=469881 Jesse J. Jones changed: What|Removed |Added Component|General |Animation -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469881] Animation Curve Issues on Resize
https://bugs.kde.org/show_bug.cgi?id=469881 Jesse J. Jones changed: What|Removed |Added Version|unspecified |5.1.5 Assignee|unassigned-b...@kde.org |krita-bugs-n...@kde.org Component|general |General Product|kde |krita -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469881] Animation Curve Issues on Resize
https://bugs.kde.org/show_bug.cgi?id=469881 Jesse J. Jones changed: What|Removed |Added Summary|Animation Curve Issues |Animation Curve Issues on ||Resize -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469881] New: Animation Curve Issues
https://bugs.kde.org/show_bug.cgi?id=469881 Bug ID: 469881 Summary: Animation Curve Issues Classification: I don't know Product: kde Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mortalp...@gmail.com Target Milestone: --- SUMMARY *** While animating with layers that used Animation Curves, resizing the image did not resize considering the Animation Curves, so the animation was positioned off-screen. Undo did not fix it and the animation layer had been permanently moved down and to the right. Could have ruined all of my work had I not saved beforehand. *** STEPS TO REPRODUCE 1. Make a frame by frame animation, set position keyframes moving the X and Y position at different intervals. 2. Resize the image (notice the animation is not in the correct place) 3. Undo resize (notice animation is still not in the correct place) OBSERVED RESULT Animation curve information is not calculated properly on image resize, and undo doesn't reset it properly. EXPECTED RESULT Resize and undo after should not change animation curve's position. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Easily reproducible. -- 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 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #1 from jesse --- We should also check that there is a trim function to remove outer white spaces from both the payee and the value in the import. This may be there already. I mention it just in case it is not. I have noticed that the payee field in the transaction input form does see 'happy' as different from 'happy '. The last one has a trailing blank. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468959] Context menu move transaction selector window too small
https://bugs.kde.org/show_bug.cgi?id=468959 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #1 from jesse --- I agree it is annoying but still kMyMoney is highly useable. I have been using it for the past several years. Hopefully it does get addressed. Thanks. -- 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 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #2 from jesse --- We need this. :) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442049] reports: click on account to see transactions contributing to the report for the date
https://bugs.kde.org/show_bug.cgi?id=442049 --- Comment #2 from jesse --- Glad to see support for this! I am still interested just not sure how to code this.. yet. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 465730] New Skrooge AppImage Crashes Upon Attempted Load
https://bugs.kde.org/show_bug.cgi?id=465730 --- Comment #2 from Jesse --- Hello Stephane, Thank you for the overview and instructions. Very helpful. I executed your terminal command and received a version of 2.31 for several entries. I then went to review updates and packages that are held back with the "apt update" command and updated them manually, but no progress. It is then that I, sadly, realized that I was using my secondary machine which looks physically identical, along with the background and several other items. It is running Mint 20.3, not 21.1. I booted up the proper machine, downloaded the AppImage, made it executable, and it ran immediately with no issues, and all icon images were shown from my last bug. I ran your terminal command anyway and received version 2.35 for 2 entries. I have now learned that not all Linux AppImages are "backward compatible" between OS versions, even though they are self contained, and will watch out for that in the future. There are still some necessary dependencies. I know how frustrating it is for a developer to get reports like this due to my own ignorance/stupidity, and for that I apologize. I shall make it more obvious to myself which machine I am on in the future. If this is actually a bug for Mint Cinnamon 20.3, please let me know and I can enter a new bug and provide any additional info you need. I thank you again for your time. This issue can be closed. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 465730] New: New Skrooge AppImage Crashes Upon Attempted Load
https://bugs.kde.org/show_bug.cgi?id=465730 Bug ID: 465730 Summary: New Skrooge AppImage Crashes Upon Attempted Load Classification: Applications Product: skrooge Version: 2.29.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: jesgei...@outlook.com CC: steph...@mankowski.fr Target Milestone: --- Created attachment 156248 --> https://bugs.kde.org/attachment.cgi?id=156248=edit Terminal error output SUMMARY *** Happy that my previous bug was addressed, I downloaded the new v2.29 AppImage version and tried to run it but it was not opening. Tried several different mirrors, and several other steps. Finally I ran file from a terminal and got a bunch of lines that seem to indicate missing components from the AppImage. Since I understand an AppImage is self-contained, I would not need to have or install these on my OS. See attached screenshot for error output. *** STEPS TO REPRODUCE 1. Download new 2.29 AppImage version and make it executable 2. Attempt to open file using double-click, or "open" command 3. Then manually execute file in terminal using ./ syntax OBSERVED RESULT - Using step 2 above there is no hard drive activity, and no indication that the app will open. I waited an hour while I went to lunch just to make sure. - Using step 3 above displays tons of output about items missing, I assume packages or components. See attached file. EXPECTED RESULT After being made executable, AppImage file should open normally. SOFTWARE/OS VERSIONS Skrooge AppImage info unknown as it doesn't open. Desktop Flatpak install works just fine. Running Linux Mint Cinnamon 21.1 Vera x64 ADDITIONAL INFORMATION Previous AppImage versions (namely 2.28) opened just fine -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 303562] Order of columns in ledger view is not adjustable.
https://bugs.kde.org/show_bug.cgi?id=303562 --- Comment #5 from jesse --- Thanks all! Do we know when this version will release? How long does it historically -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 303562] Order of columns in ledger view is not adjustable.
https://bugs.kde.org/show_bug.cgi?id=303562 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #2 from jesse --- Thanks for keeping it open! Much appreciated! I look forward to the implementation if possible. Great work on this software btw. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 465335] New: Skrooge v2.28.0 AppImage Icons Don't show
https://bugs.kde.org/show_bug.cgi?id=465335 Bug ID: 465335 Summary: Skrooge v2.28.0 AppImage Icons Don't show Classification: Applications Product: skrooge Version: unspecified Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: jesgei...@outlook.com CC: steph...@mankowski.fr Target Milestone: --- Created attachment 155976 --> https://bugs.kde.org/attachment.cgi?id=155976=edit Screenshots and System Info SUMMARY AppImage vs Flatpak app has icon issues. This is for Skrooge version 2.28.0, which is not available for selection above. See attachment for visual comparison. Downloading and executing the latest AppImage version from website shows a vast majority of icons that are unavailable for use in the app. They are all represented as a page with an ! on it. Installing the same version as a Flatpak from my OS software manager (Linux Mint 21.1 Cinnamon) shows all icons as available and correctly displayed. STEPS TO REPRODUCE 1. Install Flatpak version of application, open it and select the Operations page/tab. All icons will display correctly, and in other parts of the app. 2. Download the AppImage version, make it executable. 3. Run the AppImage and select the Operations page/tab OBSERVED RESULT Flatpak version loads all icons correctly. AppImage does not. See attachment for visual comparison (2 pages, 1 for FlatPak and 1 for AppImage). EXPECTED RESULT AppImage version should have all icon files compiled within AppImage format, or properly utilize available system icons as the Flatpak version does. SOFTWARE/OS VERSIONS Linux Mint 21.1 Cinnamon x86-64 bit Screenshots in attachment -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 463015] Inactive Payee
https://bugs.kde.org/show_bug.cgi?id=463015 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #1 from jesse --- I am curious, would marking a payee inactive simply avoid showing the payee in the list? I am assuming the payee is still there since the system needs it for the integrity of the data. Also, what should happen if a payee is marked inactive but a new transaction comes in for that payee? I think, it should still hide the payee but when you attempt to enter the payee or transaction, kMyMoney should inform you. The message that should show would need to explain how to re-activate the payee. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462964] New: Gnome Dark Mode Support
https://bugs.kde.org/show_bug.cgi?id=462964 Bug ID: 462964 Summary: Gnome Dark Mode Support Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Gnome offers a Dark Mode but MyMoney does not seem to use it or change when it is selected by the Gnome user. STEPS TO REPRODUCE 1. Use Fedora or any other distribution with Gnome 42+ 2. Switch to Dark Mode (top right system tray, selected dark mode) 3. Open KMyMoney OBSERVED RESULT Kmymoney is not using the Dark Mode feature EXPECTED RESULT Kmymoney uses the Dark Mode feature and displays in dark mode. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome 43.1 KDE Frameworks Version: Version 5.100.0 Qt Version: Version 5.15.7 (built against 5.15.7) ADDITIONAL INFORMATION KMyMoney Version 5.1.3-71876c371 Maybe related: https://bugs.kde.org/show_bug.cgi?id=449590, https://bugs.kde.org/show_bug.cgi?id=460719 but neither are for KMM. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462643] New: Cash flow - Money in and money out
https://bugs.kde.org/show_bug.cgi?id=462643 Bug ID: 462643 Summary: Cash flow - Money in and money out Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Idea for a report to show the money that came into the Assets accounts and the money that left the Assets accounts. Let the user select the accounts they want to be analyzed. The report should show the amounts as Debits vs Credits with the option to show a single column with the negative amounts vs the positive amounts for the Accounts. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome 37 KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462246] Report Future Transation LIST
https://bugs.kde.org/show_bug.cgi?id=462246 --- Comment #2 from Jesse --- Hi Jack, Hoping that replying on my phone gets to you. Will check later. Suggestion for implementation: what about tagging those "ghost" transactions with a new status code "S" for Scheduled to go along with Cleared and Reconciled? Hopefully it would reduce the overall reporting rework as it's just an additional option to an already existing field. Just a suggestion. Thanks for getting back to the inquiry. Jesse Geiger >From an Android's Outlook From: Jack Sent: Friday, December 2, 2022 5:19:09 PM To: jesgei...@outlook.com Subject: [kmymoney] [Bug 462246] Report Future Transation LIST https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D462246data=05%7C01%7C%7C3dbb0a237e8f4e92560608dad4b33ce8%7C84df9e7fe9f640afb435%7C1%7C0%7C638056163549711708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=Y8HnS7EmywPzMFpJXZLUoQNYg9AvFvZPGFwsGgRsVus%3Dreserved=0 --- Comment #1 from Jack --- This is a valid wishlist. The underlying issue is that scheduled transactions in the future are not really transactions until they are entered into the ledger. They are shown in the ledger due to special handling which is only used in the ledger, not anywhere else. I'm not sure how much effort it would be to include these transactions in reports, but I suspect it is far from trivial, and thus unlikely to be implemented in the near future. It would not only require generating the "pseudo-transactions" (I just invented that term) but also finding a way to differentiate them from "real" transactions. Depending on the report, you then also have to be careful if they might affect any totals shown. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462246] New: Report Future Transation LIST
https://bugs.kde.org/show_bug.cgi?id=462246 Bug ID: 462246 Summary: Report Future Transation LIST Classification: Applications Product: kmymoney Version: 5.0.8 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jesgei...@outlook.com Target Milestone: --- Created attachment 154026 --> https://bugs.kde.org/attachment.cgi?id=154026=edit System info and problem screenshots SUMMARY *** I am trying to print out an account transaction list that INCLUDES future transactions that are listed in gray due to the scheduler. No current report template seems to have that ability. Even if I choose a date range like "next 3 months" all report transactions stop at today. I would prefer to not "enter next transaction" because it hasn't entered yet, which is the point of the scheduler. Again: - not a list of scheduled transactions - not a forecast *** STEPS TO REPRODUCE 0. Use AppImage file for application 1. Have transactions entered for the past 3 months and "confirmed." Not sure what term to use here, but "Cleared" or "Reconciled" doesn't matter here. 2. Have scheduled transactions that fall within the next 3 months, but DO NOT add them (enter next transaction function). They should remain gray from the scheduler, not turn white as if they were cleared entries. 3. Open any transaction report (ex: transactions by account) 4. Configure the report filters for the relevant account and date range "Last 3 to Next 3 months" 5. Run the report OBSERVED RESULT Filtered transactions listed STOP at today's date. Nothing scheduled beyond today appears in the report. EXPECTED RESULT Scheduled transactions beyond today's date (within the specified date range) should be listed in the transaction list. OR have a flag in the report config to include scheduled transactions or not. SOFTWARE/OS VERSIONS Linux Mint, info in attached doc KDE Plasma Version: N/A KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION I have attached a document with an example. It shows the end of my account with a few transactions from today and scheduled ones as well. Then it shows the transaction report that stops. There are 3 items listed beyond today (Nov 25) because they are "confirmed" entries, but the others do not. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462149] Create a New Report results in the new report being empty.
https://bugs.kde.org/show_bug.cgi?id=462149 jesse changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from jesse --- Hi Jack, Yes, the report still comes up blank after closing it and re-opening it. If I change the number of accounts, it remains the same. Still all zeros. It is almost like it lost the source of the data. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462149] Create a New Report results in the new report being empty.
https://bugs.kde.org/show_bug.cgi?id=462149 --- Comment #4 from jesse --- Created attachment 153984 --> https://bugs.kde.org/attachment.cgi?id=153984=edit Example with the Networth report Let me know if this helps -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462149] Create a New Report results in the new report being empty.
https://bugs.kde.org/show_bug.cgi?id=462149 --- Comment #3 from jesse --- (In reply to Jack from comment #2) > I can't reproduce this. Does it happen with any report? > What was the base report for the one you show in the attachment? The title > shows "Where the money went this year" but a new report should always start > with "Copy of ". What filters are in place for the report you show? > Do you see any differences between the configuration of the "New" report and > the one it is a copy of? Yes the new reports do start with 'Copy of' but I remove that anyways, and just name it something unique. As for recreating it, I can recreate it in master only. If you use the stable releases, it works fine. My report is called Where Money went - This month. It is a report where I show the transfers then I hit the new button, and the blank report shows up. When I try to copy another report.. The Net Worth by Month, for example. This one is out of the box report. If I hit the New Report button, it will open the Report configuration dialog box, then when you close the dialogue box, the report is empty.(all zeros) See new attachment named example_net_worth -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462149] Create a New Report results in the new report being empty.
https://bugs.kde.org/show_bug.cgi?id=462149 --- Comment #1 from jesse --- Created attachment 153958 --> https://bugs.kde.org/attachment.cgi?id=153958=edit Example of the report that is created with empty values. Example of the new report created with empty values. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462149] New: Create a New Report results in the new report being empty.
https://bugs.kde.org/show_bug.cgi?id=462149 Bug ID: 462149 Summary: Create a New Report results in the new report being empty. Classification: Applications Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Using Master: If you create a new report, the new report appears but all the data is empty. Meaning it all shows as zeros. I will attache a screenshot if possible to help describe the issue. STEPS TO REPRODUCE 1. Open a kMyMoney book 2. proceed to report, open any report 3. click on create new report. OBSERVED RESULT the new report is shown but it is all empty, it shows zeros for all the values. EXPECTED RESULT The new report should open but not be empty or show all the fields as zeros. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Fedora Gnome 37 KDE Frameworks Version: KDE Frameworks Version 5.99.0 Qt Version: Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION Using master... KMyMoney - Version 5.1.80-27c8a9a30 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461749] Allow interruption of report generation
https://bugs.kde.org/show_bug.cgi?id=461749 --- Comment #8 from jesse --- Yes, I think the clean up of data structures and such should be left to the developers to figure out and engineer the best solution. From a user perspective though, I think it makes senses that the user should be allowed to configure the report without the need for the report to execute first. This would keep the issue you are reporting from happening. I have not personally ran into it as my data size is very low. But one day I will face this. I believe, from a user perspective, it would be ideal if I can open a configuration for a report, and decide after configuring it if I want to : 1. Cancel - disregard the changes and stop the report execution. Return the user to the list of reports to choose from. 2. Apply - Apply the changes to the report but do not execute the report. Return the user to the list of reports to choose from. 3. Run - Apply the changes to the report and execute the report generation. This would result with three options for the user in the report configuration dialog box. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461841] New: Ability to mark account/categories as placeholders
https://bugs.kde.org/show_bug.cgi?id=461841 Bug ID: 461841 Summary: Ability to mark account/categories as placeholders Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Provide a way to designate some categories/accounts as placeholders only. Block any attempts to add transactions to the placeholder accounts. Will make the reports easier to read as the placeholder accounts should not show anything in the columns across the table. Will also help keep the accounts more organized. STEPS TO REPRODUCE 1. Go to the categories section 2. Edit a category 3. Go to a report like income/expense report. notice that the parent accounts have a value. Assuming the parent accounts should not have a value. OBSERVED RESULT You are not able to designate an account/category as a placeholder. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: KDE Frameworks Version 5.99.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) App image: Version 5.1.3-cc213a5e2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461749] Allow interruption of report generation
https://bugs.kde.org/show_bug.cgi?id=461749 --- Comment #6 from jesse --- Why not put a cancel button and if the cancel button is pressed, do not generate the report and close the dialog? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461749] Allow interruption of report generation
https://bugs.kde.org/show_bug.cgi?id=461749 --- Comment #3 from jesse --- Ok. I see. I think it should wait to generate the report until the configure dialog is closed or Apply is pressed by the user. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461749] Allow interruption of report generation
https://bugs.kde.org/show_bug.cgi?id=461749 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #1 from jesse --- Another idea: Maybe the right solution should allow the user to configure the report before running it. Maybe from the list of reports, add a configure button next to the report name, to allow the user to configure the report before running it. This will allow the user to set the date range and other selections for optimizations before the code attempts to generate the report. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461685] New: ledger entry amount should default to highlight all textclic
https://bugs.kde.org/show_bug.cgi?id=461685 Bug ID: 461685 Summary: ledger entry amount should default to highlight all textclic Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY When a user leaves the application and comes back to it, if they are in the Amount field, it should highlight the whole value. STEPS TO REPRODUCE 1. Open a MyMoney Book 2. Go to the ledger for an account 3. Fill out the new transaction entry form (Click in the amount field and switch to another application) 4. return to kMyMoney OBSERVED RESULT Notice that the cursor is still in the amount field but the value 0.00 is showing and the cursor is after the '.00'. You will now have to remove the value before you can enter the value that you need there. EXPECTED RESULT When the Amount field gets focus, the cursor should highlight the full value and be ready for the user to type it over the existing value. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome 36 (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: KDE Frameworks Version 5.99.0Qt Version 5.15.5 (built against 5.15.5) Qt Version: ADDITIONAL INFORMATION App image: KMyMoney Version 5.1.3-cc213a5e2 I think bug 397356 may be related. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461644] New: Feature Request: Allow user to select the depth in hierarchy that the report should go to.
https://bugs.kde.org/show_bug.cgi?id=461644 Bug ID: 461644 Summary: Feature Request: Allow user to select the depth in hierarchy that the report should go to. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Today the reports allow the user to select All, Top, Groups, Total... I would like to ask for a feature to allow the user to selects the depth to which the reports will do down a hierarchy. Total = 0, Groups=1, Top=2, All=3, 4, 5, 6, 7, 8, 9, 10, etc.. If there choice a user selects is deeper than the available depths, then just show ALL. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT User can only select from 4 choices. The reports are limited to lots of detail or not enough detail. Completely depends on who the user set up their accounts, if many sub categories, then this will be encountered. EXPECTED RESULT Allow user to select the depth. This way the user can select and adjust the reports as needed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: KDE Frameworks Version 5.98.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) KMyMoney Version 5.1.3-3408d1edc ADDITIONAL INFORMATION May be related to : https://bugs.kde.org/show_bug.cgi?id=275706 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461295] New: Matching example is incorrect
https://bugs.kde.org/show_bug.cgi?id=461295 Bug ID: 461295 Summary: Matching example is incorrect Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: documentation Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY The example on this page: https://docs.kde.org/stable5/en/kmymoney/kmymoney/details.payees.personalinformation.html#details.payees.personalinformation.matching is incorrect. The image shows the matching name as sun trust and the text explains that the application will be able to match the transactions with SUNTRUST in the name to the payee. STEPS TO REPRODUCE 1. go to https://docs.kde.org/stable5/en/kmymoney/kmymoney/details.payees.personalinformation.html#details.payees.personalinformation.matching 2. Read the example and compare to the image OBSERVED RESULT The example says that the application will be able to match “SUNTRUST BANK MAPLE VALLEY, GA 111506” and “SUNTRUST BANK MAPLE VALLEY, GA 121606” using the matching value of 'sun trust'. EXPECTED RESULT the matching value will need to be SUNTRUST in the image. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome 36 KDE Plasma Version: n/a KDE Frameworks Version:KDE Frameworks Version 5.98.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION App image: KMyMoney Version 5.1.3-3408d1edc -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460633] Typing stops working when sending a text from computer.
https://bugs.kde.org/show_bug.cgi?id=460633 --- Comment #3 from Jesse Harris --- Sorry about spamming comments or whatever this is. Last one for now. I am investigating further as we speak. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460633] Typing stops working when sending a text from computer.
https://bugs.kde.org/show_bug.cgi?id=460633 --- Comment #2 from Jesse Harris --- Ok so now its happening after the 7th character no matter what I type, but it doesn't do it every time. Sometimes closing and reopening KDE Connect on my laptop fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460633] Typing stops working when sending a text from computer.
https://bugs.kde.org/show_bug.cgi?id=460633 --- Comment #1 from Jesse Harris --- It seems to happen at random, like sometimes it happens, sometimes it doesn't. I am not doing anything differently that I can think of. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460633] New: Typing stops working when sending a text from computer.
https://bugs.kde.org/show_bug.cgi?id=460633 Bug ID: 460633 Summary: Typing stops working when sending a text from computer. Classification: Applications Product: kdeconnect Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: electroboy...@tutanota.com Target Milestone: --- 1. Open texting section of kdeconnect on desktop/laptop and select a person to text. 2. Click on the message box. 3. Type the symbol "!" 4. Press any character key. The result of these actions is that attempting to type any character key after an "!" will not show in the message box. The expected result is for the characters to show up in the message box. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I am running Fedora 36 KDE spin on a Dell Latitude E5470 with 32GB of RAM and a Core i5-6300U cpu. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 460108] New: Reports allow account level selection
https://bugs.kde.org/show_bug.cgi?id=460108 Bug ID: 460108 Summary: Reports allow account level selection Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Please add the ability for the user to select how many levels down from the parent account level should reports display. Today you can choose All, Top-Level, Groups and Totals. Please allow the user to select the number of levels down in the hierarchy to display. STEPS TO REPRODUCE 1. open kMyMoney 2. Select a report (Assets by Month for example) 3. Press Configure 4. Under Rows/Columns, click on the Detail drop down box. OBSERVED RESULT You see 4 choices EXPECTED RESULT Display the 4 choices or allow the user to select the number of accounts levels to drill down to. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 Gnome KDE Plasma Version: n/a KDE Frameworks Version: KDE Frameworks Version 5.98.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459866] Wish list: Default to new transaction entry when in ledger
https://bugs.kde.org/show_bug.cgi?id=459866 --- Comment #2 from jesse --- (In reply to Jack from comment #1) > When I open a ledger, I more commonly want to look at existing transactions > than to enter a new one. Even for new transactions, I import far more than > I manually enter. Perhaps this can be a user configuration setting, but I > would argue against it being the default. > I would also point out that if you are going to enter a new location, you > are going to need to use the keyboard, so typing the shortcut for a new > transaction is only a few extra keystrokes, not a totally unrelated action. > It also is reasonable to discuss which field has focus when a new > transaction is started. In this case, I agree on it being the date, and > preferably the day part of the field, although my understanding is that (in > master) it is the left-most field, which depends on the locale being used > (MDY, DMY, ...) Yes, I normally do the same. There are some accounts where my bank does not allow for OFX/direct connect. Either they want me to pay for it or they just do not offer it. In any case, for those I like to enter the transactions. At times, I also sit down with my receipts (paper or digital emails/texts) and enter them to get a better picture of my financial status. At the end of the month, I download the qif files and import them(I let kMyMoney do the matching). Perhaps I am the only one doing it this way and if so, that is fine. If the team gets to this wish list item, it would be cool it not, and no one else needed it, that is fine too. I do think it can be a setting. I just do not like to switch between the keyboard and mouse too often. I, however, am not a UX expert so if there are any, maybe they may have some good insight to share with us. It is also when I am manually entering transactions that I would find it useful to have the program open a new transaction form after I close the existing transaction I am working on. I think the current app image version and master both let you set the column within the date field that you want to be the starting focus point. I change between the month and the day all the time. :) Maybe if there was a keyboard short for changing the ledger field that the user is looking at... that would also be cool Like ctrl-L for ledger list, then a search box to filter, arrow keys to high light and then enter key to select. :) That can be another feature request for the future. I wish I could be more helpful than just offering wish list items. working on studying the code. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459866] New: Wish list: Default to new transaction entry when in ledger
https://bugs.kde.org/show_bug.cgi?id=459866 Bug ID: 459866 Summary: Wish list: Default to new transaction entry when in ledger Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY When a user is on a ledger, by default have the cursor on the new transaction entry with current date. This will help optimize the time it takes to enter a new transaction. Upon closing a transaction, a new transaction row should open with the current date in the date field. STEPS TO REPRODUCE 1. Open kMyMoney file 2. Change settings (Settings > Configure kMyMoney > Ledger > uncheck show transaction form) 3. Open a ledger OBSERVED RESULT The ledger is opened but I have to click on the New button at the bottom left hand corner (means I need to use the mouse) or using my keyboard shortcut (I added this myself not sure if it is because of using Gnome) ctrl+ i, and the new transaction form shows up. EXPECTED RESULT When inside a ledger, always have the cursor on a new transaction entry form/row. This will minimize the number of keystrokes/mouse movements the user must perform, which in turns helps to streamline the transaction entry process. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome 36 KDE Frameworks Version: KDE Frameworks Version 5.98.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION This is a wish list. This may be related to bug https://bugs.kde.org/show_bug.cgi?id=447621 but I am not sure. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459781] New: Make Account names into links in the reports
https://bugs.kde.org/show_bug.cgi?id=459781 Bug ID: 459781 Summary: Make Account names into links in the reports Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: file Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY When reading reports, I would like to have the ability to 'drill-down' into an account. If I see a large unexpected amount for an account, I would like to be able to click on it and have the ledger come up with the transactions which add up to the amount in the report on the screen. Maybe execute a filter/search on the ledger for that account based on the settings(date range) from the report. STEPS TO REPRODUCE 1. Open kMyMoney 2. open a report, income/expense 3. find an account that has any value 4. attempt to click on the account name to see the details. OBSERVED RESULT Nothing happens because the account names are not links. EXPECTED RESULT Would be really cool if we can click on the account name and have it open the ledger for that account starting at the first transaction that(by date) that contributed to the amount shown in the report. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome 36 KDE Frameworks Version: KDE Frameworks Version 5.98.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459772] disallow the change to Reconcile outside of reconciliation process
https://bugs.kde.org/show_bug.cgi?id=459772 --- Comment #2 from jesse --- (In reply to Jack from comment #1) > There have been similar discussions about this in the past, with no definite > resolution, but an agreement that the current situation allows a user to get > into an inconsistent state. It is not clear how soon this will get > addressed by the developers. One previous discussion suggested that rather > than simply disallowing to change the state of a transaction to or from "R" > except by the reconciliation process itself, the user should be notified if > any action on their part would alter the reconciliation state of the > account. This would also show up changing the amount of a reconciled > transaction, as well as the other issue you mention. > Note that you cannot really affect the reconciliation state of another > account, since a transaction is reconciled (per split, I believe) separately > in each account it touches. hmm.. I see. For the first part, about disallowing the user to click a transaction into R status, I still think it should not be as simple as a click. Reconciliation is very important and I even consider it an integrity check of the transactions. What happens when someone has to inject a transaction into an account for a time frame that has already been reconciled, for example: my checking account is reconciled as of 2021-06-01, but my credit card account shows a payment from that checking account coming out from 2021-05-31. If I add the transaction to my CC as it shows in my CC statement, it will change my reconciled checking account. I feel, instead, kMyMoney should ask the user if they want to continue(which I think it does today) and if the user does continue, it should unreconcile the transactions past that date. Another thing that would help here, is if in the ledger it showed the clear amount (already there), reconciled amount, and balance (already there). Extremely cool if there was a total for the Debits and credits at the bottom. :) All of this could be controlled by a flag in the settings: "Show All Account Detail Totals" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459773] New: Wish list: use absolute values in Charts
https://bugs.kde.org/show_bug.cgi?id=459773 Bug ID: 459773 Summary: Wish list: use absolute values in Charts Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: file Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY I noticed that if you open a liability account in the ledger, and you hit the show chart at the top, it will graph in the negative axis. In the Reports, I also see that some values are negative (Expenses and Transfers) and although, you have the option to chart the Expenses as negative(downward) or positive(upward), you cannot do that with the Transfers. I rather see the values/bar charts all be positive(absolute) values. I believe most users will understand that Expenses and Transfers out of an Asset account will reduce the amounts(meaning the values are negative). It will help make the charts a little more readable in my opinion but offering the user the choice on how they wish to see their data reported would be best. The feature is already there for Expense in the reports ( ability to choose how to graph). The Show Charts button for the ledger will need to be adjusted too. STEPS TO REPRODUCE show chart button: 1. Open any liability ledger with transactions in it with a balance 2. Click on the show chart button at the top OBSERVED RESULT Notice how the chart is showing negative in the Show Chart button EXPECTED RESULT Notice how the chart is showing negative in the Show Chart button STEPS TO REPRODUCE Reports: 1. Open any report that will show liabilities/expenses/transfers 2. Click on the Chart button and OBSERVED RESULT You will see that Expense chart downward as do transfers. EXPECTED RESULT There should be a way to ask kMyMoney to show the transfers and expenses as absolute values in the positive quadrant of the chart. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome 36 KDE Frameworks Version: KDE Frameworks Version 5.98.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION Although only a wish list item, I think it will be very helpful when I analyze my spending. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459772] New: disallow the change to Reconcile outside of reconciliation process
https://bugs.kde.org/show_bug.cgi?id=459772 Bug ID: 459772 Summary: disallow the change to Reconcile outside of reconciliation process Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Wish list: I noticed that the user is capable of clicking on the column named 'C'. This however, seems to circumvent the reconciliation process. I think the ability to move to reconcile should only be available through the reconciliation process. STEPS TO REPRODUCE 1. Open any ledger 2. for a transaction, click on the column 'C', twice. OBSERVED RESULT You will noticed the value change to C on the first click, then R on the second click. EXPECTED RESULT You should be allowed to change the state to C but not to the R - which indicates reconciled. SOFTWARE/OS VERSIONS KMY: Version 5.1.3-3408d1edc app image Linux/KDE Plasma: Fedora Gnome 36 KDE Plasma Version: n/a KDE Frameworks Version: KDE Frameworks Version 5.98.0 Qt Version: Qt Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION I know some users may never reconcile their transactions, which is fine if they do not want to. They can simply leave the transactions in 'C' clear mode. For the rest of us, I believe protecting the integrity of reconciliation may be important. The product should not allow transactions to be changed to reconciled without going through the correct process. Further, I do not know how to best handle when a transaction is injected into a ledger into a time period that is already reconciled. Maybe show a warning when the user is entering a transaction that will affect another account's reconciliation status. Or maybe, unreconcile (if that is even a word) the transactions with a date past the new injected transaction. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 --- Comment #14 from jesse --- Hi all, (In reply to Jack from comment #12) > However, didn't you say there have been particular combinations of setup and > version where this did not happen? Not really. I had mentioned in comment #2 " JV : It does not happen if I change to a different application on the same virtual desktop. ". There I just meant that alt-tab to another application or clicking on another application within the same virtual desktop did not show the same behavior. Alt-tab to an application on a different virtual desktop, still showed the same behavior. > Can anyone think of any other application that could provide a similar > situation to test? Perhaps > LibreOffice Calc with focus on a specific cell? I tested this scenario with LibreOffice Calc. I clicked on a Cell and then switched virtual desktops. It retained focus on the cell. >From what I compiled on Master, it does not seem to happen there. However, not sure what to do with this bug. This is still an issue on the current version but maybe, just maybe, it will be fixed when the new release is out. (not sure when that will be though) What is the right thing to do in these situations? thanks, Jesse -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 jesse changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #11 from jesse --- >From what I can tell this problem is there for Gnome on Wayland, xOrg and classic. I opened KMY, same app image on all three, opened a ledger, clicked on a transaction, used the keyboard keys to switch virtual desktops (nothing opened on the second virtual desktop), and switched back. The focus was lost on the selected transaction. Hopefully this helps. FYI.. another thing that I noted on version: KMyMoney Version 5.1.80-06ee79919... (master) this behavior did not occur. There it keeps the focus. thanks. I am updating the Status to Reported. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458967] RE: Setting location of weather in LinuxFX 11
https://bugs.kde.org/show_bug.cgi?id=458967 --- Comment #1 from Jesse Bassett --- Created attachment 151964 --> https://bugs.kde.org/attachment.cgi?id=151964=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458967] New: RE: Setting location of weather in LinuxFX 11
https://bugs.kde.org/show_bug.cgi?id=458967 Bug ID: 458967 Summary: RE: Setting location of weather in LinuxFX 11 Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jesse.r.bass...@outlook.com Target Milestone: --- Application: plasmashell (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.15.0-47-generic x86_64 Windowing System: X11 Distribution: Linuxfx 11.2 22.04.2 LTS DrKonqi: 5.25.4 [CoredumpBackend] -- Information about the crash: Tried setitng the location of my pc for the weather applet on windowsfx 11. However the app caused a desktop crash. The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x7f49fb968ef2 in QString::split(QChar, QFlags, Qt::CaseSensitivity) const () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f49ac9bbaa7 in DWDIon::calculatePositions(QStringList, QVector&, QVector&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/ion_dwd.so #8 0x7f49ac9bc289 in DWDIon::parseStationData(QByteArray) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/ion_dwd.so #9 0x7f49ac9be2fb in DWDIon::setup_slotJobFinished(KJob*) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/ion_dwd.so [...] #11 0x7f49fc5467e0 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 Reported using DrKonqi This report was filed against 'kde' because the product 'plasmashell' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 451646] No way to change the hierarchy for a loan
https://bugs.kde.org/show_bug.cgi?id=451646 --- Comment #2 from jesse --- Is it possible to have this as a feature request? I have ran into this before. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 451646] No way to change the hierarchy for a loan
https://bugs.kde.org/show_bug.cgi?id=451646 jesse changed: What|Removed |Added CC||jvap...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 --- Comment #9 from jesse --- Yes. It could be. Thanks Jack! I am on vacation in Mexico right now so i will not be able to test anything late next week. Thanks again! Jesse -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 --- Comment #7 from jesse --- (In reply to Jack from comment #6) > Jesse - when you respond to questions, you can change the status from > NEEDSINFO back to REPORTED. That will stop the (automated) Bug Janitor from > getting involved. > > A few additional questions: > - Is this with Xorg or with Wayland? > - Please confirm that it only happens when using Gnome and not when using > KDE/Plasma. > > Thanks. Hi Jack. Sure thing. Right now I will leave it as is because I am not home to provide the information requested. At this time I was using Gnome w/Wayland. Under Plasma, I do not recall this happening. Anyone else have Plasma installed that can test the Plasma path? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 --- Comment #5 from jesse --- Hello, Is there anything else I can provide to help with this bug? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 --- Comment #3 from jesse --- (In reply to Thomas Baumgart from comment #1) > I tried to duplicate this on a KDE desktop (Plasma) and was unable to do so. > Here are a couple of questions: > > - Does this behavior also show up when you switch to a different application > on the same virtual desktop? KMyMoney loses and regains focus in this case > already. > - How do you switch virtual desktops (keyboard sequence)? Does this behavior > also happens when you switch virtual desktops using the mouse (don't know if > this is possible at all) > - What happens if you switch to another application on the same desktop, > then switch desktops, come back and select KMyMoney again? In case the > transaction selection changes it would be interesting to know when this > happens. Also wanted to add that, I do not remember this occurring when I had Plasma installed. (I had to change to gnome for some multi-display support reasons). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 --- Comment #2 from jesse --- (In reply to Thomas Baumgart from comment #1) > I tried to duplicate this on a KDE desktop (Plasma) and was unable to do so. > Here are a couple of questions: > > - Does this behavior also show up when you switch to a different application > on the same virtual desktop? KMyMoney loses and regains focus in this case > already. JV : It does not happen if I change to a different application on the same virtual desktop. > - How do you switch virtual desktops (keyboard sequence)? JV: I use the ctrl-alt-arrowkeys to move >Does this behavior > also happens when you switch virtual desktops using the mouse (don't know if > this is possible at all) JV: yes, if I switch using the mouse click/mouse touchpad gestures, it still occurs > - What happens if you switch to another application on the same desktop, > then switch desktops, come back and select KMyMoney again? In case the > transaction selection changes it would be interesting to know when this > happens. JV: It gets reset after I switch to the next virtual desktop. Switching to the other app on the same virtual desktop as KMY, does not cause this. It seems to be when I switch virtual desktops only. There is a way in Gnome where you can see all the virtual desktops at once, and as soon as I select a different virtual warehouse, KMY scrolls to the bottom of the ledger. Hopefully this helps. I am using the app image. I can try to install the distribution's version (Fedora's repo in this case) to test if it helps. I know a lot of things look different, and maybe work different, depending on the app image vs local install version. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457484] Reconciled transaction not accepted
https://bugs.kde.org/show_bug.cgi?id=457484 --- Comment #6 from jesse --- hmm... interesting. At first I did not agree with the order of precedence, so I did not respond immediately until I could think it through a little more. Now that I have, I agree with Thomas. " order of decreasing precedence would be b), c), d) and a). " I would go with that as well. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457640] New: Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 Bug ID: 457640 Summary: Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY I am a Fedora Gnome users. Sometimes I use Plasma as well. I have noticed a small inconvenience with Gnome. I am not 100% sure if this is present with Plasma. The inconvenience is related to switching between virtual desktops. I usually have more than one virtual desktop open and more often I have KMY open in one desktop and my PDFs open in another. I switch virtual desktops using keyboard shortcuts. When using KMY, I noticed that if I select a transaction and then switch virtual desktops, it loses the focus on that transaction. If that transaction was from a while ago, say two months, it will scroll to the bottom of the ledger, past many dozens of transactions, when I return to the virtual desktop from reviewing my bank statements. This forces me to have to scroll back to find the transaction I was researching. STEPS TO REPRODUCE 1. Open a kmy file and ledger with many transaction. 2. scroll up to a transaction and highlight it by clicking it. 3. switch virtual desktops 4. switch back to the virtual desktop KMY is opened on OBSERVED RESULT The selected transaction is no longer selected and the view scrolls down to the latest transaction in the ledger. EXPECTED RESULT The ledger view should stay focused on the selected transaction. SOFTWARE/OS VERSIONS Using app image. KMyMoney Version 5.1.2-db4223684 Linux/Gnome: 42.3- fedora 36 KDE Plasma Version: n/a KDE Frameworks Version: KDE Frameworks Version 5.95.0 Qt Version: Qt Version 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION: I believe this happens as a result of losing focus on the window or window component. I do not know how this could be changed or if this is a Gnome only type of issues due to the QT working on Gnome(gtk based). maybe there is a way for the KMY software to hold in memory the last used transaction when it loses focus on the ledger. Then, when it regains the focus, read the variable to see where it left off? I have no idea.. just guessing to be honest. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457484] Reconciled transaction not accepted
https://bugs.kde.org/show_bug.cgi?id=457484 --- Comment #2 from jesse --- Hello, What I see is that there is a transaction that has been imported(not reconciled yet). In the ledger the transaction is highlighted a color to indicate that it is not yet 'accepted' post the import. Then, I reconcile the account, including the date of the transaction. The transaction is now reconciled along with the rest of the dates for the reconciliation period. I agree that a transaction should be cleared/confirmed prior to being reconciled but what I am noticing is that the transaction does not need to be 'accepted'. When you import transactions from an ofx file, for example, you need to accept the transaction. This does not auto clear/confirm the transaction, only Accepts it. In my opinion, an imported transaction should be accepted before it can be 'cleared/confirmed', and thus should definitely be marked accepted before it allows for reconciliation. But that is just my opinion and I realize that I may not be taking all possible issues into account. Let me know if that helps. I may just be way off course. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457484] New: Reconciled transaction not accepted
https://bugs.kde.org/show_bug.cgi?id=457484 Bug ID: 457484 Summary: Reconciled transaction not accepted Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY I have noticed that a transaction can be 'reconciled' but not 'accepted'. I would think that the transaction must be accepted before being allowed to be reconciled. Is there a potential reason why a transaction could be reconciled but not accepted? I figured this happened because I imported the transactions and then reconciled. I did not go through and accept each transaction. But the question in my mind is whether this should even be allowed. Maybe the reconciliation program should ask the user to accept all the transactions? Or maybe this does not matter in personal finances? STEPS TO REPRODUCE 1. import transactions but do not accept each one 2. reconcile the account OBSERVED RESULT Account is now reconciled but the transactions are still highlighted as never been accepted. EXPECTED RESULT Account is now reconciled and the transactions are accepted. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Gnome Fedara KDE Frameworks Version 5.95.0 Qt Version 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454788] Maximize vertically does not take into account increased titlebar size with touch mode
https://bugs.kde.org/show_bug.cgi?id=454788 --- Comment #2 from Jesse Laatu --- (In reply to Ismael Asensio from comment #1) > Doies the same thing happen when maximizing vertically with the button (not > through a rule)? > > Also, is this on X11 or Wayland (in Wayland this would make some.semse as > there's no native concept of partial maximizing there)? > > Thanks! I did mention wayland in the additional information, sorry if it wasn't clear. I have some issues with x11 on the setup so I have not tested that. I tested vertical maximization with a hotkey and it seems to work as expected. I was using the rules to maximize windows in both directions to have them completely maximized as there is no maximize rule. It is a tiny 4" touchscreen, so increasing the size of some elements like the touch mode does is pretty useful, I'm not sure how the 800x480 resolution affects this, but likely it is more notieceable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454788] New: Maximize vertically does not take into account increased titlebar size with touch mode
https://bugs.kde.org/show_bug.cgi?id=454788 Bug ID: 454788 Summary: Maximize vertically does not take into account increased titlebar size with touch mode Product: kwin Version: 5.24.90 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: jesse.la...@gmail.com CC: isma...@gmail.com Target Milestone: --- SUMMARY When using the Maximize vertically rule and touch mode(Workspace behavior > General Behavior > Touch Mode) together the window is maximized to a wrong size. Normal maximize works as intended. STEPS TO REPRODUCE 1. Workspace behavior > General Behavior > Touch Mode: Always enabled 2. Window rule to maximize vertically 3. trigger the rule OBSERVED RESULT Window is maximized too big vertically and overflows the screen(panel: Windows can cover) or panel(depending on panel settings) EXPECTED RESULT Window is vertically maximized as it would be when using normal maximize. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro-arm / kde-unstable KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Raspberry pi 400, 800x480 touch screen, 100% scaling on wayland. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453351] Number Field Not Maintained on Transfers
https://bugs.kde.org/show_bug.cgi?id=453351 --- Comment #4 from Jesse --- Not necessarily splits (I just use those to say part of the purchase was food and another was for medication or something), but my main use case is paying bills. I can understand that a check number only applies to the checking account, but when paying credit cards online they give you a confirmation number. I use that number to show on my checking account, but also on the credit card to show the payment was successful and to dispute if they say a payment wasn't made (or late). I suppose technically that number only applies to the credit card account. No big deal, I guess I just got so used to using it that way in other systems, and seeing it on either side was easiest without switching between accounts. I would agree to mark this as "working as intended." Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430363] Allow frame rates less than 1 for GIF export
https://bugs.kde.org/show_bug.cgi?id=430363 Jesse changed: What|Removed |Added CC||jesse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413203] Some notifications don't disappear after timeout
https://bugs.kde.org/show_bug.cgi?id=413203 Jesse Litton changed: What|Removed |Added CC||kde@eternaldusk.com --- Comment #7 from Jesse Litton --- My observation has been that low-priority notifications do the timer animation and *do* go away (which seems correct). Normal-priority notifications do the little timer animation around the close button but *do not* go away (which seems broken). Critical-priority notifications do not show the animation and do not go away (which seems correct). The change to me seems to be the way normal notifications don't hide after the timing animation like they used to. I've only really started noticing it over the last month or so in the newer plasma packages for Ubuntu Jammy. It's annoying because so many apps (Teams, Flameshot, etc.) use normal-level notifications. Unfortunately we can't just completely disable notifications from something like Teams... or we won't see an "answer this call" pop-up if someone calls you. In addition to having 'normal' priority notifications autohide after timeout, it would be great to have extra options in the notification configuration such that the *user* can decide if they want each priority to autohide (or not) after their own configurable times. And, of course, if it could be overridden on a per-app basis then all the better. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 450120] New: Debit and Credits total in ledger
https://bugs.kde.org/show_bug.cgi?id=450120 Bug ID: 450120 Summary: Debit and Credits total in ledger Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY It would be nice to have a total for the Debits and Credits in the ledger. Maybe a drop down next to it to ask the user if it should show: - Show Totals since last reconciliation - Show Totals since start of month - Show Totals since start of Quarter - Show Totals since start of week - Show Totals between (start) and (end) dates. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Currently we cannot see the running totals separately for Debits and Credits. We have to manually pull the data into an excel spreadsheet and run the totals there(usually because something is not adding up). EXPECTED RESULT See the running totals : based on a user set combo box. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome KDE Plasma Version: N/A KDE Frameworks Version: Version 5.90.0 Qt Version: Version 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 449730] New: Printing Reconciliation reports missing pages
https://bugs.kde.org/show_bug.cgi?id=449730 Bug ID: 449730 Summary: Printing Reconciliation reports missing pages Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY After reconciliation the user is presented with the option to print the reconciliation report. However, there are two tabs. Each has a print button. If the user presses the print button, it will only print the information on that tab. Not both. STEPS TO REPRODUCE 1. Open Kmy file 2. Reconcile an account 3. Print the reconciliation report to a file. 4. Open the report file. OBSERVED RESULT If the user presses the print button, it will only print the information on that tab. Not both. EXPECTED RESULT Since the report is made of two tabs, pressing the print button should print the report as a PDF with two pages. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gnome KDE Plasma Version: N/A KDE Frameworks Version: Version 5.90.0 Qt Version: Version 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION I am using the App Image version of the application KMyMoney Version 5.1.2-281f69d70 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 449707] New: Full date in ledger
https://bugs.kde.org/show_bug.cgi?id=449707 Bug ID: 449707 Summary: Full date in ledger Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY It would be nice if the ledger would show the date in full. For example: Instead of 1/1/22 it should show 01/01/22. It would be even better, if it showed the date in 2022/01/01 format. It may just be personal preference though. I am currently using Gnome. If there is a system date format setting that needs to be changed, let me know. So far I have not found one. STEPS TO REPRODUCE 1. Open any ledger account 2. go to a transaction where there is a single digit month or day 3. OBSERVED RESULT You will notice that single digit months/days, only show 1 character instead of being prefixed with 0 to be consistent in spacing. EXPECTED RESULT Preference is to show to characters per day/month. Single digits should be prefixed with '0'. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Gnome KDE Plasma Version: using gnome for now. KDE Frameworks Version: Version 5.90.0 Qt Version: Version 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 449678] Protect account from changes in already reconciled time spans
https://bugs.kde.org/show_bug.cgi?id=449678 --- Comment #2 from jesse --- Thanks for fixing the title.. I struggled on what to put there. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 449678] New: Reconciliation Allowed outside of the Reconciliation process
https://bugs.kde.org/show_bug.cgi?id=449678 Bug ID: 449678 Summary: Reconciliation Allowed outside of the Reconciliation process Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY I noticed that it is possible to mark a transaction as reconciled outside of the reconciliation process. I believe it should not be allowed. Reconciliation is an important step. I would even think that if someone changes an old transaction that has been reconciled, that the transactions after the changed transaction, should be un-reconciled, to force a review. Another good catch would be to block anyone from adding a transaction in one account that would change the reconciliation status of another account. For now, I think it would be good if it would at least provide the option to require the reconciliation process to execute before a transaction could be reconciled. The process should, as it does today, ask for a specific date and amount that the account to add up to. I hope these make sense. If not, let me know and I can expand on any of them. STEPS TO REPRODUCE 1. Just a wish list item... 2. 3. OBSERVED RESULT EXPECTED RESULT We should not be allowed to change or add transaction into a ledge account during a timeframe for which the account has already be reconciled. All reconciliations should be done through the process and not allow the user to simply change the state of the reconciliation by clicking the field. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gnome KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444561] Moving favorite items is limited to current scrollbar view
https://bugs.kde.org/show_bug.cgi?id=444561 Jesse Litton changed: What|Removed |Added CC||kde@eternaldusk.com --- Comment #1 from Jesse Litton --- It looks like this bug has gotten even worse. I noticed today that dragging items is completely disabled if scrollbars are present. If I delete enough favorites to make the scroll bar disappear, dragging is again enabled. Add one more favorite to make them appear... and no more dragging at all. So, if you have more than one screen of favorites, there's no longer any way to re-order them. Tested with 5.23.90 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 446491] Reports: Cashflow report is incorrect
https://bugs.kde.org/show_bug.cgi?id=446491 --- Comment #2 from jesse --- Created attachment 144628 --> https://bugs.kde.org/attachment.cgi?id=144628=edit Example of the bug Adding a file that shows the issue. Please see the Cashflow report. You will see that the Assets show both income and expenses.. then the total which is $10,600.00. Then you see below that Income and Expenses separately listed. If you see further below, the report does a Grand Total which is incorrect at $11,200.00. What the report did was it accounted for the income and expenses under the Asset section. Then continued to again add income and subtract expenses to get the Grant Total. So it double counted. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 446491] New: Reports: Cashflow report is incorrect
https://bugs.kde.org/show_bug.cgi?id=446491 Bug ID: 446491 Summary: Reports: Cashflow report is incorrect Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY The Cash flow report is showing Totals that are incorrect. Or at least appear to be incorrect. The report shows the list of Asset accounts, and the transactions in/out of these accounts. Further down the report, it shows the Expenses, including those that were already accounted for in the first section under the Asset accounts. The Income section also list any income transactions that occurred into the asset accounts. Again these were already accounted for in the Asset accounts section as well. Thus we are showing the assets, adding income and subtracting expense, then once again subtracting the expense and adding the income. There is a total for each section, Asset, Expense, Income. The main problem is that the Grant Total is doing Assets Total - Expense Total + Income Total. This is how we are double counting. STEPS TO REPRODUCE 1. Open Kmymoney file - with transactions 2. Go to Reports 3. Open Cash flow report OBSERVED RESULT The totals are not correct. Shows asset accounts: - Checking account - transaction: Salary +1500 - transaction: Rent -1200 - Savings account Total Assets: 300 Income: - Category/account : amount - ex: Salary: Salary: +1500.00 Total Income: 1500 Expense: - Category/account: amount - ex: Rent : -1200.00 Total Expense: 1200 Total: (Total Assets + Total Income - Total Expenses) = 300 + 1500 - 1200= 600 << incorrect EXPECTED RESULT It would be nice if the report showed as follows instead. List Accounts included in Cash Flow: - Checking account - Savings account Money into the account: Do not show each individual transaction here. - Category/account : amount - ex: Salary : 1500.00 Money out of the account: - Category/account: amount - ex: Rent : 1200.00 Total Cash Flow for Accounts: 300.00 << correct cash flow SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux - Gnome 34 KDE Frameworks 5.51.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system ADDITIONAL INFORMATION App Image: Version 5.1.2-c2865cb Potential duplicate of bug #391384 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391384] Cashflow report double-counts income as asset flow
https://bugs.kde.org/show_bug.cgi?id=391384 jesse changed: What|Removed |Added Version|4.8.1 |5.1.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 445510] Column order of Debits and Credits
https://bugs.kde.org/show_bug.cgi?id=445510 --- Comment #5 from jesse --- Ok thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 445510] Column order of Debits and Credits
https://bugs.kde.org/show_bug.cgi?id=445510 --- Comment #3 from jesse --- Hi all! Thanks Thomas for the add in feature! I can't wait to use it! How will I know what version this new feature is in? Do i need to build from source or will an app image contain it? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424480] Make the activity switching animation optional
https://bugs.kde.org/show_bug.cgi?id=424480 Jesse changed: What|Removed |Added CC||jesse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 445510] New: Column order of Debits and Credits
https://bugs.kde.org/show_bug.cgi?id=445510 Bug ID: 445510 Summary: Column order of Debits and Credits Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Most statements from institutions in the USA, show the statement in the order of Debits/Additions, then Credits/Subtractions. When I am comparing my monthly statement to the my KMyMoney's ledger, it is something I have to take into account. Is there a way to offer the ability to list the Debits first an then the Credits. For an asset account, it currently shows Payments(Credits) and then Deposit(Debits). I would rather it be the other way, Deposit(Debits) then Payments(Credits). It would be great if there is a total at the bottom. There is tons of real estate on the ledger. STEPS TO REPRODUCE 1. Open MyMoney file 2. go to an Asset, like a checking account 3. Observe how Payments is listed first then Debits. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gnome 40.4 KDE Plasma Version: N/A KDE Frameworks 5.51.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 443551] Default reconciliation state not used for new entries
https://bugs.kde.org/show_bug.cgi?id=443551 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #4 from jesse --- On the surface, I do not think we should allow transactions to be automatically entered as reconciled. However, let us consider what reconciliation was intended for. My understanding, it was intended to say that the user has compared the ledger in the program to their bank statements and accepts them as being in sync. Now, in 2021, when many people, not all, import transactions from a download provided by the institution, would we still reconcile? It almost seems like that step is no longer necessary. Back in the day when check writing was very normal still, it may have made sense. Maybe not now? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 344708] Add average column to reports
https://bugs.kde.org/show_bug.cgi?id=344708 --- Comment #2 from jesse --- I would still like to see this. :) thanks, jesse -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442052] New: transaction date vs post date
https://bugs.kde.org/show_bug.cgi?id=442052 Bug ID: 442052 Summary: transaction date vs post date Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY Allow for tracking of both transaction date and post date. After some research, it seems that most banks keep track of the post date. However, this make it very difficult for personal financing. Keep in mind the following goals: - I want to track when I made transactions for taxes purposes. Here the date on which I made the purchase or sell, matters most. - I want to keep in sych with my financial institution. Here is one scenario: I make charges to my credit card on the weekend. Most transactions, will post on Monday, not when made. The financial institution does know the transaction date, but their OFX will use the POST date. Statements do show both, transaction date and post date. In KMyMoney, I enter the transaction manually on the day it was made. But now it will not match my banks. Scenario two: Paying my Credit card bill. When I pay my credit card from my checking account, it will reflect that the transaction is pending as of the date I sent it. My Credit card will not receive the money and process it until a few days later. In Double entry accounting, both accounts have to be modified at the same time/date. Should we be using the transaction date(when I sent the payment) or when the transaction posted? Or should we keep track of both. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION It may be a duplicate or an expansion of this https://bugs.kde.org/show_bug.cgi?id=135198 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442049] New: reports: click on account to see transactions contributing to the report for the date
https://bugs.kde.org/show_bug.cgi?id=442049 Bug ID: 442049 Summary: reports: click on account to see transactions contributing to the report for the date Product: kmymoney Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: jvap...@yahoo.com Target Milestone: --- SUMMARY When looking at a report, the user should be able to drill down to the account(category) transactions at the start of the time range which is set in the report or group date range where the user clicked. Example, a report that shows the accounts balance across three months: if the user clicks on the value for a cross section of an Account and month 1, then the ledge should open for that account at the start for Month 1. This will help when users are looking back at the reports. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: - Gnome 40.4.0 KDE Frameworks 5.51.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 441690] Totals for accounts, categories and subcategories
https://bugs.kde.org/show_bug.cgi?id=441690 --- Comment #3 from jesse --- Adding to my previous post: I can see the 'Total Value' not the 'Total Balance'. As far as 'Total Balance', I cannot see that for neither the Parent or sub-category/account. In case that helps. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 441690] Totals for accounts, categories and subcategories
https://bugs.kde.org/show_bug.cgi?id=441690 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #2 from jesse --- That is weird. I am using app image: KMyMoney-5.1.2-1db6ddd-x86_64 OS: Linux Fedora with Gnome KDE Frameworks 5.51.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system When I go to the Accounts View, I have show total balance and total value, enabled but they do not show. I had to unselect them and reselect them. Another issue for later. However, when they do show, it does work as the OP suggested. In the Accounts view, I can see the total sum and, if I expand it, the total sum stays for parent. While expanded I can see the Total Value for the subcategories/account and parent. I know in the reports it does not work this way but if I understand correctly the OP is in the Accounts View, not in the reports. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 429433] Falkon tends to bind large memory usage over time
https://bugs.kde.org/show_bug.cgi?id=429433 Jesse McClure changed: What|Removed |Added CC||c...@jessemcclure.org --- Comment #3 from Jesse McClure --- FYI, we're tracking what is likely the same issue here: https://bbs.archlinux.org/viewtopic.php?id=268398 In that thread you can find a very simple tiny bit of code that should replicate the issue. I'd be curious too if Falkon users see worse symptoms of this problem on wayland than on X11. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 353555] Database backend is much slower than standard kmy format
https://bugs.kde.org/show_bug.cgi?id=353555 --- Comment #9 from jesse --- I still have not had time to try to figure out if the database has indexes or not. I don't use the application with the database option. >From what Martin said, the real need is based on using external programs to query the sqlite database. Without a way to know all the use cases, it may be best to either include documentation in the manual as to how and when a user would want to add indexes for their querying, or to add a few indexes to help our 80% of the use cases. However, I think the decision should be made as to whether saving to the sqlite format was intended for this purpose or not. If not, then perhaps there are no further changes required. -- You are receiving this mail because: You are watching all bug changes.
