This seems to be a result of the filtering of the combo boxes for the kit aspects.

For example:

• register a remote linux device
• add a kit (defaults to a desktop kit)
• set the build device to "remote linux"

The compiler and the Qt version in the UI are both set to "None", and if you haven't registered any compiler/Qt for the device they are even disabled.

BUT, unexpectedly the compiler and Qt version are still considered to be the desktop compiler and desktop Qt, as can be observed via the kit's tool tip.

If you have a compiler registered for the remote linux device and set that as the compiler for the kit, the kit is marked as "broken" because the Qt version and the compiler don't match (even though the Qt version is "none" in the UI with no way to change it if you haven't also registered a Qt version for the device).