[kmymoney4] [Bug 371069] CSV plugin mishandles UTF-16 files

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371069

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #6 from Jack  ---
I think you might be able to use dos2unix to modify the file into a usable
format, or at least confirm info about the encoding and BOM.  It may take a
while to wade through all them options and parameters.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 371398] New: Graphics glitches out when using firefox.

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371398

Bug ID: 371398
   Summary: Graphics glitches out when using firefox.
   Product: plasmashell
   Version: master
  Platform: Other
   URL: https://drive.google.com/drive/folders/0BzmacKNa7tvrX1
BfWE1SQzg2SWM?usp=sharing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Look & Feel package
  Assignee: plasma-b...@kde.org
  Reporter: one.sna...@gmail.com
CC: plasma-b...@kde.org

Text is unreadable while typing. Its impossible to highlight text. Tabs also
glitch out. Random things disappear.

Reproducible: Always

Steps to Reproduce:
1. Open firefox. 
2. Open new tabs, type etc. It completely loses it


Actual Results:  
Text is unreadable while typing. Its impossible to highlight text. Not sure
whats happening top tabs but they glitch out as well.

Expected Results:  
Have firefox work normally

I have videos of it glitching out. Its rather hard to explain. I just got
Kubuntu by the way.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 370242] "Geldinstitute": "Konten ohne zugewiesene Geldinstitute" cannot delete

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370242

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #3 from Jack  ---
If you run the consistency check again, are there still any reported issues? 
The first time you ran it, it might have fixed many issues; we are interested
if there are any it couldn't fix automatically.  They may not be important, but
we don't know until we check.

4.6.6 is now somewhat old.  You could get the latest 4.8 by using Claydoh's PPA
on launchpad.  (https://launchpad.net/~claydoh/+archive/ubuntu/kmymoney2-kde4)

The slowness is probably not related to the first problem, so we should
concentrate on the deletion issue first.  I can't think of any reasons to
prevent deleting an institution other than if there are accounts in it.  Is it
possible there are any closed and hidden accounts?  (Go to Configure KMyMoney. 
Click on General (top icon on the left) then click the Filter tab.  Be sure "Do
not show closed accounts" is not checked.)  If that is not it, we'll have to
wait for other ideas.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 370242] "Geldinstitute": "Konten ohne zugewiesene Geldinstitute" cannot delete

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370242

--- Comment #1 from Jack  ---
If you just hover the mouse over that institution, does any tooltip display,
possibly showing the reason you cannot delete it?  Are there any accounts in
that institution?  If so, you will not be able to delete it.

Also, can you run a consistency check?  Does it show any problems?

One other thing to try is to run KMyMoney from a konsole command line.  It
might show more information about any problem with the file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 364425] CSV import only shows checking accounts when selecting Banking

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364425

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #8 from Jack  ---
Ralf - it is possible (but not easy) to run a newly compiled version of KMM.  I
use a specific install prefix just for that purpose - I don't think it will
work directly from the build dir since I'm not sure all the directories are in
the (relative) expected location.  It involves setting some KDE env variables
and running kbuildsycocaX where X is 4 or 5.  Actually, I have separate
locations for 4 (4.8.0) and 5 (frameworks from master).  I'll be glad to post
the script I use to the dev mailing list if there is interest.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 369448] ofx import results in duplicate transactions

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369448

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #2 from Jack  ---
I can confirm this is the problem.  In a downloaded qfx file, BOA uses
something like
201609101 but in a direct connect download, it uses
D2016254T1048539.  There are other differences also (at least in my
example) such as the file not including the  (which in the direct connect
seems only to be part of the  anyway, but it is the FITID difference that
causes KMM not to recognize the duplicate transaction.

Unfortunately, I predict 0% chance of getting BOA to fix this, since it seems
absolutely impossible to talk to anyone who knows anything and can do anything
except follow their script.  In any case, I'm really curious if anyone has any
idea why they re-enabled direct connect, after going to all that trouble to
discontinue it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 369448] ofx import results in duplicate transactions

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369448

--- Comment #1 from Jack  ---
When you say you did an OFX update, did you download a new file, or did you
actually succeed with an OFX Direct Connect?  If the latter, I suspect that the
download included transaction IDs (which KMM uses to uniquely identify
downloaded transactions) which were NOT present in the previously downloaded
qfx file.  If that is the case, then you should not have this problem again,
unless mixing direct connect downloaded transactions with those imported from
file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 369438] New: Allow selection of OFX tag to use for Payee, even if account not mapped

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369438

Bug ID: 369438
   Summary: Allow selection of OFX tag to use for Payee, even if
account not mapped
   Product: kmymoney4
   Version: git (master)
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: ostrof...@users.sourceforge.net

