Bug 432071

Summary:	Print reconcile report is empty
Product:	[Applications] kmymoney	Reporter:	jesse <jvapr27>
Component:	reports	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	me
Priority:	NOR
Version:	5.1.1
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description jesse 2021-01-25 03:07:29 UTC

SUMMARY
After reconciling an account, I attempted to print the reconciliation report. However, the output PDF file is empty. 
I want to save the reconciliation report for my record keeping. The reports, however are empty. 

STEPS TO REPRODUCE
1. Open KMY file
2. Reconcile an account
3. Upon finishing, select to print the reconciliation report. 
4. The report printing will appear successful(No Errors). However, navigate using a file manager to the location where you saved the PDF. 
5. Open the PDF.. you will find that the PDF is empty. 


OBSERVED RESULT
Empty report. 

EXPECTED RESULT
PDF should have the same data as that presented in the reconciliation report

SOFTWARE/OS VERSIONS
Operating System: Generic 32
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.75.0
Qt Version: 5.14.2
Kernel Version: 5.10.8-100.fc32.x86_64
OS Type: 64-bit
KDE Frameworks 5.51.0
Qt 5.11.3 (built against 5.11.3)
The xcb windowing system

ADDITIONAL INFORMATION

Comment 1 Thomas Baumgart 2021-01-25 15:48:27 UTC

I duplicated this only in the AppImage version. The regular installed version works without problems.

Starting from the command line, I see the following when printing only when using the AppImage version:

  Failure to generate QImage from invalid or empty PDF document.

Comment 2 Dawid Wróbel 2021-01-25 16:36:53 UTC

Based on the previous issues of this nature, I suspect it is caused by the relative location of some resources. The upcoming changes to have the resources embedded with the code should hopefully fix this.

Comment 3 Thomas Baumgart 2021-02-01 15:28:05 UTC

I mark this as duplicate to the more general bug report.

*** This bug has been marked as a duplicate of bug 432380 ***