another appimage oddity (stock price fetching fails)

2019-10-11 Thread Jack Ostroff
I've been using the appimage version for the past few days, following  
the issues with importer plugins, and just discovered that it fails  
when fetching stock prices.  (empty quote data)  Re-installing 5.0.6,  
using the exact same data file, and all prices get fetched with no  
problem.  I'm pretty sure I'm currently using Financial Times for all  
my stock prices.


Just to check - the appimage is fetching from
http://funds.ft.com/uk/Tearsheet/Summary?s=PFE... but locally compiled  
5.0.6 is using
http://funds.ft.com/uk/Tearsheet/Summary?s=PFE... and I don't see any  
difference between them.
Lookoing at the online quotes config for Financial Times, they also  
appear to be identical.


Any thoughts?

Jack

Re: KMyMoney Compile..3rdparty directory

2019-10-11 Thread Thomas Baumgart
Hi guys,

On Freitag, 11. Oktober 2019 18:29:59 CEST Jack wrote:

> For background, some time ago, ALL data storage was moved to plugins,  
> where the basic XML (and KMY if compressed) storage was previously in  
> the main body of code.  The XML plugin should always be included.  This  
> missing -lxmlstoragehelper sounds familiar to me, but I can't find  
> anything relevant right now. There is no cmake parameter for this,  
> because the basic file storage (XML) is always enabled.
> 
> However, the "Waiting for unfinished jobs" suggests you are using -jN  
> where n>1 in your make command.  Try running with -j1 in case the issue  
> is that it is just trying to use a file before it is created.  Also,  
> check whether any xmlstoragehelper.* files exist, in case the problem  
> is looking in the wrong place for it, rather than it not having been  
> created yet.

I am running with -j13 (yes, thirteen) here and don't have a problem. It might 
be, that the xmlstoragehelper only gets compiled when the SQL backend is 
generated. An idea would be then to switch sqlstorage back on and see if it 
helps. If so, we need to fix the build system.

Thomas