If an account is mapped to an online account with libofx, under the
Edit/Account, Online Settings tab, Import Details subtab, there is a dropdown
"Payee's name is based on contents of the OFX tag" with choices of PAYEEID,
NAME, and MEMO.  This is not present under aqbanking or if the account is not
mapped, so it cannot be specified for OFX file imports.  

As it seems an increasing number of institutions making it increasingly
difficult for KMM to use OFX Direct Connect, this it becoming an increasingly
common issue.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 277041] "Pay to" text box unexpectedly changes when changing field from OFX import

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=277041

--- Comment #2 from Jack  ---
With no feedback or evidence it still happens, should this be closed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 368593] KmyMoney File Not opening and gives error As " Please use an older version...."

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368593

--- Comment #8 from Jack  ---
>From the piece of the file shown in Comment 4, it does not look like anything I
would expect in a KMM file.  You might try running 'strings
"/media/paarkavin/Paarkavin/Ex1/YaArO/yAaRo - Sep-16.kmy" | more' to see if you
can tell anything more about where that file might have come from, in case it
gives you an idea when or how the corruption happened.  
You don't say which distribution you are using, but it is possible (although
unlikely) that one of the file recovery programs (google for recovering deleted
files) might find something.  Unfortunately, the more you use the filesystem
before remounting it read-only, the less likely this will succeed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 363151] Crash when editing project configuration

[Rex Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363151

Rex Jack  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from Rex Jack  ---
with Version 5.0.0 it is fixed

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 367869] Wishlist item - Update stock prices via crond

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367869

--- Comment #1 from Jack  ---
A variant on this would be to allow command line switches for all appropriate
menu items.  Having the program not need to open any windows at all for these
non-interactive sessions would also be useful.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 365408] 4K 3840x2160 screen with HiDPI setting, icons, checkboxes are too small

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365408

--- Comment #1 from Jack  ---
Kernel: Linux 3.19.0-32-generic (x86_64)
Compiled: #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015
Default C Compiler: GNU C Compiler version 4.8.4 (Ubuntu
4.8.4-2ubuntu1~14.04.3)
Distribution: Linux Mint 17.3 Rosa
Hardware: MSI GS72 6QE-206NL (Stealth Pro 4K)
Resolution: 3840x2160 pixels

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 365408] 4K 3840x2160 screen with HiDPI setting, icons, checkboxes are too small

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365408

Jack  changed:

   What|Removed |Added

 CC||i...@jacksoft.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 366130] when reconciling, the opening balance is incorrect

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366130

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
The opening balance on the reconciliation wizard is really for information
only, and does not actually contribute to the calculation.  As long as the
final balance matches, you are OK.  However, what is the difference between the
KMM opening balance and the statement opening balance?  See if you can find one
or more transactions adding up to that amount.  That might at least give you a
clue to what happened.  KMM calculates the opening balance by summing up all
the reconciled transactions in the account.  That should be the same as the
closing balance of the previous reconciliation.  The most likely way it could
change would be if one or more transactions had the status changed either to or
from reconciled to anything else.  

Unfortunately, I do not know of any way to revisit a previous reconciliation -
unless you have a backup from the right time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345655

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #40 from Jack  ---
This has actually been instructive for me - that reconciliation error I have
seen has always been in investment accounts, and I certainly have increased
precision in many of the equities.  Now I'll have to watch for it to happen
again, and see if I actually do have similar rounding problems that have simply
never been large enough to be obvious in any of the visible transaction
amounts.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345655

--- Comment #33 from Jack  ---
(In reply to sven.keller from comment #31)
I do not know exactly what that particular error message is in tended to say. 
I get it fairly often, with no apparent issued with the account.  As Alan said,
review everything in the account since the previous reconciliation to assure
the correct status of all transactions.  However, given the same account
balance, cleared balance, and online balance, it is possible there really are
not any problems, other than the spurious error message.

Make lots of backups!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365366] Can not download new Version

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365366

--- Comment #6 from Jack  ---
Unless you can compile it yourself, I suspect you will just have to keep
checking the web page for an announcement.  In the past, only one person has
succeeded in compiling it for Window, although I believe multiple people are
currently trying to do so.  The problem is that the entire effort related to
KDE on windows is going towards the Frameworks migration effort, and 4.8 is
still pre-frameworks, so it is difficult to get assistance with any problems
that arise.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365366] Can not download new Version

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365366

--- Comment #3 from Jack  ---
Devels:  there appears to be no 4.8.0 download for windows.  The windows
download still points to 4.7, and the 4.8 download points to source.

