'Client vertex and index arrays - all vertex array attribute and element array index pointers must refer to buffer objects. The default vertex array object (the name zero) is also deprecated. Calling VertexAttribPointer when no buffer object or no vertex array object is bound will generate an INVALID_- OPERATION error, as will calling any array drawing command when no vertex array object is bound.' source: https://www.khronos.org/registry/OpenGL/specs/gl/glspec33.core.pdf page 344

Hi, You are not giving crucial informations: What version of Qt are you using ? Which one gave you the warning ? Which not ? Are you using a custom build of Qt ? What OS are you on ? Version of the nVidia driver ?

@Stefan-Monov76 Good to hear that it works! :-) Regarding your question: I don't know, sry.

Hi and welcome to devnet, Like you already found, the QtWayland module is likely what you are looking for. If you would like to discuss things about it, one recommended channel is the #qt-labs IRC channel. You can also bring your questions on the interest mailing list You'll find there Qt's developers/maintainers. This forum is more user oriented.

@Chris-Kawa Fair enough. Thanks for taking the time. Cheers!

The libpng warning comes from libpng, nothing Qt can do about it. The QML engine crash is unrelated to libpng warning. Can you reproduce this crash with a simple app ? What do you mean by portable devices ? QML applications run on the RPi, BeagleBoneBlack, i.MX boards or iOS and android based phone.

I did register but realized I posted with the wrong email address. Now I've corrected it and can see my post on the list. Thank you.

Hi and welcome to devnet, Why not use a script to start your application ? By the way, shouldn't it rather be launched by your init manager (systemd, init, etc.) ? In any case, qputenv could be used to set the environment variables and you would have to modify by hand argc and argv before passing them to your QApplication instance.

Hi and welcome to devnet, Since you are using an unreleased version of Qt and hitting something that's probably influenced by the internals of Qt. I'd recommend posting your question on the interest mailing list You'll find there Qt's developers/maintainers (this forum is more user oriented)

He should have tried to submit it to code review

Looks like a bug, you should check on the bug report system

@SGaist Thank you for reply. As you said, we shall optimize Qt and DFB. Thank you.