I cannot get Qt Creator / Designer to work for the life of me
-
M
Mlibu
less than a minute agoHi there. I have had a frustrating last couple of weeks. I am having Qt Creator 12.0.2 fail on me around five minutes after startup; possibly(?) more often when interacting with the properties pain. Qt Creator just crashes and disappears on me in both Manjaro Linux and Windows. Yes I uninstalled all Manjaro linux packages before installing all Qt and tools with the online installer through both default installs of "Qt Desktop" and "Qt Designer" and also custom installs omitting all but the core Qt and QtQuick packages. I created a defaiult QtQuick project, I activated the Qt Quick plugin, and after I use Designer (which seems to work fine) it quickly stops.
Has anyone else heard of this? The QtCreator 13 beta does the same thing. I'm about to try the LTS. Then maybe I'll have to go back to 11? I did see one recommendation to try an offline install of qtcreator in response to it not working on Arch Linux but it did the same thing for me on windows?
I am using Qt6 / QtQuick. Thank you.
-
M
Mlibu
less than a minute agoHi there. I have had a frustrating last couple of weeks. I am having Qt Creator 12.0.2 fail on me around five minutes after startup; possibly(?) more often when interacting with the properties pain. Qt Creator just crashes and disappears on me in both Manjaro Linux and Windows. Yes I uninstalled all Manjaro linux packages before installing all Qt and tools with the online installer through both default installs of "Qt Desktop" and "Qt Designer" and also custom installs omitting all but the core Qt and QtQuick packages. I created a defaiult QtQuick project, I activated the Qt Quick plugin, and after I use Designer (which seems to work fine) it quickly stops.
Has anyone else heard of this? The QtCreator 13 beta does the same thing. I'm about to try the LTS. Then maybe I'll have to go back to 11? I did see one recommendation to try an offline install of qtcreator in response to it not working on Arch Linux but it did the same thing for me on windows?
I am using Qt6 / QtQuick. Thank you.
@Mlibu said in I cannot get Qt Creator / Designer to work for the life of me:
Has anyone else heard of this?
No such issue on my side (Kubuntu Linux, QtC 12.0.2).
-
M
Mlibu
less than a minute agoHi there. I have had a frustrating last couple of weeks. I am having Qt Creator 12.0.2 fail on me around five minutes after startup; possibly(?) more often when interacting with the properties pain. Qt Creator just crashes and disappears on me in both Manjaro Linux and Windows. Yes I uninstalled all Manjaro linux packages before installing all Qt and tools with the online installer through both default installs of "Qt Desktop" and "Qt Designer" and also custom installs omitting all but the core Qt and QtQuick packages. I created a defaiult QtQuick project, I activated the Qt Quick plugin, and after I use Designer (which seems to work fine) it quickly stops.
Has anyone else heard of this? The QtCreator 13 beta does the same thing. I'm about to try the LTS. Then maybe I'll have to go back to 11? I did see one recommendation to try an offline install of qtcreator in response to it not working on Arch Linux but it did the same thing for me on windows?
I am using Qt6 / QtQuick. Thank you.
-
@Tink What could be wrong with all my hardware then? If it works in Manjaro then why isn't it working for me?
Min requirements for Qt Creator:
256 MB of RAM 500 MHz CPU, 1 GHz preferred for 60-FPS velvet-smooth UI OpenGL ES 2.0 support *You need a GPU for this? I only have thinkpads and they don't have GPUs. I have a Macbook Pro with a GPU but I don't want to do all the XCode stuff. It's always a pain because XCode updates all the time and then you need to do it all over again. I have already run Android Studio on them..
-
@Tink What could be wrong with all my hardware then? If it works in Manjaro then why isn't it working for me?
Min requirements for Qt Creator:
256 MB of RAM 500 MHz CPU, 1 GHz preferred for 60-FPS velvet-smooth UI OpenGL ES 2.0 support *You need a GPU for this? I only have thinkpads and they don't have GPUs. I have a Macbook Pro with a GPU but I don't want to do all the XCode stuff. It's always a pain because XCode updates all the time and then you need to do it all over again. I have already run Android Studio on them..
@Mlibu
It's more likely to be something about your environment, installed software, something you do or even the code you are working on than hardware.If you get nowhere else, and you say Creator crashes, it might be worth running Creator under
gdbfrom a command line. If you are lucky you will get a stack trace if it crashes, and there just might be a clue there. If you are not lucky, it won't actually "crash", won't have a stack trace or won't have anything useful in the trace. But worth a try.... -
C Christian Ehrlicher moved this topic from General and Desktop on
-
@Mlibu
It's more likely to be something about your environment, installed software, something you do or even the code you are working on than hardware.If you get nowhere else, and you say Creator crashes, it might be worth running Creator under
gdbfrom a command line. If you are lucky you will get a stack trace if it crashes, and there just might be a clue there. If you are not lucky, it won't actually "crash", won't have a stack trace or won't have anything useful in the trace. But worth a try....I'm not working on any code. I create a new project and it breaks before I can configure a single rectangle in designer.
At first I tried an ASUS flipbook with 4Gb RAM and Windows 10 but it didn't work. I thought it was the RAM so I bought a Lenovo M73 Mini. It has a stock Manjaro/KDE/X11 install with only Kodi installed and rendering effects activated. KDE itself seems to be working very smoothly with transparency, wobbly windows, etc.
-
I'm not working on any code. I create a new project and it breaks before I can configure a single rectangle in designer.
At first I tried an ASUS flipbook with 4Gb RAM and Windows 10 but it didn't work. I thought it was the RAM so I bought a Lenovo M73 Mini. It has a stock Manjaro/KDE/X11 install with only Kodi installed and rendering effects activated. KDE itself seems to be working very smoothly with transparency, wobbly windows, etc.
-
@Mlibu That does not address running it (Creator executable) under
gdbin case you get a clue from the crash stack trace....@JonB So does that mean that the lack of a GPU is not the problem?
I ran under gdb and after the threads start up I get "Found an unknown QML value." followed by "Trying to construct an instance of an invalid type, type id: -1".
Then there is a line "Detaching after vfork from child process 11111". After that line there is a bunch of:
qtc.imagecontainer.debug: void QmlDesigner::readSharedMemory(qint32, QmlDesigner::ImageContainer&) Not able to create image: 0 0 0.
Then more of the first error, then more of the second, then Thread 1 'qtcreator' received signal SIGSEGV, Segmentation fault.
And that's it. Any ideas?
-
@JonB So does that mean that the lack of a GPU is not the problem?
I ran under gdb and after the threads start up I get "Found an unknown QML value." followed by "Trying to construct an instance of an invalid type, type id: -1".
Then there is a line "Detaching after vfork from child process 11111". After that line there is a bunch of:
qtc.imagecontainer.debug: void QmlDesigner::readSharedMemory(qint32, QmlDesigner::ImageContainer&) Not able to create image: 0 0 0.
Then more of the first error, then more of the second, then Thread 1 'qtcreator' received signal SIGSEGV, Segmentation fault.
And that's it. Any ideas?
-
@JonB So does that mean that the lack of a GPU is not the problem?
I ran under gdb and after the threads start up I get "Found an unknown QML value." followed by "Trying to construct an instance of an invalid type, type id: -1".
Then there is a line "Detaching after vfork from child process 11111". After that line there is a bunch of:
qtc.imagecontainer.debug: void QmlDesigner::readSharedMemory(qint32, QmlDesigner::ImageContainer&) Not able to create image: 0 0 0.
Then more of the first error, then more of the second, then Thread 1 'qtcreator' received signal SIGSEGV, Segmentation fault.
And that's it. Any ideas?
@Mlibu said in I cannot get Qt Creator / Designer to work for the life of me:
then Thread 1 'qtcreator' received signal SIGSEGV, Segmentation fault.
So you are supposed to (at least try to) view the stack trace.
btis the gdb command. See if there is any clue there. -
@Mlibu said in I cannot get Qt Creator / Designer to work for the life of me:
then Thread 1 'qtcreator' received signal SIGSEGV, Segmentation fault.
So you are supposed to (at least try to) view the stack trace.
btis the gdb command. See if there is any clue there.@JonB
Yes I did. I thought you meant stack trace and bt was what I did. I closed it by accident without saving the trace and I have been trying to do it again.However, I have been having other strange things happen when I install QtCreator. There is an 'impoort <projectname>' in the Screen01.ui.qml with a line error: QML Module contains C++ plugin, currently reading type information. I cannot build with that there and have to remove it before I can build. Also when I first go to the designer page the UI does not get drawn properly and it seems hung somehow. There is only a checkered item in the screen even though I had created the new Qt project. Then later the proper UI seems to come back. But then it only lasts for a couple minutes and dies. And I delete the project directories before I try again. I tried CMake, build, clean project, etc etc.
I only found this comment on SO which doesn't give very many details on how to resolve it, unfortunately. It just talks about resetting the code model and explicitly importing the qrc path.
This time Qt Creator just froze in the designer screen instead if crashing. Also I noticed that KDE Plasma 5 requires qtdesigner from qt5-tools. Could this be confusing anything?
Here is the top of my stack:
#0 0x00007ffff52daed0 in QV4::Compiler::Codegen::visit(QQmlJS::AST::UiProgram*) () from /home/user/Qt/Tools/QtCreator/bin/../lib/qtcreator/../Qt/lib/libQt6Qml.so.6
#1 0x000000000ca811a0 in ?? ()
#2 0x00007fffa3b45538 in ?? ()
#3 0x00007fffffffbec0 in ?? ()
#4 0x00007fffa808d6c0 in ?? ()
#5 0x00007ffff56132a9 in QV4::QQmlTypeWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) ()Maybe when I install my next system I'll hold my nose and install Manjaro Gnome and see if that works.
-
@JonB
Yes I did. I thought you meant stack trace and bt was what I did. I closed it by accident without saving the trace and I have been trying to do it again.However, I have been having other strange things happen when I install QtCreator. There is an 'impoort <projectname>' in the Screen01.ui.qml with a line error: QML Module contains C++ plugin, currently reading type information. I cannot build with that there and have to remove it before I can build. Also when I first go to the designer page the UI does not get drawn properly and it seems hung somehow. There is only a checkered item in the screen even though I had created the new Qt project. Then later the proper UI seems to come back. But then it only lasts for a couple minutes and dies. And I delete the project directories before I try again. I tried CMake, build, clean project, etc etc.
I only found this comment on SO which doesn't give very many details on how to resolve it, unfortunately. It just talks about resetting the code model and explicitly importing the qrc path.
This time Qt Creator just froze in the designer screen instead if crashing. Also I noticed that KDE Plasma 5 requires qtdesigner from qt5-tools. Could this be confusing anything?
Here is the top of my stack:
#0 0x00007ffff52daed0 in QV4::Compiler::Codegen::visit(QQmlJS::AST::UiProgram*) () from /home/user/Qt/Tools/QtCreator/bin/../lib/qtcreator/../Qt/lib/libQt6Qml.so.6
#1 0x000000000ca811a0 in ?? ()
#2 0x00007fffa3b45538 in ?? ()
#3 0x00007fffffffbec0 in ?? ()
#4 0x00007fffa808d6c0 in ?? ()
#5 0x00007ffff56132a9 in QV4::QQmlTypeWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) ()Maybe when I install my next system I'll hold my nose and install Manjaro Gnome and see if that works.
-
@JonB
Yes I did. I thought you meant stack trace and bt was what I did. I closed it by accident without saving the trace and I have been trying to do it again.However, I have been having other strange things happen when I install QtCreator. There is an 'impoort <projectname>' in the Screen01.ui.qml with a line error: QML Module contains C++ plugin, currently reading type information. I cannot build with that there and have to remove it before I can build. Also when I first go to the designer page the UI does not get drawn properly and it seems hung somehow. There is only a checkered item in the screen even though I had created the new Qt project. Then later the proper UI seems to come back. But then it only lasts for a couple minutes and dies. And I delete the project directories before I try again. I tried CMake, build, clean project, etc etc.
I only found this comment on SO which doesn't give very many details on how to resolve it, unfortunately. It just talks about resetting the code model and explicitly importing the qrc path.
This time Qt Creator just froze in the designer screen instead if crashing. Also I noticed that KDE Plasma 5 requires qtdesigner from qt5-tools. Could this be confusing anything?
Here is the top of my stack:
#0 0x00007ffff52daed0 in QV4::Compiler::Codegen::visit(QQmlJS::AST::UiProgram*) () from /home/user/Qt/Tools/QtCreator/bin/../lib/qtcreator/../Qt/lib/libQt6Qml.so.6
#1 0x000000000ca811a0 in ?? ()
#2 0x00007fffa3b45538 in ?? ()
#3 0x00007fffffffbec0 in ?? ()
#4 0x00007fffa808d6c0 in ?? ()
#5 0x00007ffff56132a9 in QV4::QQmlTypeWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) ()Maybe when I install my next system I'll hold my nose and install Manjaro Gnome and see if that works.
-
@JonB
Yes I did. I thought you meant stack trace and bt was what I did. I closed it by accident without saving the trace and I have been trying to do it again.However, I have been having other strange things happen when I install QtCreator. There is an 'impoort <projectname>' in the Screen01.ui.qml with a line error: QML Module contains C++ plugin, currently reading type information. I cannot build with that there and have to remove it before I can build. Also when I first go to the designer page the UI does not get drawn properly and it seems hung somehow. There is only a checkered item in the screen even though I had created the new Qt project. Then later the proper UI seems to come back. But then it only lasts for a couple minutes and dies. And I delete the project directories before I try again. I tried CMake, build, clean project, etc etc.
I only found this comment on SO which doesn't give very many details on how to resolve it, unfortunately. It just talks about resetting the code model and explicitly importing the qrc path.
This time Qt Creator just froze in the designer screen instead if crashing. Also I noticed that KDE Plasma 5 requires qtdesigner from qt5-tools. Could this be confusing anything?
Here is the top of my stack:
#0 0x00007ffff52daed0 in QV4::Compiler::Codegen::visit(QQmlJS::AST::UiProgram*) () from /home/user/Qt/Tools/QtCreator/bin/../lib/qtcreator/../Qt/lib/libQt6Qml.so.6
#1 0x000000000ca811a0 in ?? ()
#2 0x00007fffa3b45538 in ?? ()
#3 0x00007fffffffbec0 in ?? ()
#4 0x00007fffa808d6c0 in ?? ()
#5 0x00007ffff56132a9 in QV4::QQmlTypeWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) ()Maybe when I install my next system I'll hold my nose and install Manjaro Gnome and see if that works.
Hi @Mlibu,
IIRC, the QML stuff needs 3D accelleration. Could you try to start Creator without these plugins to see if that makes a difference?
/opt/Qt/Tools/QtCreator/bin/qtcreator -noload QmlDesignerBase -noload QmlJSEditor -noload QmlJSToolsRegards
-
Hi @Mlibu,
IIRC, the QML stuff needs 3D accelleration. Could you try to start Creator without these plugins to see if that makes a difference?
/opt/Qt/Tools/QtCreator/bin/qtcreator -noload QmlDesignerBase -noload QmlJSEditor -noload QmlJSToolsRegards
-
@aha_1980 The QT Creator requirements say you need at least OpenGL ES 2.0 support. dlxdiag tells me I have OpenGL 3.2.
When I try that command I can't use the design page at all.
-
@aha_1980 No but it didn't crash before unless I used designer. My point is, I did a course, I heard creator/designer/QML/Qt6 was great, so I'm hoping I can use it. I'm also hoping I don't need to buy a gaming PC to do this, just to run linux on it. But I'm seeing that it is going that way.
-
M Mlibu referenced this topic on
-
M Mlibu referenced this topic on
