App released with windeployqt not showing UI

[SGaist]

Hi,

One thing that is strange is your qmldir option. It should be pointed to your application sources where you store your QML files so that their dependencies are all deployed.

It looks a bit unrelated since you have your application showing on some machines but still, it would be better to fix it.

[Fausto01]

@hskoglund Yes it has no dedicated graphic board.

[Fausto01]

@SGaist The batch file with the commands for releasing the app is at the same level of the qml directory, something like this:

└── Project/
    ├── release.bat
    ├── qml/
    │   └── main.qml
    └── src/
        └── main.cpp

[hskoglund]

I had same problem using QML on a Windows 10 portable PC with an integrated Intel graphics adapter. The solution that worked for me was to upgrade the graphics driver to the latest version from Intel. maybe it will help you also.

[Fausto01]

@hskoglund Seems that it's already the newest version (from Windows Update)

[hskoglund]

Windows Update didn't work for me, I had to go to the Intel website and fetch the driver there.

[kkoehne]

@Fausto01 said in App released with windeployqt not showing UI:

I've tried to set QT_DEBUG_PLUGINS=1 and run the application from terminal (even started as admin) but nothing has changed. I also checked the drivers and it is all updated. Any hint?

Windows GUI apps do not have a console by default, and therefore also do not write debug information to the console. Instead, it goes to the central 'debug buffer'. You can see the output of the buffer by a) launching your app in an IDE like Qt Creator, or b) run the standalone dbgview.exe.

(Caveat: Only one client should listen to the debug buffer at any given time on the whole machine.)

Try this, and setting QT_DEBUG_PLUGINS environment variable should really print you a lot of information.

[Fausto01]

Thank you guys, I'll try and give you an update asap

[Fausto01]

@kkoehne I've tried but nothing appears again. My application is compiled in release mode, do I have to build it in debug mode to see the output from dbgview?

[JonB]

@Fausto01
You should not need to compile for Debug in order to get the diagnostic output from setting environment variable QT_DEBUG_PLUGINS=1 when you run your application. Are you sure you did this correctly before launching your program, so many people seem to get this wrong?

[Fausto01]

@JonB this are the steps I've done:

1. Open dbgview.exe (should I do something else?)
2. Open a terminal in the installation folder of my application
3. On the terminal -> "set QT_DEBUG_PLUGINS=1"
4. On the terminal -> ./MyApp.exe
5. Check if dbgview.exe has printed something

Is it correct?

[JonB]

@Fausto01
Yes, those are the correct steps. I do not use Windows/dbgview so I do not know why you do bot see the diagnostics. I will leave it for @kkoehne to comment further.

[Fausto01]

Note: as i previously said, I've tried to create a file just after the creation of QApplication but the file was not created. Seems that the application is not starting, even if I see it running on the task manager

[Fausto01]

Ok I've tried to create a file before and after the creation of QApplication. The file before QApplication in created, the file after is not created because the app stucks in the creation of QApplication (after the creation I have a return 0 but the app is running on task manager). Any hint?

[J.Hilk]

@Fausto01 the obvious one, have you tried qt 5.15 ?
5.14 is no longer supported and may or may not have had bugs related to your issue :D

[Fausto01]

@J-Hilk No I don't, I will try and give you an update

[Fausto01]

@J-Hilk Seems that with Qt 5.15.2 the problem is solved... I don't know how much time I spent trying to solve. Thank you! I'll be back if I see some other issues :)