James:  please tell us EXACTLY what you have tried.  What link are you clicking
on https://kmymoney.org.  Right now, the download link points to a source file,
which won't help you on Windows.  The windows download link points to 4.7.2,
which is probably what you are currently running.  Also, please post EXACT

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365307] Download

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365307

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #3 from Jack  ---
James - you need to provide more information.  Exactly what URL/web site are
you using to download?  What is the name of the downloaded file?  What is the
exact error message?  Please confirm that you get the error when trying to run
the downloaded file, and not when downloading.  As Allan said, you do not need
to register anywhere to download or install or use KMyMoney, but we can't help
you without more information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365366] Can not download new Version

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365366

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
You already filed a bug - use that one.  No need for duplicate reports.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 365408] New: 4K 3840x2160 screen with HiDPI setting, icons, checkboxes are too small

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365408

Bug ID: 365408
   Summary: 4K 3840x2160 screen with HiDPI setting, icons,
checkboxes are too small
   Product: kate
   Version: 3.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: i...@jacksoft.eu

On a 4k laptop with Linux Mint 17.3, using HiDPI,
some icons (in file tabs) and some filetabs, as well as icons in the setting
menus and check boxes are not scaled properly.
I think using the HiDPI setting, they should be 2x bigger in size.
The text is scaled correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365307] Download

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365307

--- Comment #1 from Jack  ---
You need to provide more information if you want help.  Where were you trying
to download from?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 365177] Changing investment fraction doesn't change rounding behavior

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365177

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
Please clarify:  do you see the correct numbers after restarting KMM?  If so,
the issue is not that the rounding behaviour isn't change, but that it isn't
changed immediately, and requires a restart of KMM to take effect.  One is a
real bug, the other is simply an inconvenience, although it might be possible
to have the change take effect immediately.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 364487] I wish I could hide accounts / categories in reports AND roll up there amount in parent

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364487

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #4 from Jack  ---
(In reply to Hugo from comment #2)
While I am not formally trained in accounting, I don't think there is any
problem suppressing accounts in a report.  In fact, I don't see this as
suppressing anything, you are just reporting summary information, not full
details.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 364487] I wish I could hide accounts / categories in reports AND roll up there amount in parent

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364487

--- Comment #1 from Jack  ---
By "hiding" do you actually mean not including them by unchecking them on the
configuration page?  As you realize, that is not hiding them, it is not
including them at all.  I think one way to describe what you want is to have
separate "include" and "display" checks for each account/category/...

Have you tried exporting the report to excel?  It would still be work, but not
require manually redoing the sums.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345655

--- Comment #12 from Jack  ---
First, sorry I didn't recognize that as a typo. :-)
Second, I'm going to have to review the details of this bug in more detail to
be sure I really understand what is happening before I make any
recommendations.  I do agree that there are issues with rounding, especially
with investment accounts and securities that are tracked at many decimal
places.  

For now, there are a few things you might do.  First, can you create a test kmy
file that shows the issue?  Just the investment and the checking accounts, for
example.  Will the mismatch happen even if you manually enter the bank
transaction at exactly 100?  If so you could send the file, so someone can look
to see what is happening.  You can also do that yourself.  A .kmy file is just
a gzipped xml file.  (Always make a backup!)  If you can find the various
transactions in the file, you can see how KMM is exactly recording the amounts.
 The other option is that you could see if you can create an anonymized file,
and post that, if it still shows the problem.

Separately, even if you cannot directly map  your KMM account to your online
investment account, see if your broker lets you download the transactions -
hopefully as OFX or possible QIF.  KMM can import either of those.  You can
work separately to see if you actually can do a direct connect to your broker.

One other thing to check is the default precision set in KMM.  Select the
Settings/Configure KMyMoney menu item, and on the General view, the Global tab,
what is the Price precision set to?  Mine is set to 4 digits.  I'm not certain,
but I think that may affect the precision to which things are rounded (but not
necessarily displayed).  I certainly agree that if it is saying that 100 != 100
(I use dollars not pounds, but I don't think that should matter) then something
is amiss.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345655

Jack  changed:

   What|Removed |Added

 CC|ostroffjh@users.sourceforge |
   |.net|

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345655

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #9 from Jack  ---
As I understand it, all current developer time is going to the conversion to
KDE Frameworks.  This issue is unlikely to be addressed until after that is
complete.  

In addition, while this may certainly be annoying, if does not make KMM
useless.  I track several investment accounts in KMM, with multiple brokers,
and it works just fine for me.  Remember, nobody is being paid to work on KMM. 
(You may also want to be careful about your choice of words, as "sued" has a
particular legal implication in English, definitely in the US.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 275043] Assignment of recipient by MEMO-Tag when importing data

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=275043

--- Comment #1 from Jack  ---
Isn't this now possible?  Perhaps this bug was just missed when the feature was
added.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 363151] New: Crash when editing project configuration