> On 2019.10.11 10:06, jvap...@gmail.com wrote:
> > Okay, so I managed to get into ccmake and turn off the sqlcipher and
> > sqlstorage.
> > 
> > However, now when I compile, I get this error:
> > 
> > /usr/bin/ld: cannot find -lxmlstoragehelper
> > collect2: error: ld returned 1 exit status
> > make[2]: ***
> > [kmymoney/plugins/xml/tests/CMakeFiles/mymoneystoragenames-
> > test.dir/build.make:101: bin/mymoneystoragenames-test] Error 1
> > make[1]: *** [CMakeFiles/Makefile2:6801:
> > kmymoney/plugins/xml/tests/CMakeFiles/mymoneystoragenames-test.dir/all]
> > Error 2
> > make[1]: *** Waiting for unfinished jobs
> > [ 40%] Building CXX object
> > kmymoney/mymoney/storage/tests/CMakeFiles/mymoneystoragemgr-
> > test.dir/mymoneystoragemgr-test.cpp.o
> > /usr/bin/ld: cannot find -lxmlstoragehelper
> > collect2: error: ld returned 1 exit status
> > 
> > Has anyone seen this before? I looked in ccmake to see if there is a
> > config for lxmlstoragehelper I need to flip. I couldn't find one.
> > 
> > Any ideas?
> > 
> > thanks,
> > 
> > JV
> > 
> > 
> > On Thu, 2019-10-10 at 20:27 -0500, jvap...@gmail.com wrote:
> > > I guess the only question, is why does it not find it? Is it because
> > > I
> > > don't have something configured correctly?
> > >
> > > I don't currently keep it in a sql database, I just use whatever
> > > default KMM starts up with. This may seem trivial to you but to me  
> > it
> > > makes it difficult to understand if I have the product compiled and
> > > installed correctly. Also, leave me wondering why it cannot find the
> > > package even though it is installed on the system.
> > >
> > > Anyways, if it doesn't matter, that is fine. I just want to
> > > understand
> > > what is causing it not to find it.
> > >
> > > Will update soon. Thanks again!
> > >
> > > JV
> > >
> > >
> > >
> > > On Thu, 2019-10-10 at 18:44 -0400, Jack wrote:
> > > > On 2019.10.10 18:27, jvap...@gmail.com wrote:
> > > > > Thanks guys!
> > > > >
> > > > > But, why do I get this then?
> > > > >
> > > > > sqlcipher.x86_64 : SQLCipher is an open source extension to
> > > > > SQLite
> > > > > that
> > > > > provides transparent 256-bit AES encryption of database files.
> > > > > sqlcipher.i686 : SQLCipher is an open source extension to SQLite
> > > > > that
> > > > > provides transparent 256-bit AES encryption of database files.
> > > > > sqlcipher.x86_64 : SQLCipher is an open source extension to
> > > > > SQLite
> > > > > that
> > > > > provides transparent 256-bit AES encryption of database files.
> > > > > sqlcipher-devel.x86_64 : Development files for sqlcipher
> > > > > sqlcipher-devel.i686 : Development files for sqlcipher
> > > > > sqlcipher-devel.x86_64 : Development files for sqlcipher
> > > > >  
> > =
> > > > > ==
> > > > > 
> > > > >  Name
> > > > > Matched:
> > > > > sqlcipher
> > > > >  
> > =
> > > > > ==
> > > > > 
> > > > > 
> > > > > libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
> > > > > libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
> > > > I'm just guessing, but the above looks like output for some query
> > > > about
> > > > packages with sqlcipher in the name.  If so, it's just  
> > informative.
> > > >
> > > > > [kodemonkey@thinkpad build]$ sudo dnf install sqlcipher-
> > > > > devel.x86_64
> > > > > Last metadata expiration check: 0:20:52 ago on Thu 10 Oct 2019
> > > > > 05:05:01
> > > > > PM CDT.
> > > > > Package sqlcipher-devel-3.4.1-5.fc30.x86_64 is already  
> > installed.
> > > > > Dependencies resolved.
> > > > > Nothing to do.
> > > > > Complete!
> > > > > [kodemonkey@thinkpad 

[kmymoney] [Bug 412813] Changes in report not taken into account

2019-10-11 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=412813

--- Comment #6 from Thomas Baumgart  ---
Bonjour Patrick,

that one has been fixed in 5.0.2. See
https://bugs.kde.org/show_bug.cgi?id=392519

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

Re: KMyMoney Compile..3rdparty directory

2019-10-11 Thread Jack
For background, some time ago, ALL data storage was moved to plugins,  
where the basic XML (and KMY if compressed) storage was previously in  
the main body of code.  The XML plugin should always be included.  This  
missing -lxmlstoragehelper sounds familiar to me, but I can't find  
anything relevant right now. There is no cmake parameter for this,  
because the basic file storage (XML) is always enabled.


However, the "Waiting for unfinished jobs" suggests you are using -jN  
where n>1 in your make command.  Try running with -j1 in case the issue  
is that it is just trying to use a file before it is created.  Also,  
check whether any xmlstoragehelper.* files exist, in case the problem  
is looking in the wrong place for it, rather than it not having been  
created yet.


On 2019.10.11 10:06, jvap...@gmail.com wrote:

Okay, so I managed to get into ccmake and turn off the sqlcipher and
sqlstorage.

However, now when I compile, I get this error:

/usr/bin/ld: cannot find -lxmlstoragehelper
collect2: error: ld returned 1 exit status
make[2]: ***
[kmymoney/plugins/xml/tests/CMakeFiles/mymoneystoragenames-
test.dir/build.make:101: bin/mymoneystoragenames-test] Error 1
make[1]: *** [CMakeFiles/Makefile2:6801:
kmymoney/plugins/xml/tests/CMakeFiles/mymoneystoragenames-test.dir/all]
Error 2
make[1]: *** Waiting for unfinished jobs
[ 40%] Building CXX object
kmymoney/mymoney/storage/tests/CMakeFiles/mymoneystoragemgr-
test.dir/mymoneystoragemgr-test.cpp.o
/usr/bin/ld: cannot find -lxmlstoragehelper
collect2: error: ld returned 1 exit status

Has anyone seen this before? I looked in ccmake to see if there is a
config for lxmlstoragehelper I need to flip. I couldn't find one.

Any ideas?

thanks,

JV


On Thu, 2019-10-10 at 20:27 -0500, jvap...@gmail.com wrote:
> I guess the only question, is why does it not find it? Is it because
> I
> don't have something configured correctly?
>
> I don't currently keep it in a sql database, I just use whatever
> default KMM starts up with. This may seem trivial to you but to me  
it

> makes it difficult to understand if I have the product compiled and
> installed correctly. Also, leave me wondering why it cannot find the
> package even though it is installed on the system.
>
> Anyways, if it doesn't matter, that is fine. I just want to
> understand
> what is causing it not to find it.
>
> Will update soon. Thanks again!
>
> JV
>
>
>
> On Thu, 2019-10-10 at 18:44 -0400, Jack wrote:
> > On 2019.10.10 18:27, jvap...@gmail.com wrote:
> > > Thanks guys!
> > >
> > > But, why do I get this then?
> > >
> > > sqlcipher.x86_64 : SQLCipher is an open source extension to
> > > SQLite
> > > that
> > > provides transparent 256-bit AES encryption of database files.
> > > sqlcipher.i686 : SQLCipher is an open source extension to SQLite
> > > that
> > > provides transparent 256-bit AES encryption of database files.
> > > sqlcipher.x86_64 : SQLCipher is an open source extension to
> > > SQLite
> > > that
> > > provides transparent 256-bit AES encryption of database files.
> > > sqlcipher-devel.x86_64 : Development files for sqlcipher
> > > sqlcipher-devel.i686 : Development files for sqlcipher
> > > sqlcipher-devel.x86_64 : Development files for sqlcipher
> > >  
=

> > > ==
> > > 
> > >  Name
> > > Matched:
> > > sqlcipher
> > >  
=

> > > ==
> > > 
> > > 
> > > libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
> > > libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
> > I'm just guessing, but the above looks like output for some query
> > about
> > packages with sqlcipher in the name.  If so, it's just  
informative.

> >
> > > [kodemonkey@thinkpad build]$ sudo dnf install sqlcipher-
> > > devel.x86_64
> > > Last metadata expiration check: 0:20:52 ago on Thu 10 Oct 2019
> > > 05:05:01
> > > PM CDT.
> > > Package sqlcipher-devel-3.4.1-5.fc30.x86_64 is already  
installed.

> > > Dependencies resolved.
> > > Nothing to do.
> > > Complete!
> > > [kodemonkey@thinkpad build]$
> > >
> > >
> > > It seems it is already installed.
> > Yes, it looks that way.  What's the question here?  If you are
> > planning
> > on keeping your KMM data in a .xml or .kmy (gzipped xml) file,  
then

> > you
> > do not need any sql related packages.  It doesn't hurt anything if
> > they
> > are installed, but you don't need them.
> >
> > > It is driving me nuts! LOL
> > I know it can be confusing, but I'm not sure what your current
> > problem
> > or question is.  If you have already run cmake once, then run
> > "ccmake
> > ." in the build directory, so you can browse all the parameters,
> > and
> > turn off those you don't need.  Because of all those options, I
> > often
> > write a script to run cmake, with explicit values for all the
> > ENABLE_
> > 

Re: KMyMoney Compile..3rdparty directory

2019-10-11 Thread jvapr27
Okay, so I managed to get into ccmake and turn off the sqlcipher and
sqlstorage. 

However, now when I compile, I get this error: 

/usr/bin/ld: cannot find -lxmlstoragehelper
collect2: error: ld returned 1 exit status
make[2]: ***
[kmymoney/plugins/xml/tests/CMakeFiles/mymoneystoragenames-
test.dir/build.make:101: bin/mymoneystoragenames-test] Error 1
make[1]: *** [CMakeFiles/Makefile2:6801:
kmymoney/plugins/xml/tests/CMakeFiles/mymoneystoragenames-test.dir/all] 
Error 2
make[1]: *** Waiting for unfinished jobs
[ 40%] Building CXX object
kmymoney/mymoney/storage/tests/CMakeFiles/mymoneystoragemgr-
test.dir/mymoneystoragemgr-test.cpp.o
/usr/bin/ld: cannot find -lxmlstoragehelper
collect2: error: ld returned 1 exit status

Has anyone seen this before? I looked in ccmake to see if there is a
config for lxmlstoragehelper I need to flip. I couldn't find one. 

Any ideas? 

thanks, 

JV


On Thu, 2019-10-10 at 20:27 -0500, jvap...@gmail.com wrote:
> I guess the only question, is why does it not find it? Is it because
> I
> don't have something configured correctly? 
> 
> I don't currently keep it in a sql database, I just use whatever
> default KMM starts up with. This may seem trivial to you but to me it
> makes it difficult to understand if I have the product compiled and
> installed correctly. Also, leave me wondering why it cannot find the
> package even though it is installed on the system. 
> 
> Anyways, if it doesn't matter, that is fine. I just want to
> understand
> what is causing it not to find it. 
> 
> Will update soon. Thanks again!
> 
> JV
> 
> 
> 
> On Thu, 2019-10-10 at 18:44 -0400, Jack wrote:
> > On 2019.10.10 18:27, jvap...@gmail.com wrote:
> > > Thanks guys!
> > > 
> > > But, why do I get this then?
> > > 
> > > sqlcipher.x86_64 : SQLCipher is an open source extension to
> > > SQLite  
> > > that
> > > provides transparent 256-bit AES encryption of database files.
> > > sqlcipher.i686 : SQLCipher is an open source extension to SQLite
> > > that
> > > provides transparent 256-bit AES encryption of database files.
> > > sqlcipher.x86_64 : SQLCipher is an open source extension to
> > > SQLite  
> > > that
> > > provides transparent 256-bit AES encryption of database files.
> > > sqlcipher-devel.x86_64 : Development files for sqlcipher
> > > sqlcipher-devel.i686 : Development files for sqlcipher
> > > sqlcipher-devel.x86_64 : Development files for sqlcipher
> > > =
> > > ==
> > > 
> > >  Name
> > > Matched:
> > > sqlcipher
> > > =
> > > ==
> > > 
> > > 
> > > libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
> > > libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
> > I'm just guessing, but the above looks like output for some query
> > about  
> > packages with sqlcipher in the name.  If so, it's just informative.
> > 
> > > [kodemonkey@thinkpad build]$ sudo dnf install sqlcipher-
> > > devel.x86_64
> > > Last metadata expiration check: 0:20:52 ago on Thu 10 Oct 2019  
> > > 05:05:01
> > > PM CDT.
> > > Package sqlcipher-devel-3.4.1-5.fc30.x86_64 is already installed.
> > > Dependencies resolved.
> > > Nothing to do.
> > > Complete!
> > > [kodemonkey@thinkpad build]$
> > > 
> > > 
> > > It seems it is already installed.
> > Yes, it looks that way.  What's the question here?  If you are
> > planning  
> > on keeping your KMM data in a .xml or .kmy (gzipped xml) file, then
> > you  
> > do not need any sql related packages.  It doesn't hurt anything if
> > they  
> > are installed, but you don't need them.
> > 
> > > It is driving me nuts! LOL
> > I know it can be confusing, but I'm not sure what your current
> > problem  
> > or question is.  If you have already run cmake once, then run
> > "ccmake  
> > ." in the build directory, so you can browse all the parameters,
> > and  
> > turn off those you don't need.  Because of all those options, I
> > often  
> > write a script to run cmake, with explicit values for all the
> > ENABLE_  
> > options, just so I know what I'm requestiong, and don't rely on
> > default  
> > values.  It's perhaps a bit harder to set up, but it saves some
> > sanity  
> > in the long run.
> > 
> > > I will try the libofx method. Thanks!
> > > 
> > > JV
> > > 
> > > On Thu, 2019-10-10 at 19:29 +0200, Thomas Baumgart wrote:
> > > > On Donnerstag, 10. Oktober 2019 18:29:32 CEST Jack wrote:
> > > > 
> > > > > Hello JV,
> > > > > 
> > > > > On 2019.10.09 22:35, jvap...@gmail.com wrote:
> > > > > > Thanks Thomas and Jack.
> > > > > > 
> > > > > > I am a little confused/in shock now. :) It sounds like I do
> > > > > > not
> > > > need
> > > > > > to use AQBanking? I believe I need it since I use it to
> > > > > > allow
> > > > > > me
> > > > to
> > > > > > update my accounts (download) transactions. Are you saying
> > 

