[kmymoney] [Bug 461952] Adding new payee or category by typing in the transaction form triggers "Do you want to add" after typing the first character that doesn't match an existing name
https://bugs.kde.org/show_bug.cgi?id=461952 Paul Worrall changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #7 from Paul Worrall --- (In reply to Jack from comment #6) That sounds exactly like the bug I reported, so reopening -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461952] Adding new payee or category by typing in the transaction form triggers "Do you want to add" after typing the first character that doesn't match an existing name
https://bugs.kde.org/show_bug.cgi?id=461952 Paul Worrall changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Paul Worrall --- I can't reproduce it using kmymoney-master-3185-linux-gcc-x86_64.AppImage under Wayland so setting status to FIXED. I'll try and test it with a local build of git master and update the status if necessary -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 477030] Problem tag report in split transction
https://bugs.kde.org/show_bug.cgi?id=477030 Paul Worrall changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||p.r.worr...@gmail.com --- Comment #1 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 447858 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 447858] Tags not showing in Transaction Reports
https://bugs.kde.org/show_bug.cgi?id=447858 Paul Worrall changed: What|Removed |Added CC||frederic-m.r...@laposte.net --- Comment #6 from Paul Worrall --- *** Bug 477030 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 333093] Enhanced Scheduling needed
https://bugs.kde.org/show_bug.cgi?id=333093 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #9 from Paul Worrall --- Also, the *Last* #DayOfTheWeek each month (e.g. the Last Thursday) please. :-) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461952] Adding new payee or category by typing in the transaction form triggers "Do you want to add" after typing the first character that doesn't match an existing name
https://bugs.kde.org/show_bug.cgi?id=461952 Paul Worrall changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Keywords||wayland --- Comment #2 from Paul Worrall --- I also cannot reproduce on X11 so this is specific to Wayland. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461952] New: Adding new payee or category by typing in the transaction form triggers "Do you want to add" after typing the first character that doesn't match an existing name
https://bugs.kde.org/show_bug.cgi?id=461952 Bug ID: 461952 Summary: Adding new payee or category by typing in the transaction form triggers "Do you want to add" after typing the first character that doesn't match an existing name Classification: Applications Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-devel@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: --- SUMMARY When entering a new transaction, if I try to enter a new name by typing in the Payer/Payee or Category boxes, and the characters I type trigger the drop-down list, typing a subsequent character that doesn't match an existing name triggers the "Do you want to add?" dialogue making it impossible to type the full name. For example: If I already have a Payee called "Employer" and I want to create a transaction with "Pension" as a new payee, I type "P", (the drop down list appears), then type "e", the dialogue appears asking if I want to create a payee called "Pe" STEPS TO REPRODUCE (Using Payee as the example) 1. Open a book with at least one Payee already defined 2. Open a ledger 3. Start to enter a new transaction 4. Start typing in the Payer/Payee box some characters that match the name of an existing payee so that the drop-down list appears 5. Try to type further characters to define a new name OBSERVED RESULT The dialogue asking you to confirm the creation of a new Payee appears after typing one further character that does not match an existing payee EXPECTED RESULT The dialogue doesn't appear until the text box loses the focus SOFTWARE/OS VERSIONS KMyMoney: 5.1.80 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Graphics Platform: Wayland ADDITIONAL INFORMATION Sometimes two "Do you want to add" dialogues can be triggered at the same time -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461866] Transactions with no category assigned cause a "Sum of splits is not zero" consistency error
https://bugs.kde.org/show_bug.cgi?id=461866 --- Comment #2 from Paul Worrall --- Thanks for your explanation Jack, I hadn't thought of the two ends of a transaction being "splits". I can now see why uncategorised transactions are "unbalanced". Maybe it should be in the manual if it isn't already. My use case is that I have some old transactions which are uncategorised, in accounts that are now closed, that hadn't been bothering me with 5.1.3 because they didn't raise a consistency error, and I don't remember what they were for so I don't know what category to assign to them. Some of them were imported and not accepted, though accepting them doesn't of itself assign a category. I guess I could add a "Don't Know" category just to suppress the consistency report I can imagine this being raised again and again when more people start using this version of KMM Sorry for raising a bug for something that is just my misunderstanding, feel free to close this as RESOLVED/INTENTIONAL -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461866] New: Transactions with no category assigned cause a "Sum of splits is not zero" consistency error
https://bugs.kde.org/show_bug.cgi?id=461866 Bug ID: 461866 Summary: Transactions with no category assigned cause a "Sum of splits is not zero" consistency error Classification: Applications Product: kmymoney Version: git (master) Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: --- SUMMARY I have a number of transactions with no category assigned. When I save KMM these trigger a Consistency Error saying the sum of the splits on those transactions are not zero, which is not true - there are no splits. STEPS TO REPRODUCE 1. Create a transaction with no category assigned 2. Save the file OBSERVED RESULT Consistency Check saying the sum of the splits on the transaction are not zero EXPECTED RESULT No consistency check message (as per version 5.1.3), or if unassigned category is really a consistency error, a message saying something like "Category Unassigned". SOFTWARE/OS VERSIONS KMyMoney: 5.1.80 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461588] "I18N_ARGUMENT_MISSING" under Edit Account -> Hierarchy
https://bugs.kde.org/show_bug.cgi?id=461588 --- Comment #1 from Paul Worrall --- Previously fixed in other places, see: https://invent.kde.org/office/kmymoney/-/merge_requests/15/ -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461588] New: "I18N_ARGUMENT_MISSING" under Edit Account -> Hierarchy
https://bugs.kde.org/show_bug.cgi?id=461588 Bug ID: 461588 Summary: "I18N_ARGUMENT_MISSING" under Edit Account -> Hierarchy Classification: Applications Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-devel@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: --- Created attachment 153583 --> https://bugs.kde.org/attachment.cgi?id=153583=edit screenshot STEPS TO REPRODUCE 1. Right click an account and select "Edit Account..." 2. Display the Hierarchy tab OBSERVED RESULT Text at the top contains "I18N_ARGUMENT_MISSING" in two places (see attachment) EXPECTED RESULT That string is not present SOFTWARE/OS VERSIONS KMyMoney: 5.1.80 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION I'm in en_GB.UTF8 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 461557] Failure to save to samba share on remote Debian server
https://bugs.kde.org/show_bug.cgi?id=461557 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #5 from Paul Worrall --- For info: I created a samba share on my Debian server using the same config, and using KMyMoney for Linux it saves OK to that. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441801] KMyMoney crash after configure toolbar then select new view
https://bugs.kde.org/show_bug.cgi?id=441801 --- Comment #3 from Paul Worrall --- Still present in 5.1.80 (from KDE Neon Unstable repos) Easy to reproduce. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441801] KMyMoney crash after configure toolbar then select new view
https://bugs.kde.org/show_bug.cgi?id=441801 --- Comment #2 from Paul Worrall --- Also crashes after: 1. Configure Toolbar 2. Run Reconcile Wizard Application: KMyMoney (kmymoney), signal: Segmentation fault [New LWP ] [New LWP 5560] [New LWP 5561] [New LWP 5563] [New LWP 5564] [New LWP 5565] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7ff2c4ec299f in __GI___poll (fds=0x7fff887f3138, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7ff2c9be4ec0 (LWP 5493))] Thread 7 (Thread 0x7ff256bfe700 (LWP 5565)): #0 0x7ff2c25d825d in g_source_ref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff2c25d8328 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2c25d9cbf in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff2c25da312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff2c25da4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff2c56ef65b in QEventDispatcherGlib::processEvents (this=0x7ff248000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff2c569387b in QEventLoop::exec (this=this@entry=0x7ff256bfdbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7ff2c54ad442 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7ff2c54ae623 in QThreadPrivate::start (arg=0x55a3b44aee60) at thread/qthread_unix.cpp:331 #9 0x7ff2c3890609 in start_thread (arg=) at pthread_create.c:477 #10 0x7ff2c4ecf133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7ff2573ff700 (LWP 5564)): #0 0x7ff2c4ec299f in __GI___poll (fds=0x7ff250004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff2c25da36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2c25da4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff2c56ef65b in QEventDispatcherGlib::processEvents (this=0x7ff25b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7ff2c569387b in QEventLoop::exec (this=this@entry=0x7ff2573febe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7ff2c54ad442 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7ff2c54ae623 in QThreadPrivate::start (arg=0x55a3b4472b50) at thread/qthread_unix.cpp:331 #7 0x7ff2c3890609 in start_thread (arg=) at pthread_create.c:477 #8 0x7ff2c4ecf133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7ff29d80f700 (LWP 5563)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7ff2c91319b4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a3b473bcd0, cond=0x7ff2c9131988) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7ff2c9131988, mutex=0x55a3b473bcd0) at pthread_cond_wait.c:647 #3 0x7ff2c51e8e30 in std::condition_variable::wait(std::unique_lock&) () from /lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x7ff2c86c2d01 in ?? () from /lib/x86_64-linux-gnu/libQt5WebKit.so.5 #5 0x7ff2c86c2e1f in ?? () from /lib/x86_64-linux-gnu/libQt5WebKit.so.5 #6 0x7ff2c51eede4 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7ff2c3890609 in start_thread (arg=) at pthread_create.c:477 #8 0x7ff2c4ecf133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff29e847700 (LWP 5561)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55a3b44e4968) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a3b44e4918, cond=0x55a3b44e4940) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55a3b44e4940, mutex=0x55a3b44e4918) at pthread_cond_wait.c:647 #3 0x7ff2b4c1d5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7ff2b4c1d1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7ff2c3890609 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff2c4ecf133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff2b49ef700 (LWP 5560)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55a3b45f8eec) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a3b45f8e98, cond=0x55a3b45f8ec0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55a3b45f8ec0, mutex=0x55a3b45f8e98) at pthread_cond_wait.c:647 #3 0x7ff2b4c1d5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7ff2b4c1d1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7ff2c3890609 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff2c4ecf133 in clone () at
[kmymoney] [Bug 452863] New: New file setup wizard: UK VAT Accounts produces "invalid top-level account type" error
https://bugs.kde.org/show_bug.cgi?id=452863 Bug ID: 452863 Summary: New file setup wizard: UK VAT Accounts produces "invalid top-level account type" error Product: kmymoney Version: 5.1.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. File=>New 2. Personal data: Enter some personal data 3. Select currency: British Pound 4. Select accounts: Untick "I have a current account" 5. United Kingdom account types: choose "UK VAT Accounts" 6. Finish OBSERVED RESULT Error message: "Invalid top-level account type 1 in template file file:///usr/share/kmymoney/templates/en_GB/uk-vat.kmt" EXPECTED RESULT No error SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-40-generic (64-bit) Graphics Platform: X11 Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 333093] Enhanced Scheduling needed
https://bugs.kde.org/show_bug.cgi?id=333093 --- Comment #8 from Paul Worrall --- *** Bug 437726 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 437726] Add specific day of a week for Scheduler to run
https://bugs.kde.org/show_bug.cgi?id=437726 Paul Worrall changed: What|Removed |Added Resolution|--- |DUPLICATE CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 333093 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 452497] New: Scheduled transactions: "Next due date", "Number remaining" and "Date of final" do not always update in step
https://bugs.kde.org/show_bug.cgi?id=452497 Bug ID: 452497 Summary: Scheduled transactions: "Next due date", "Number remaining" and "Date of final" do not always update in step Product: kmymoney Version: 5.1.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: --- STEPS TO REPRODUCE (There are probably other ways too) 1. Create a scheduled monthly transaction with next due date in the future 2. Choose "This schedule will end at some time" (number of transactions remaining defaults to 0 with date = today -- OK) 3. Increment number of transactions until it gets to 12 (date of final transaction updates correctly) 4. Click OK to save the schedule 5. Edit the schedule just created and decrement the number of transactions to 11 (final date updates OK) 6. Increment the number of transactions back to 12 OBSERVED RESULT Date of final transaction does not update in the final step EXPECTED RESULT Date of final transaction updates OK SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-39-generic (64-bit) Graphics Platform: X11 Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR ADDITIONAL INFORMATION There is something wrong with the logic that updates these fields -- in my 'live' database I have schedules that show e.g. number of transactions = 10, but date of final corresponds to 12 payments, and if I increment the number of transactions, to 11 it decreases the date of final to correspond correctly. A consequence also seems to be that reports that show scheduled transactions do not show the right number. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 429469] Text not visible in print-out when using dark theme
https://bugs.kde.org/show_bug.cgi?id=429469 Paul Worrall changed: What|Removed |Added CC||kdebugs.20.orzelf@spamgourm ||et.com --- Comment #5 from Paul Worrall --- *** Bug 451994 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 451994] Unreadable print with dark theme
https://bugs.kde.org/show_bug.cgi?id=451994 Paul Worrall changed: What|Removed |Added Status|REPORTED|RESOLVED CC||p.r.worr...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 429469 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446680] New: Filtering report on amount with large limits changes the limits by mis-interpreting scientific notation
https://bugs.kde.org/show_bug.cgi?id=446680 Bug ID: 446680 Summary: Filtering report on amount with large limits changes the limits by mis-interpreting scientific notation Product: kmymoney Version: 5.1.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-devel@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: --- Set up a report that is filtered on amount, e.g. from 1000.00 to 100.00, then go back into "Configure": the large amount has been changed to 106.00. This seems to be 10^6 incorrectly reformatted to 106. Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: X11 Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 411272] Not saving changes to Shortcuts
https://bugs.kde.org/show_bug.cgi?id=411272 Paul Worrall changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=441190 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441190] keyboard shortcut conflict
https://bugs.kde.org/show_bug.cgi?id=441190 Paul Worrall changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=411272 CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441937] New: Default cash flow report: Name does not match date range
https://bugs.kde.org/show_bug.cgi?id=441937 Bug ID: 441937 Summary: Default cash flow report: Name does not match date range Product: kmymoney Version: 5.1.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: reports Assignee: kmymoney-devel@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: --- The default cash flow report is named "Cash Flow Transactions This Month", but the date range filter is set to show "Year To Date" -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441801] KMyMoney crash after configure toolbar then select new view
https://bugs.kde.org/show_bug.cgi?id=441801 --- Comment #1 from Paul Worrall --- Also reproducible on current v5.1.80 under KDE Neon Unstable -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441801] KMyMoney crash after configure toolbar then select new view
https://bugs.kde.org/show_bug.cgi?id=441801 Paul Worrall changed: What|Removed |Added Assignee|unassigned-b...@kde.org |kmymoney-devel@kde.org Component|general |general Version|unspecified |5.1.2 Product|kde |kmymoney -- You are receiving this mail because: You are the assignee for the bug.