[Rex Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363151

Bug ID: 363151
   Summary: Crash when editing project configuration
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rexj...@gmx.de

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.5.1
Frameworks Version: 5.21.0
Operating System: Linux 4.4.2-hardened x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
1. Opened Project/Open Configuration/Language Support
2. Added or deleted include path
3. Pressded OK (whithout pressing Apply before)
4. Kdevelop crashed

Workaround: Press Apply before pressing OK

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd3016467c0 (LWP 17359))]

Thread 21 (Thread 0x7fd2f7fff700 (LWP 17385)):
#0  0x7fd315eb03af in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7fd2fe47ee03 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/r600_dri.so
#2  0x7fd2fe47e437 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so
#3  0x7fd315eaa5e6 in start_thread () from /lib64/libpthread.so.0
#4  0x7fd31ca789ad in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7fd2ec873700 (LWP 17413)):
#0  0x7fd315eb0758 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7fd31d12b078 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7fd31abcf4d8 in KDevelop::DUChainPrivate::CleanupThread::run() ()
from /usr/lib64/libKDevPlatformLanguage.so.10
#3  0x7fd31d12a9b2 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7fd315eaa5e6 in start_thread () from /lib64/libpthread.so.0
#5  0x7fd31ca789ad in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fd2e288b700 (LWP 17415)):
#0  0x7fd31ca6f46d in poll () from /lib64/libc.so.6
#1  0x7fd314404e5c in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fd314404f8c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd31d32dc6b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fd31d2ddb0a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fd31d125d96 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fd31d12a9b2 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fd315eaa5e6 in start_thread () from /lib64/libpthread.so.0
#8  0x7fd31ca789ad in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7fd2dad85700 (LWP 17417)):
#0  0x7fd315eb03af in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7fd31d12b09a in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7fd312ef2d77 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fd312ef7388 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fd312ef1e05 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fd312ef73e2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fd312ef1e05 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fd312ef73e2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fd312ef1e05 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fd312ef73e2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fd312ef1e05 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fd312ef4d35 in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fd31d12a9b2 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#13 0x7fd315eaa5e6 in start_thread () from /lib64/libpthread.so.0
#14 0x7fd31ca789ad in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7fd2da584700 (LWP 17418)):
#0  0x7fd315eb03af in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7fd31d12b09a in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  

[kmymoney4] [Bug 351874] QIF import of investment buys and sells mishandles commissions

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=351874

--- Comment #5 from Jack  ---
I import to investment accounts from OFX frequently, and it works just fine. 
(Well, mostly, but my problems are mainly in what my broker provides, not how
KMM handles it, and I've complained about it in the past on the mailing list.) 
I can probably provide some example files, but I'd have to choose carefully for
ones that  don't show any of the problems.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 363069] Wrong accounts are presented during import of investment statement

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363069

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #5 from Jack  ---
I can't comment on the code itself, but in the initial bug report, you talk
about csv import, but it looks to me like your proposed changes will apply to
any import.  How are you checking that the import is for an investment account?
 If there is actually something in the import, this is great.  If it is only
because you have to specify that it is an investment import for the csv
importer, then it should be restricted to that situation.  If the proposed
changes actually take care of that, you can ignore my comment.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 362384] Cannot enter transaction with postdate prior to account's opening date error

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362384

--- Comment #1 from Jack  ---
The "account" can be either the account in which you are entering the
transaction, or the category to which you are assigning the transaction. 
Remember, KMM treats categories internally as accounts.  If you can change the
category after entering the transaction, and the transaction date is prior to
the opening date of the category, that should probably count as a bug. 
Categories generally get opening dates of the date they were created, which
does lead to this error.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 362263] OFX import transactions inherit split from preexisting transaction

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362263

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
I can confirm I've seen this behavior in the past.  It appears that KMM takes
an imported transaction, and even if it doesn't actually  match it to an
existing transaction, if the closest match (although I have no idea what
criteria it might use) is a split transaction, then it makes the imported one
split also.  It's been a while since I've seen it, but as I recall, it's not
too hard to remove the extra/unneeded split, and make the transaction as it
should be.

Note that I can imagine some cases where this behaviour could be desired, such
as for a pay check, and you have set up splits to handle various deductions. 
However, I think most of the time, it is not desireable.  As much as I hate
adding to configuration options, or pop-ups for the user to specify details
about an import, I think the right solution to this requires one or the other -
either a setting to say never create a split transaction on import, or a pop-up
stating the import matched a split transaction - should it be used or not.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 361865] Dialog uses 'share' when in fact referring to shares and/or bonds (i.e., securities)

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361865

--- Comment #4 from Jack  ---
> --- Comment #3 from allan  ---
> Out of interest, what is the distinction between the original term and the
> proposed revision?

