Registered Member
|
As you can see follow, all binaryes use Qt5 libraries. But, when I run it with gdb, something call /usr/lib/x86_64-linux-gnu/libQtGui.so.4
ldd /home/user/build-untitledM1-Desktop-Debug/untitledM1 | grep marble
readelf -d /usr/local/lib/libmarblewidget.so
readelf -d /usr/local/lib/libastro.so
gdb output
readelf -d /home/user/build-untitledM1-Desktop-Debug/untitledM1
|
Registered Member
|
There is backtrace
|
Registered Member
|
Hi,
I can't really tell what's happening. Seems like you got this "almost" running at least. Marble produces a lot of "QIODevice::write: device not open" spam in my app too. Don't know where libQtGui v 4 is linked, you have to find this - good luck! |
Registered Member
|
Ok, Adam, thank you for help.
May be somebody else can give me some advice? |
Administrator
|
Given the crash is in QtGui, I strongly suspect it is trying to load the Oxygen style plugin. Are you able to find out what other libraries are loaded to verify this?
Another way of seeing if this is the case is to pass the argument "-style plastique" to the example Marble application, which should force it to not use the Oxygen style.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
'marble-qt' application run successfull. I can not to build examples for marble from git sources (it can not find headers). Can I someway pass this argument for widget in my app?
I am trying to find causer of QtGui call now. |
Administrator
|
I'm afraid not - if your application is already loaded successfully, and is written in Qt 5 though, it shouldn't be attempting to load Qt 4. The style argument I mentioned is something passed at the start of an application, and always affects the whole application.
Could you try getting a full backtrace? This may help us in finding out why it is trying to load a Qt 4 plugin.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
May it be relevant?
readelf -d /usr/local/lib/marble/plugins/libAnnotatePlugin.so
|
Registered Member
|
May be I do not understand some, but I think, that is all backtrace. There is full gdb session:
|
Administrator
|
It could be relevant. Where are you installing the Marble which you have self-compiled?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
It located in /usr/local
I used
as Adam sayed. |
Administrator
|
Okay, that is the cause of the problem then.
Either the Marble you're building is contaminated with both Qt 4 and Qt 5 elements, or you have an existing Qt 4 installation of Marble which is being mixed with the Qt 5 Marble. This is not a supported configuration in either case.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I have not installed marble except self build.
And it runs ok. What in my actions could result in the mixing Qt4 and Qt5? I do not understand, why marble-qt work, and app with marble widged do not.
|
Administrator
|
Which build process installed /usr/local/lib/marble/plugins/libAnnotatePlugin.so?
You can check the file install_manifest.txt in your Marble build directory to see if it installed it. If it didn't, then this is an installation remnant from something in the past - which needs to be removed.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
/home/user/marble/build/install_manifest.txt contains string
|
Registered users: Bing [Bot], daret, Google [Bot], Sogou [Bot]