Hi Cecilio,
Is it on Linux?

Yes, Linux Mint 18.3

Hi Cecilio,

Can't reproduce yet.
Breaks - stops in Xojo IDE, right?
Is it 64- or 32-bit application? Any image fails?

It's a WebApp, (cgi).

When print, the browser closes the session because it has stopped. (broken)

If I delete the image of the report. No problem and it prints well and does not break.

It is a 64bit web application.

I have tried other images, all PNG, and with all fails.
JPG does not allow the report designer.

Hi Cecilio,

Still unable to reproduce.
Do you compile it on the same system? What if you switch to standalone and run from console - will you see the error message?

This is the error show in console:
Fontconfig error: Cannot load default config file
Violación de segmento
-----------------------------------

Hi Cecilio,

Thank you, so there is a real crash, but unfortunately, I'm unable to track it yet.
Did you try to debug in Xojo IDE on Linux? I understand you're compiling right on Linux, right? What is the last executed method?

I created a simple project with a report and a picture in it.
Could you please try to run it? Will it crash?

I enabled logging, so the log will be created in the vlogs folder near to the executable.

Hello
Yes, I compile on Linux directly. The last method is the one that prints.

Your example has also broken.

I copy you the log:
---------------------------------
Valentina_SetDebugLevel...
PARAM: inLevel = 3
return

VProject_Ctor_Local...
PARAM: instance = 140497708389904
PARAM: inFi = 140497708518664
return

VProject_Open...
PARAM: instance = 140497708389904
return

VProject_MakeNewReportByName...
PARAM: instance = 140497708389904
PARAM: inName = "Report_1"
PARAM: inDatabaseSource = "sqlite:///home/cecilio/Xojo/VReport_Picture_Test/Builds - VReport_Picture_Test.xojo_binary_project/Linux 64 bit/VReport_Picture_Test/reports_db.sqlite"
PARAM: inQuery = "SELECT * FROM T1"
return object = 140497708521968

VReport_PrintToBuffer...
PARAM: instance = 140497708521968
PARAM: inPrintType = 3
PARAM: inStartPageIndex = 1
PARAM: inEndPageIndex = 0

In your example:

report_2 and report_3 are printed perfect. No problem.

report_1 crash. (only when there are images)

More than a year ago, I made another app that had images and did not break.

crash y this point: dim data as string = report.PrintToBuffer(EVReportPrintType.kToPDF, 1 )

Hi Cecilio,

And which version of V4RB is installed?

Also, what is the version of Xojo?

In xojo I have the latest version 2017r3.

In V4RB I do not know. Is it updated with Valentina Studio?

Valentina Studio is updated frequently. Version Valentina Studio Pro 8.1

Thinking about it, I have not copied anything to the xojo plugins folder.

How should I update it?

No, V4RB is not updated automatically.

For example, you can check /usr/local/lib/vcomponents_64 folder.
It contains versioned shared libraries, like
libvkernel_release_x64.so.810 - it is the version 8.1.0

I have seen how to update V4RB.

I have updated it to 8.1.

Problem solved. !!! Now it's perfect.

I am very sorry for all the inconveniences. Excuse me.

Lesson learned.

Hi.!
I continue having problems.
When printing continues breaking with the message: "Violation of segment.".

I updated with "v4rb_x64_8_lin.deb" The first day was perfect.

I do not know if I should eliminate the previous installation. In usr / local / lib / vcomponent_64 there are old files.
I have renamed the folder and installed it again. But I'm still having problems.

Where does the v4rb_x64_release.so file take when compiling an app?

Is there an update guide in linux?

Hi Cecilio,

v4rb_x64_release.so is taken from ValentinaPlugin.xojo_plugin that you copied to the Plugins folder of Xojo.

So you can use ldd v4rb_x64_release.so to check if the correct versions of vkernel, vshared, etc, ... libraries are linked.

This is the result of v4rb_x64_release.so in the compiled folder (for 64bit app):
------------------------------------
ldd v4rb_x64_release.so
linux-vdso.so.1 => (0x00007fffab3b6000)
libvshared_release_x64.so.810 => /usr/local/lib/vcomponents/libvshared_release_x64.so.810 (0x00007f92a6b27000)
libvreport_release_x64.so.810 => /usr/local/lib/vcomponents/libvreport_release_x64.so.810 (0x00007f92a4ad1000)
libvclient_release_x64.so.810 => /usr/local/lib/vcomponents/libvclient_release_x64.so.810 (0x00007f92a43d9000)
libvkernel_release_x64.so.810 => /usr/local/lib/vcomponents/libvkernel_release_x64.so.810 (0x00007f92a2d2c000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f92a2980000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f92a2677000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f92a2461000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f92a2096000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f92a1e92000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f92a1c75000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f92a1a6c000)
libicui18n.so.54 => /usr/local/lib/vcomponents/libicui18n.so.54 (0x00007f92a1621000)
libicuuc.so.54 => /usr/local/lib/vcomponents/libicuuc.so.54 (0x00007f92a1278000)
/lib64/ld-linux-x86-64.so.2 (0x00005561a51e0000)
libicudata.so.54 => /usr/local/lib/vcomponents/libicudata.so.54 (0x00007f929f84e000)

-----------------------
Are the versions and libraries correct?

Yes, that's correct.
Did anything change after pictures started to work - maybe system restart?