There are two separate bugs in question here.  The first, about the 
German translation, had a specific suggestion - to use a word that is 
not specifically restricted in referring to stocks only.  Burkhard Lueck 
suggested to file a separate bug against the original English, so the 
translators would have a better context.

My position is that the English should not be changed, which leaves open 
the question of how to improve the context for the translators.

Your point about the extent of use of the term "share" suggests that it 
should be reviewed at a higher level, but for this specific pair of 
bugs, I think the only place to focus is in four of the specific types 
of investment transactions which mention "shares" specifically buy, 
sell, add, and remove.

My understanding is that the original term is equivalent to "share" only 
as it means the same as stock.  The suggested replacement seems to be a 
more generic term, similar to "security."   In English, I would argue 
that you buy shares of a security (stock, bond, or mutual fund) but not 
the security itself, although I admit it might be a difference only to 
English teachers.  I'm willing to leave it up to the German speakers 
whether the difference is important in that language.  In addition, if 
we can specify the context somehow, then it can be dealt with an any 
translation, in case it does make a difference.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 361865] Dialog uses 'share' when in fact referring to shares and/or bonds (i.e., securities)

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361865

--- Comment #2 from Jack  ---
I believe the underlying problem is that English is just sometimes a 
messy language.  In discussing investments, the word "share" seems to be 
used in two slightly different ways.  (I am referring to common usage, 
not to a formal dictionary definition.)  Sometimes it is used as an 
equivalent word for stock, as in the article referred to by the link in 
the original post.  The other use is to refer to the unit of investment. 
  This is certainly used for both stocks and mutual funds.  I have not 
found any particular examples of this use for bonds, but I believe the 
term is used in the same way.  If we do not accept this, what term would 
be used for the unit of ownership of a bond?.

I will try to get a short lesson next week from my investment advisor to 
confirm this, but unless he says something I do not expect, I would 
argue to leave the English terms unchanged.  If that is done, we will 
have to find a way to inform the translators that "share" in those four 
terms is used as the unit of investment, not a particular type of security.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 361850] Error in German translation

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361850

--- Comment #4 from Jack  ---
I also responded to the other bug to say that I believe the English 
terms are OK as they are, although I will do more research to see if 
there is anything to support that "share" does not apply as well to 
bonds and mutual funds as to stocks.

I don't speak German, so I can only assume the bug is correct that the 
current German translation uses terms which only apply to stocks and not 
to bonds.  (What about mutual funds?).  As I am not currently sure where 
in the code the terms exist, I do not know if there is any reasonable 
way to put a comment or hint that translations should use a term which 
applies equally to stocks, bonds, and mutual funds.

(I am not a developer, but I do maintain the documentation for KMyMoney, 
and I will certainly make a note to check that the handbook is correct 
and accurate in use of all these terms.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 361865] Dialog uses 'share' when in fact referring to shares and/or bonds (i.e., securities)

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361865

--- Comment #1 from Jack  ---
As a native English speaker, I do not see a problem.  To me, a "share" 
is the unit of ownership of a security, whether it is a stock or bond or 
mutual fund.  The link provided shows a difference between stocks and 
bonds, but is not explicit enough that "shares" does not also apply to 
bonds.  I will do more research before wanting to change the English 
terms.

To discuss the terminology further, I don't consider that I buy a 
security.  I buy shares in that security.  The first time I buy shares 
in a given security, I do have to add that security to the list of those 
in which I own shares, but when I buy more shares, I don't buy that 
security again.  I'm not sure I can perfectly explain the grammar, but 
the current use seems good.

I will respond directly to the other bug to discuss changing the German 
translation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360938

--- Comment #15 from Jack  ---
On 4/2/2016 1:14 PM, via KDE Bugzilla wrote:
> Then I did another CC on the DB and this time it reported identical output but
> at the bottom:
>
> Finished: 0 problems corrected. 111 problems still present.
That is not really as bad as it looks.  All those errors about account 
opening dates are from recent changes to the program, so you would not 
have seen them previously.  However, I don't think any of these errors 
should cause a crash.  The first step is to recover your data and let 
you keep working.  After that, if saved a copy of the bad database, then 
at a lower priority, it might be possible to find the source of the crash.

The issue is that an account should not have any transaction with a date 
earlier than the opening date of the account.  In KMM, payees and 
categories are internally treated as accounts, and when they are 
created, their opening date is the date they were created, not the date 
of the first transaction.  This is where most of these issues come from.

As you saw, KMM was able to fix most of those errors by altering the 
opening date of the account.  For the others, you can try to manually 
edit the account and change the opening day to be early enough.  In 
general, the best way I have found to do this is to open the ledger for 
the target account, then click the edit account icon (if you have it 
displayed) or else select the Account/Edit menu.  It seems the "Opening 
Balances" account is a bit difficult to find - but the first transaction 
in the ledger for most other accounts is the initial transfer of the 
opening balance for that account, so you can right click on the 
transaction, and there should be a choice "Go to 'Opening Balances"'.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360938

