Bug 396709

Summary: crash on startup on windows 7 x64
Product: [Applications] kmymoney Reporter: shizuma
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED WORKSFORME    
Severity: critical CC: ralf.habacker
Priority: NOR Keywords: triaged
Version: 4.8.2   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
See Also: https://bugs.kde.org/show_bug.cgi?id=396805
https://bugs.kde.org/show_bug.cgi?id=396797
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: kmymoney crashing
fx-rate kroken setup
Screenshot showing update price with from fx-rate with KMymoney 4.8.2
attachment showing retrieving BTC to CAD failing on Win 7 SP1
current visualc++ installed on fully patched Windows 7 RTM

Description shizuma 2018-07-20 20:17:28 UTC
Created attachment 114035 [details]
kmymoney crashing

kmymoney-x86_64-w64-mingw32-4.8.2-4.1-setup.exe install correctly, but kmymoney.exe doesn't start at all on plain windows 7 x64 AMD Athlon II.

ok on windows 7 sp1 though,  still AMD Athlon II
Comment 1 shizuma 2018-07-20 20:56:50 UTC
Complement of information 1:

Inatalled the 32 bits - kmymoney-i686-w64-mingw32-4.8.2-4.1-setup -  on x64 plain windows 7 machine and it works.  One has to find kmymoney.exe and make a shortcut otherwise it won't start, exiting silently.

Untested in Win 7 SP1.

Complement of information 2:

Fx-rate (Now renamed KmYMoney Currency default never made for me.  Not once, even with the patches applied.  Nor in 4.8.0, nor in 4.8.2.  Have to resort to alphavantage setup mentioned earlier in the yahoo finance thread by myself.

Another attachment showing setup ( the one that doesn't work).
Comment 2 shizuma 2018-07-20 20:58:07 UTC
Created attachment 114037 [details]
fx-rate kroken setup

produces errors on every entry to be checked.
Comment 3 shizuma 2018-07-20 23:12:05 UTC
complement of information 3:

Both versions of 4.8.2 are totally unfit for Win 7 64 bits original v 7600.

Experimented a lot and had to revert to faithful 4.8.0. using a ghost image 'dd if=/dev/sdb of=/dev/sda bs=1M'.

The damage was beyond repair. E,g, trying to save a file when you enter a price in a transaction, random crashes, etc.  Not trusting that installation a single bit, I reverted to the condition prior 4.8.2.

Recommendation:  avoid at all costs on Win 7.0 64 bits.  You've been warned.  Very weird things are going to happen and you won't like.  

If you don't have any backup image, you're screwed or are in for hours of back and forth seances of debugging for something that wasn't broken in the first place, exception of the yahoo rates, of which the replacement isn't an iota better.  That of course developers are willing to assist in debugging.

Haven't had a lot of success in the past.
Comment 4 Ralf Habacker 2018-07-21 16:51:20 UTC
Created attachment 114052 [details]
Screenshot showing update price with from fx-rate with KMymoney 4.8.2

I just updated prices with KMyMoney 4.8.2 on Windows 7 SP1 without any issues.
Comment 5 Ralf Habacker 2018-07-21 16:56:05 UTC
Just installed the 32bit and 64bit KMyMoney installer 4.8.2 on Windows 7 64 bit SP1 and did not found any mentioned issues. Start menu entries for running KMyMoney are present and the application workes out of the box.

I suggest to update your Windows 7 to SP1.
Comment 6 shizuma 2018-07-22 05:50:13 UTC
Created attachment 114064 [details]
attachment showing retrieving BTC to CAD failing on Win 7 SP1

Other also fail.  All of them.

Thanks for the suggestion to update to SP1 but I've been trying for years without success, particularly non stop this week, getting error after error.  Seems it won't happen.  Sorry.
Comment 7 Ralf Habacker 2018-07-23 09:04:03 UTC
(In reply to shizuma from comment #2)
> Created attachment 114037 [details]
> fx-rate kroken setup
> 
> produces errors on every entry to be checked.
Please file an additional bug report, because it is unrelated to this bug title - thanks.
Comment 8 Ralf Habacker 2018-07-23 10:10:35 UTC
(In reply to shizuma from comment #0)
complement of information 3:

> Both versions of 4.8.2 are totally unfit for Win 7 64 bits original v 7600
>The damage was beyond repair. E,g, trying to save a file when you enter a
> price in a >transaction, random crashes, etc. 
> Not trusting that installation a single bit, I reverted to the condition prior 4.8.2.

Just did a fresh Windows 7 64 bit virtual box machine (build 7600) setup and installed kmymoney 4.8.2 64 bit from setup installer on it and could not reproduce a crash on kmymoney start. Can you report the detailed steps you did to get the crash ?
Comment 9 Ralf Habacker 2018-07-23 17:53:05 UTC
(In reply to Ralf Habacker from comment #7)
> > produces errors on every entry to be checked.
> Please file an additional bug report, because it is unrelated to this bug
> title - thanks.

see 396797
Comment 10 shizuma 2018-07-24 16:46:14 UTC
(In reply to Ralf Habacker from comment #8)
> (In reply to shizuma from comment #0)
> complement of information 3:
> 
> > Both versions of 4.8.2 are totally unfit for Win 7 64 bits original v 7600
> >The damage was beyond repair. E,g, trying to save a file when you enter a
> > price in a >transaction, random crashes, etc. 
> > Not trusting that installation a single bit, I reverted to the condition prior 4.8.2.
> 
> Just did a fresh Windows 7 64 bit virtual box machine (build 7600) setup and
> installed kmymoney 4.8.2 64 bit from setup installer on it and could not
> reproduce a crash on kmymoney start. Can you report the detailed steps you
> did to get the crash ?

The problem is that I don't have a fresh win 7 installation, I have a fully patched one, up to but excluding SP1.

All I did is to click on the kmymoney link (x64 version) after installation and that C++ window popped out.  Installation seemed to went correctly, but no kmymoney icon present as opposite to SP1.  Might be related to multible Visual C++ versions around...  Here's the one I have installed (attached).

Is there is something else I can do to assist?
Comment 11 shizuma 2018-07-24 16:47:14 UTC
Created attachment 114098 [details]
current visualc++ installed on fully patched Windows 7 RTM
Comment 12 Ralf Habacker 2018-07-25 11:31:44 UTC
Comment on attachment 114098 [details]
current visualc++ installed on fully patched Windows 7 RTM

KMyMoney on Windows >= 4.8.1 does not use an msvc compiler and should therefore not depend on any of these redistributables.

I suggest to start kmymoney.exe through dependency walker (http://www.dependencywalker.com/), which may give some insides what goes wrong.
Choose the x86_64 variant for x86_64 kmymoney builds.

One issue may be pathes in the global PATH environment variables, pointing to different versions of shared libraries kmymoney.exe depends on. 

1. download dependency walker and unpack it somewhere
2. Open a command shell in bin dir of kmymoney installation
3. run <some-path>\depends.exe kmymoney.exe
4. selecct 'c:\' in the toolbar to see pathes 
5. Select menu entry "Profile" -> "Start Profiling" and let kmymoney.exe run

In the module windows you can see all loaded modules and from which path they were loaded. There should be only the kmymoney bin dir and pathes below the windows installation path e.g c:\Windows. If there are any pathes this may indicate a path issue I mentioned before.
Comment 13 Ralf Habacker 2018-07-25 11:33:04 UTC
>If there are any pathes

this should be: If there are any other pathes
Comment 14 Andrew Crouthamel 2018-09-28 03:18:51 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 15 Andrew Crouthamel 2018-10-29 02:21:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!