Bug 1225799

Summary: windows:mingw:win64/mingw64-kmymoney5: crashes on startup
Product: [openSUSE] openSUSE.org Reporter: Ralf Habacker <ralf.habacker>
Component: 3rd party softwareAssignee: Ralf Habacker <ralf.habacker>
Status: IN_PROGRESS --- QA Contact: E-mail List <screening-team-bugs>
Severity: Normal    
Priority: P5 - None CC: fridrich.strba, mkbosmans
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 1225808    
Bug Blocks:    
Attachments: log file

Description Ralf Habacker 2024-06-02 19:46:34 UTC
Running kmymoney5 from the binary package crashes - this has been reported at the KDE bug tracker.

How to reproduce:
1. Download the portable package from https://build.opensuse.org/projects/windows:mingw:win64/packages/mingw64-kmymoney5:mingw64-kmymoney5-installer/repositories/openSUSE_Leap_15.5/binaries
2. Unpack archive on Windows
3. In the root dir of the unpacked archive run start.bat or kmymoney.exe from the bin dir
4. follow new file wizard
5. save file

After saving the file kmymoney crashes.
Comment 1 Ralf Habacker 2024-06-02 23:22:01 UTC
Created attachment 875258 [details]
log file

The problem occurs in the openssl library during initialization by the qt webkit engine (see attached log file)
Comment 2 Ralf Habacker 2024-06-03 08:21:49 UTC
The included debug package for openssl does not have any debug source included (see bug 1225808), which makes it harder to find the reason for issue.
Comment 3 Ralf Habacker 2024-06-25 18:54:57 UTC
(In reply to Ralf Habacker from comment #2)
> The included debug package for openssl does not have any debug source
> included (see bug 1225808), which makes it harder to find the reason for
> issue.

On a build of kmymoney with a more recent Qt version (version 5.15.14 from https://build.opensuse.org/project/show/home:rhabacker:branches:windows:mingw:win64:Qt515) the problem no longer occurs, so this is a potential possibility after https://sourceware.org/bugzilla/show_bug.cgi?id=31929 has been fixed.