--- Comment #12 from Jack  ---
Well, if you don't have a backup copy of the small database before fixing, then
capturing the fixes is no longer an option.

Different sizes of databases containing the same content does not surprise me
too much - there are lots of local configuration issues like block size,
minimum table size, ... (I'm mainly guessing, but I do have some database
background.)

Unfortunately, it sounds like running a debugger would be too difficult for
you.  The simple explanation is that you run the debugger, and it runs
KMyMoney.  If it has the right information (source code and debugging symbols
compiled in) then you can watch how it runs in the source code, and can set
breakpoints (places it just stops for further instructions instead of just
going on.)  It can be very useful for a developer, as you can also examine the
value of variables, so if you know where it blows up, you can set a breakpoint
a few lines earlier, or before it calls that function, and explore the state of
things right before the problem.  Unfortunately, it is not something to learn
quickly.  

One thing I just thought of - can you reinstall an earlier  version, where you
were not getting the crash?  If so, you might be able to save as a file, or
even as an anonymized file.  Then you could try the new version, or submit the
anonymized file to the developers.  (An anonymized file changes all account
numbers and all actual financial values - changing them to random values.)

I suppose it would be helpful if we could replicate the consistency checks as
sql queries, but I'm not sure how difficult that would be.  Maybe one of the
developers who works specifically on the database back end can make a
suggestion.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360938

--- Comment #9 from Jack  ---
I'm pretty much guessing here, but if you can capture the 27 errors that were
fixed in the smaller version, can you make those corrections manually on the
larger version? If so, you might get farther in then saving the larger one as a
file.  

Am I correct that it crashes either running the consistency check on the larger
database, and also crashes trying to save that database as a file, probably
because it runs the consistency check.  If so, I would try to figure out from
the backtrace (perhaps running in a debugger?) and try to trap the error, so
although it may not correct the error, it wont just abort.  That may also show
you what it is choking on, and you might be able to fix it manually.  I don't
know if the Claydoh repository includes a version with debug symbols, but if
so, that would produce more useful backtraces and be easier to run in a
debugger.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 361246] Kmymoney won't start

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361246

--- Comment #3 from Jack  ---
As Allan pointed out (although it was only to the mailing list, not to the bug)
you are running a frameworks version of KMyMoney.  This has not yet been
released, and it is not really ready for production use.  4.7.2 is the most
recent official release, but it still uses kdelibs, not frameworks.  I'm not
sure why they chose to package this version (from git - not released) since it
obviously doesn't work.  The frameworks version is still under development, but
there is not yet a proposed timeline for release.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 361246] Kmymoney won't start

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361246

--- Comment #1 from Jack  ---
What version of KDE do you have installed?  I'm very curious about the KBanking
message - I don't use it myself, but in my case, I do see "KMyMoney kbanking
plugin loaded, and I'm still using Qt4.  Can you do from a command line "ldd
`which kmymoney` | grep -i qt" and post the results?

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 347008] Konsole does not start, process list shows several konsole instances as "defunct".

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347008

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #3 from Jack  ---
I also see this, with kubuntu 15.10 running as a vbox guest.
konsole 15.0.8.0
kde frameworks 5.15.0
qt: 5.4.2

It happens if I try to launch from within the VBox instance, or even if I ssh
-Y in from the host (Gentoo).  Doing a ps from that ssh session often seems to
show some drkonqui instances, but I can't figure out how to get the full
information from any of them.

In the KUbuntu - if I do Alt-Tab, I can see the konsole instances with a square
frown face icon, but nothing actually shows up as a visible window.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360938

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #7 from Jack  ---
Aside from doing more backups :-) the first thing I would do is to see if it
also crashes using a file instead of a database.  If it works with a file, but
crashes with the database, that helps focus where to look for the problem.  You
might also try testing with a newly created (and thus essentially empty) file
and database.  That would show whether the crash has anything to do with your
data or not.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361021

--- Comment #5 from Jack  ---
Without looking at the details, I believe this is not a problem with the CSV
importer, but with any KMM import of an investment transaction which requires a
brokerage account for transfer of funds.  (I have it with OFX import.) The
issue is that when KMM imports an investment transaction, it does not specify
the brokerage account, so the missing assignment refers to the amount which
would go to that account.  When you edit the transaction, KMM automatically
enters the brokerage account, so the error disappears.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 352954] Report: Transactions by Reconciliation Status does not correctly honor selected state in config

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352954

