@Aron: No, it doesn't. But now I found out that it's not NM's fault but caused by a strict "1.2.0" version check in nmqt which is supposed to remove some API for 1.2, but ofc. didn't catch 1.1.93. I'm talking to upstream how to resolve that, but this bug can proceed fine.
@Aron: No, it doesn't. But now I found out that it's not NM's fault but caused by a strict "1.2.0" version check in nmqt which is supposed to remove some API for 1.2, but ofc. didn't catch 1.1.93. I'm talking to upstream how to resolve that, but this bug can proceed fine.