FS#74457 - [qtcreator] Launching processes breaks with Qt 6.3.0
Attached to Project:
Arch Linux
Opened by Aaron Barany (akb825) - Wednesday, 13 April 2022, 01:57 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 19 April 2022, 06:30 GMT
Opened by Aaron Barany (akb825) - Wednesday, 13 April 2022, 01:57 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 19 April 2022, 06:30 GMT
|
Details
Description:
After upgrading to Qt 6.3.0, launching applications through Qt Creator causes it to get in a broken state where it effectively cannot be used until you quit and reload. This can be partially worked around by running applications through the debugger. Additional info: * qtcreator version 7.0.0-1 * qt6 packages version 6.3.0-1 Steps to reproduce: 1. Load a project. I used a CMake project in my case. 2. Run an application through the Build -> Run menu or shortcut. 3. Observe that in the output window, the following error is printed: "Failed to start program. Path or permissions wrong?" After this point, the IDE is largely broken. Many operations hang for several seconds, and anything that involves interacting with a separate process is broken. For example, the C++ code model is broken (no symantic highlighting or code completion), all builds fail, running programs through the IDE fail, etc. This state persists until the IDE is quit and re-launched. Downgrading the qt6 packages to 6.2.4-1 resolve the issue. |
This task depends upon
Closed by Antonio Rojas (arojas)
Tuesday, 19 April 2022, 06:30 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#74505
Tuesday, 19 April 2022, 06:30 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Aaron Barany (akb825) -
Wednesday, 13 April 2022, 23:34 GMT
Comment by Aaron Barany (akb825) -
Tuesday, 19 April 2022, 04:42 GMT
I was hoping this was just a case where the package needed to be
rebuilt, but I can confirm that is not the case. I did some
debugging and it appears the socket for the clangbackend process
is getting disconnected. I created an upstream bug report here:
https://bugreports.qt.io/browse/QTCREATORBUG-27385
After more investigation, this was caused by a regression in the
QProcess class in qt6-base. I have submitted a separate bug report
against qt6-base to capture this
(https://bugs.archlinux.org/task/74505) and attached a patch that
fixes the regression. I have verified that it resolves the issue
when applying the patch locally.