[kmymoney] [Bug 412484] No date ranges in report list

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=412484

--- Comment #4 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #3)
> If the KMyMoney file is opened in subsequent years, such
> customized reports are no longer available and must be redefined
> individually for the corresponding year
I think the problem is much worse unless it is intended that reports are
sliding. Without a pre-defined base date, reports with these range types are
usable only for the year, month, day in which they were created and in all
other time ranges worthless because they contain inaccurate values.

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

[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=412429

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In|4.8.5   |4.8.5,5.0.8

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

[kmymoney] [Bug 406338] No print preview available

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=406338

Ralf Habacker  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/kmy
   ||money/0dd809ab050c558a158a5
   ||37ee568e4b8c689fcb8
   Version Fixed In||4.8.5
 Resolution|--- |FIXED

--- Comment #5 from Ralf Habacker  ---
Git commit 0dd809ab050c558a158a537ee568e4b8c689fcb8 by Ralf Habacker.
Committed on 11/10/2019 at 10:38.
Pushed by habacker into branch '4.8'.

Add print preview for charts
FIXED-IN:4.8.5

M  +7-0kmymoney/kmymoney.cpp
M  +5-0kmymoney/kmymoney.h
M  +1-0kmymoney/kmymoneyui.rc
M  +27   -2kmymoney/views/khomeview.cpp
M  +10   -0kmymoney/views/khomeview.h
M  +8-0kmymoney/views/kmymoneyview.cpp
M  +5-0kmymoney/views/kmymoneyview.h
M  +15   -0kmymoney/views/kreportsview.cpp
M  +2-0kmymoney/views/kreportsview.h

https://commits.kde.org/kmymoney/0dd809ab050c558a158a537ee568e4b8c689fcb8

--- Comment #4 from Ralf Habacker  ---
Git commit 04af112832af9307c6a2c82bb83e8bf993a19433 by Ralf Habacker.
Committed on 11/10/2019 at 10:38.
Pushed by habacker into branch '4.8'.

Disable the print preview with an unpatched kdelibs to avoid problems with the
print settings

See https://bugs.kde.org/show_bug.cgi?id=412366#c12 for details
Related: bug 412366

M  +4-0kmymoney/kmymoney.cpp

https://commits.kde.org/kmymoney/04af112832af9307c6a2c82bb83e8bf993a19433

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

[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=412366

--- Comment #14 from Ralf Habacker  ---
Git commit 04af112832af9307c6a2c82bb83e8bf993a19433 by Ralf Habacker.
Committed on 11/10/2019 at 10:38.
Pushed by habacker into branch '4.8'.

Disable the print preview with an unpatched kdelibs to avoid problems with the
print settings

See https://bugs.kde.org/show_bug.cgi?id=412366#c12 for details
Related: bug 406338

M  +4-0kmymoney/kmymoney.cpp

https://commits.kde.org/kmymoney/04af112832af9307c6a2c82bb83e8bf993a19433

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

[kmymoney] [Bug 406338] No print preview available

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=406338

--- Comment #4 from Ralf Habacker  ---
Git commit 04af112832af9307c6a2c82bb83e8bf993a19433 by Ralf Habacker.
Committed on 11/10/2019 at 10:38.
Pushed by habacker into branch '4.8'.

Disable the print preview with an unpatched kdelibs to avoid problems with the
print settings

See https://bugs.kde.org/show_bug.cgi?id=412366#c12 for details
Related: bug 412366

M  +4-0kmymoney/kmymoney.cpp

https://commits.kde.org/kmymoney/04af112832af9307c6a2c82bb83e8bf993a19433

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

[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=412429

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In|5.0.8   |4.8.5
  Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy
   |money/65461d923923c4f0b163b |money/c47a6355e6583710cdd46
   |c790a63463dbcc8b5b7 |0ad7bb1b93b3d546961

--- Comment #14 from Ralf Habacker  ---
Git commit c47a6355e6583710cdd460ad7bb1b93b3d546961 by Ralf Habacker.
Committed on 11/10/2019 at 10:38.
Pushed by habacker into branch '4.8'.

Fix 'No display of transactions in the tags view when tags are specified in a
split'
FIXED-IN:4.8.5,5.0.8

(cherry-picked from commit 1285c644bdaa79f95ef22d55c808aa877c6aa861)

M  +9-1kmymoney/mymoney/mymoneytransactionfilter.cpp
M  +10   -0kmymoney/mymoney/mymoneytransactionfilter.h
M  +5-2kmymoney/mymoney/mymoneytransactionfiltertest.cpp
M  +1-0kmymoney/views/ktagsview.cpp

https://commits.kde.org/kmymoney/c47a6355e6583710cdd460ad7bb1b93b3d546961

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

[kmymoney] [Bug 412813] Changes in report not taken into account

2019-10-11 Thread Patrick
https://bugs.kde.org/show_bug.cgi?id=412813

--- Comment #5 from Patrick  ---
Bonjour Thomas,

Yes, it is a question for kubuntu, but I have noticed a strange behaviour :
- instead of closing the setup window with "fermer" button (it is a 
french version !) if I close with "Chercher" button, changes are taken 
into account, and all is ok.
I wonder if the label of "chercher" button is right ! It might be 
"appliquer" instead !

Regards
Patrick



Le 10/10/2019 à 21:03, Thomas Baumgart a écrit :
> https://bugs.kde.org/show_bug.cgi?id=412813
>
> --- Comment #4 from Thomas Baumgart  ---
> That is more of a question for kubuntu. The KMyMoney project provides the
> source tarballs for them and they need to pick it up.
>

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

[kmymoney] [Bug 406338] No print preview available

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=406338

--- Comment #3 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #2)
> See https://bugs.kde.org/show_bug.cgi?id=412366#c12 for issues with
> unpatched kdelibs for 4.8 builds

Windows versions use a patched kdelibs by default, which means that this
problem affects releases on Unix-like operating systems.

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

[kmymoney] [Bug 406338] No print preview available

2019-10-11 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=406338

--- Comment #2 from Ralf Habacker  ---
See https://bugs.kde.org/show_bug.cgi?id=412366#c12 for issues with unpatched
kdelibs for 4.8 builds

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