--- Comment #3 from Jack  ---
Unfortunately, it's not really my bug - I just filed for someone on the mailing
list.  It may be a few days before I have time to look at this again, and if
necessary ask on the mailing list if he still has the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360379] kmymoney don't start -->kmymoney: symbol lookup error: kmymoney: undefined symbol: _ZTI9onlineJob

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360379

--- Comment #9 from Jack  ---
Thanks for following up.  Since it now works for you now, I would guess that it
was a transient issue related to dependencies, and they fixed it between
between when you updated, and when you just reinstalled.  I suppose we can
close as "worksforme"

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360379] kmymoney don't start -->kmymoney: symbol lookup error: kmymoney: undefined symbol: _ZTI9onlineJob

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360379

--- Comment #7 from Jack  ---
Hopefully I will get a chance to try this in a Kubuntu Virtual Box guest soon,
but I wonder if the ubuntu package missed a dependency on either KBanking or
one of the other  online-banking pieces.  If the packager had it installed, but
the end user does not, it might produce this  error.

Soulrebell: would you please provide the exact Ubuntu package version of KMM
you have.  That will help just in case we need to file a bug  report with
Ubuntu.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360379] kmymoney don't start -->kmymoney: symbol lookup error: kmymoney: undefined symbol: _ZTI9onlineJob

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360379

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #3 from Jack  ---
It sounds to me like a linking symbol, not a stock symbol.  Is it possible the
Ubuntu package has a compil/link problem?

Also - .kmy files are generally gzipped, so you would need to make a copy of
it, renaming to something like X.xml.gz.  Then gunzip that file.  Then you can
look at X.xml with any text editor.

I do agree with Allan suggestion to try "kmymoney -n" from a command line.  If
that fails, then the error has nothing to do with your file.  If it succeeds,
and you still get the error when opening your .kmy file, then something is
funny in the file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 359975] New: don't expand display of all accounts when closing an account

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359975

Bug ID: 359975
   Summary: don't expand display of all accounts when closing an
account
   Product: kmymoney4
   Version: git master
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: ostrof...@users.sourceforge.net

In the Accounts view, if I right click on an account and close it, the entire
display gets redrawn with the account hierarchy fully expanded, even if it was
all collapsed prior to the close.  This can be annoying if I'm specifically
trying to work only within one account and its subaccounts.  I don't know if
this is an explicitly action in the code, or a side effect of  redisplaying the
tree view.

Reproducible: Always

Steps to Reproduce:
1. Select Accounts view, List tab
2. Right click an account and select "Close account"
3.

Actual Results:  
The view is redraws, fully expanded.

Expected Results:  
The expansion or collapsed state of the tree is not changed.

I'm calling it wishlist, but minor would also be OK.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 359659] Wrong payee matching for new payees during OFX import

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359659

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
OFX and QFX are different names for essentially the same format.  

If multiple transactions are being matched to the same payee, please check that
payee to see if there is an extra matching entry with perhaps just a single
blank.  In the Payees view, select the payee to which everything is matching,
then select the "Matching" tab, and see if there is an entry which might
(inappropriately, but correctly) match all the imported transactions.  I don't
remember the details, but I remember this being found as a problem in the past.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 249363] "Map to Online Account" cannot distinguish different accounts properly

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=249363

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #10 from Jack  ---
If you have two accounts mapped, and then unmap one, when you go to remap that
account, it will only show you the one which is currently unmapped.  I don't
know if it will change anything, but if you unmap both accounts, and then try
remapping, you might get the right one to each account. (This is only a guess
on my part, based on some of the comments.)  Another thing you might try, is to
check the full ofx log.  If you create an empty file in your home directory
called ofx.log, then after you connect, it will contain a log of the OFX
session.  I would try that with both accounts unmapped, and then again after
you have mapped one of the accounts.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 342401] allow different payees on splits

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=342401

--- Comment #8 from Jack  ---
Interestingly I just ran into this - I had made a deposit earlier in the year,
including checks I received from three different sources.  I had a great deal
of trouble finding that transaction, since searching by payee obviously didn't
work, since the three payees were not mentioned in the transaction.  I only
found it by a text search.
I don't know what proper bookkeeping would require here, but I think the real
user need is just simplicity in data entry, and having a single split for the
bank deposit side, so it matches the bank statement.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 359470] Older Date

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359470

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
Today's date is not important.  You cannot enter a transaction with a date
prior to the opening date of the account.  If you edit the account, you can set
the opening date to a date prior to any transaction you want to enter for that
account.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 358936] Allow to not include on CC list for specific products

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358936

--- Comment #2 from Jack  ---
Filed at https://bugzilla.mozilla.org/show_bug.cgi?id=1245646

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 358936] New: Allow to not include on CC list for specific products

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358936

