Also watch out for multiple installations of Qt on the target PC, I think I spot at least 2:
one at ~/software/suis/new/DistributionKit
one at /opt/Qt

Try to remove one of them

@SGaist
I tried to learn how to apply a patch but it's complicated, I'm Brazilian and I can't find much about it in Portuguese.
About disabling sbom I tried adding the commands -DQT_GENERATE_SBOM=OFF and -no-sbom but it didn't change. I'm thinking about giving up and doing it the traditional way

They are converted that way because they contain no background. After PDF v1.4 the resulting pixel on a page is the composition of all overlaying graphic objects, each of which may carry an alpha component. If there is no explicit opaque object (e.g. a white rectangle) overlaying the entire page, under all the other objects, then there is no background where there are no overlying objects. It could be that the "working" images are PDF v1.3 or have an explicit background layer.

You could:

adjust the PDFs at source, or paint the resulting image over a filled canvas image to obtain an image guaranteed to have a background

I am having a similar issue too. In one of my views (mixed Qml and C++) I have a Node editor, where nodes can be added and connected. I used to handle the Keys.onPressed event and delete selected nodes and connection when Delete is pressed. This worked very well with Qt 6.6.1 in Webassembly (I use Linux). Now, when I switched to 6.8.1, Keys.onPressed event is never generated in Webassempbly (works well on desktop). My scene receives the active focus (I am logging onActiveFocusChanged) but not the keyboard events.

Hi and welcome to devnet,

Which version of Qt ?
On which OS ?
You should also connect the errorOccurred signal to ensure there's not something happening that you missed.

Hi,

You should provide more details:

version of Qt version of Windows version of Rocky 9 version of Vulkan copy of the stack trace

Component is a special type in the QtQml module that acts as a blueprint for creating objects in QML. Every QML object is implicitly part of a Component, even if you don't explicitly wrap it in a Component block. For example:

import QtQuick Item { Component.onCompleted: { console.log("Hello World") } }

Internally, QML treats this as if it is wrapped in a Component:

import QtQuick Component { Item { Component.onCompleted: { console.log("Hello World") } } }

You can analyze QQuickItem class and you will see that it inherits from QObject and QQmlParserStatus, hence it is possible to call Component.onCompleted() in Item objects.

Thank you!

I found a solution:

onClicked: { Object.keys(rectangle).forEach((key) => { if (rectangle.hasOwnProperty(key) && typeof rectangle[key] !== "function") { console.log(key + ": " + rectangle[key]) } }) }

@Pl45m4 older versions do support GCC 4, for example
https://wiki.qt.io/Qt_5.10_Tools_and_Versions
and
https://wiki.qt.io/Qt_5.7_Tools_and_Versions

I have 2 problems with the documentation.

It does not mention the buildroot toolchain It is not clear which is the last version that is ok to use GCC 4 (4.8)

... or check inside the delegate functions if the row is still the one e.g. by checking the data to display.

@fundamentalcupcake thanks for that. did you manage to get a crosscompile going by applying that patch? this is on my list of things.

@JonB I not tried if the read and write works while the errors appears...

I installed below libraries on device :
IMAGE_INSTALL:append = " libsocketcan can-utils"

and now is without any errors.