#299 QM asserts on opening project

[Baltazar]

Started happening after this issue & solution: https://sourceforge.net/p/qpc/discussion/668726/thread/697acac794/

QM launches successfully. Opening any existing project or creating a new one produces the assert shown in attachment.

Terminal output at assert:

Assertion failed in module model, line 446

[Quantum Leaps]

You seem to be using much newer Qt libraries (apparently Qt 5.11) than the Qt version to build QM.

Perhaps you could try to use the Qt version that was used to build QM in the first place. That Qt version is listed by means of the "Help | About Qt" menu, and is Qt 5.6.2 in case of the Linux version. These Qt libraries are distributed with the QM.

--MMS

[Baltazar]

Hi and thanks for quick response.

Yes,

qmake --version

returns

QMake version 3.1
Using Qt version 5.11.1 in /opt/qt511/lib

on my system, if this is the right way to check it. However, "Help | About Qt" in QM reports the same version - see attachment (I am supposing here that this shows the version that QM expects and not the one that it finds at runtime - correct me if I am wrong).

I am using QM from qp-linux_6.9.3.zip package.

I also tried to change the qtchooser configuration to point to Qt 4.8.7 and then to Qt 5.5.1 that were also found on my system but I always get the assert.

When you say These Qt libraries are distributed with the QM - how could I point QM to use its own Qt libraries?

[Quantum Leaps]

Of course, if you run QM against the Qt 5.11 libraries, the "About Qt" dialog box will show you Qt 5.11.

But, QM ships with the correct Qt libraries in the bin folder. This is the same folder where you found the QM executable. Actually, I don't understand how you could miss it:

bin
│   libicudata.so.56
│   libicui18n.so.56
│   libicuuc.so.56
│   libQt5Core.so.5
│   libQt5DBus.so.5
│   libQt5Gui.so.5
│   libQt5PrintSupport.so.5
│   libQt5Svg.so.5
│   libQt5Widgets.so.5
│   libQt5XcbQpa.so.5
│   qm
│   qm.sh
│   qmc
│   qmc.sh
│
└───platforms
        libqxcb.so

--MMS

[Baltazar]

1. I didn't miss the Qt libraries in the bin folder. But my question was: how to make QM use these particular libraries instead of some other that are present on my system.
2. I think I found the root cause of my problem: this issue and then the assert appeared after I interchanged the HDMI cables of my two monitors. Apparently, Qt had trouble showing the QM window on the "other" monitor (physically the same but via the other cable) - it can still run only on one of them, crashing on another. I suppose this is a Qt problem. QM is a wonderful piece of SW!

[Quantum Leaps]

This issue is closed as a hardware problem on the particular host machine. There is nothing to fix in the QM software for this.