QtCreator startup time is really long
-
Hello:
We have installed QtCreator 10.0 in a RHEL 8.6. The install was succesful, and we are able to execute qtcreator. The problem is that it takes like 5 minutes to start up.
We think that the root cause can be found in the following logs:
Cannot update Qt version information from /opt/Qt/5.15.13/gcc_64/bin/qmake: Timeout running "/opt/Qt/5.15.13/gcc_64/bin/qmake".. Cannot update Qt version information from /opt/Qt/5.15.13/wasm_32/bin/qmake: Timeout running "/opt/Qt/5.15.13/wasm_32/bin/qmake".. Cannot update Qt version information from /opt/Qt/5.15.13/android/bin/qmake: Timeout running "/opt/Qt/5.15.13/android/bin/qmake".. qtc.cmake.tool: Fetching capabilities failed: "" QProcess::UnknownErrorOnce those logs are shown, the QtCreator window appears, and it can be used correctly.
The first thing we checked was if the 3 qmake paths mentioned in the logs existed, and they do. We can execute them correctly from any user (it's not a permission problem).
We would really appreciate if someone could help us.
Regards,
Samuel. -
Hello:
We have installed QtCreator 10.0 in a RHEL 8.6. The install was succesful, and we are able to execute qtcreator. The problem is that it takes like 5 minutes to start up.
We think that the root cause can be found in the following logs:
Cannot update Qt version information from /opt/Qt/5.15.13/gcc_64/bin/qmake: Timeout running "/opt/Qt/5.15.13/gcc_64/bin/qmake".. Cannot update Qt version information from /opt/Qt/5.15.13/wasm_32/bin/qmake: Timeout running "/opt/Qt/5.15.13/wasm_32/bin/qmake".. Cannot update Qt version information from /opt/Qt/5.15.13/android/bin/qmake: Timeout running "/opt/Qt/5.15.13/android/bin/qmake".. qtc.cmake.tool: Fetching capabilities failed: "" QProcess::UnknownErrorOnce those logs are shown, the QtCreator window appears, and it can be used correctly.
The first thing we checked was if the 3 qmake paths mentioned in the logs existed, and they do. We can execute them correctly from any user (it's not a permission problem).
We would really appreciate if someone could help us.
Regards,
Samuel.Apparently there is a bug in the RHEL kernel see this forum entry.