Bug ID: 358936
   Summary: Allow to not include on CC list for specific products
   Product: bugs.kde.org
   Version: unspecified
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: sysad...@kde.org
  Reporter: ostrof...@users.sourceforge.net
CC: she...@kde.org

Under User Preferences, there is an item "Automatically add me to the CC list
of bugs I change 
" where the choices are Always, Never, and Only if I have no role in them.  I
would also like to avoid adding me to the CC list of bugs for specified product
- specifically those where I subscribe to the product's devel mailing list, so
I already see all the bug related emails.  Now, I have to remember to uncheck
the add me to CC box.  I don't want to select "Never" because I would be likely
to forget to CHECK that box, and so lose track of those bugs.  

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 358935] New: Tools/Consistency Check should allow save or print, not just "OK"

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358935

Bug ID: 358935
   Summary: Tools/Consistency Check should allow save or print,
not just "OK"
   Product: kmymoney4
   Version: git master
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: ostrof...@users.sourceforge.net

Running a consistency check (either explcitly from the tools menu or when
saving the file) shows the results in a pop-up window, but the only choice is
"OK."  It would be useful if there were also "Print" and "Save as" buttons. 
Now, the only way to do this is to select the contents of the window, copy, and
save to a document.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 358935] Tools/Consistency Check should allow save or print, not just "OK"

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358935

--- Comment #1 from Jack  ---
OK - I didn't look hard enough.  Copy to clipboard and save as file are
available on the context menu (right clicking within the window).  However, I'm
not going to cancel the bug, since explicit buttons for those items would be
more obvious, and avoid bugs like this :-)  even if it does make it an even
lower priority.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 342401] allow splits on payees

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=342401

--- Comment #2 from Jack  ---
It looks like less than a quarter of the wishlist items are confirmed.  I don'
think this really has any particular meaning or importance - other than perhaps
a developer will confirm an item as an unofficial way of increasing the
priority.  As has been said on the mailing list, developer time is rather
scarce, and the current priority is conversion to Frameworks.  Once that is
complete (and there is no timeline yet) there may be more attention to fixing
remaining bugs, and then to addressing wishlist items.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 357724] qif import defaults to UTF-8, need an option to choose other charsets

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357724

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #4 from Jack  ---
Michel,

Since you just went through this, if you can propose a few sentences and where
in the manual they would be most effective, I'll be glad to actually include
them.

Jack

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 357290] unwanted transfer transaction created by ofx

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357290

--- Comment #6 from Jack  ---
The question is what kind of  account do you have it set up as in KMM?  
In the ofx log, can you find what date KMM is requesting as the start of
downloaded transactions?  That is the first key point.  If it is the date of
your last update, we move on to the second issue.  However, if it is 60 days
ago, even if  you have the account configured to download only since the
previous update, then you can try setting the start date each time  you
download.  That will avoid downloading the same transactions multiple times.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 357290] unwanted transfer transaction created by ofx

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357290

--- Comment #4 from Jack  ---
I don't know if there is any good solution to the issue of a transfer wanting
to have a different date on each end, since KMM does force a single date for
all splits of a transaction.  In paying paying my credit card from checking
account, I simply accept that one of the dates is actually off by a day or two.
 At some point, I'll probably file a wish-list bug to allow KMM to maintain two
dates for a transaction (or a split, I'm still not sure which will work better
if at all possible) - a transaction date and a posting date.  Which side shows
an earlier date depends whether the trasfer is a paper check (credit account
deposit first) or an electronic payment (check withdrawal first.)

In terms of  how  far back the update account goes - is this really a checking
account, or an investment account?  I have discovered that investment accounts
do not actually store the "last update" date, and so always go back 60 days
despite the configuration setting.  (I need to do more research before
submitting a bug and/or patch.)  You can check this by creating a file
"ofx.log" in your home directory.  The ofx update will then store the log of
the transaction in that file.  See  what date KMM is actually requesting as the
start date for download.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 357290] unwanted transfer transaction created by ofx

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357290

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
I think this is a question of how the institution creates the transaction, and
how KMM imports it, specifically whether it matches it to a previous transfer
transaction or just creates a new withdrawal/deposit transaction.  To either
institution (bank or credit card) it is just a withdrawal or deposit - it could
 only be a transfer it both accounts were in the same institution.  However,
when KMM imports such a transaction, it might recognize it based on the one
from the previous month, and so create it as a transfer.

As far as KMM recreating the deleted transaction the next time you update the
account - it is probably because the bank is sending it again - based on the
start date for transaction KMM is requesting.  Check whether KMM is requesting
updates since the last update, or since a specific date, or for the last N
days.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 302763] Ability to easily subscribe to a remote (or local) iCalendar file.

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=302763

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

-- 
You are receiving this mail because:
You are watching all bug changes.