QT Creator doesn't open after installation
-
Well, that strange, did the installation fail at some point ?
-
Looks like the best thing to do, especially if there's no exe file containing creator anywhere
-
-
Same problem here,
SO: Windows 10 Preview Insider.
Qt: 5.4.2I can't open Qt Creator, I have tried downgrading to Qt 5.3 and Qt Creator 3.3, but it doesn't work.
@Crazybunny and @mchinand, in MinGW, QtCreator binary is located at C:\Qt\Tools\QtCreator\bin\qtcreator.exe, running from terminal, it doesn't give any error message. -
@hipersayan_x If you're running in an msys shell you can use strace qtcreator.exe and it will show you the system calls it is making. That should shed some light on what is happening.
If you don't use msys then you can use procmon but it would be a lot more complicated than a simple strace.
-
@ambershark, strace is not installed in MSYS, and I can't understand the output of procmon.
Edit: Ok, I found it, strace can be installed with:
mingw-get install msys-core-dbgBut it does not gives any error output.
-
@hipersayan_x What output does it give?
-
@ambershark if you are referring to strace, it shows absolutely nothing, about procmon, this is the output in CSV format.
-
@hipersayan_x Very odd that strace shows nothing. That means it's not working. It will always show something. No big deal though, procmon has all the info you need.
So looking through that log, I notice 2 things,
-
Qtcreator is crashing and calling werfault.exe which is windows' error reporting tool. Based on this line in the procmon log:
"08:38:17,2428061 p.m.","qtcreator.exe","376","Process Create","C:\WINDOWS\system32\WerFault.exe","SUCCESS","PID: 3204, Command line: C:\WINDOWS\system32\WerFault.exe -u -p 376 -s 1236" -
Qtcreator is exiting without a 0 return code indicating a failure based on this line:
"08:38:30,2722231 p.m.","qtcreator.exe","376","Process Exit","","SUCCESS","Exit Status: -1073741819, User Time: 0.8437500 seconds, Kernel Time: 1.2500000 seconds, Private Bytes: 54.972.416, Peak Private Bytes: 55.103.488, Working Set: 100.925.440, Peak Working Set: 101.199.872"
Surprisingly werfault.exe should be displaying a "this app has crashed" type message with debugging information. Weird that it isn't. From your original post you said it wasn't displaying any error.
You could dig through that procmon log in more detail, I don't really have time to go that in depth on this. You may find something that it is trying to start/use that is failing or something.
Finally my last advice would be to start qtcreator in a debugger, then you could get a backtrace and hopefully that might have a clue as to what is going on.
For instance I used gdb on assistant (I don't have or use qt creator) and this was the backtrace I got when I interrupted it:
Program received signal SIGINT, Interrupt. 0x00007ffff2739c8d in poll () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff2739c8d in poll () from /lib64/libc.so.6 #1 0x00007ffff0498734 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007ffff049883c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007ffff3a2d25b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/local/Qt-5.4.2/lib/libQt5Core.so.5 #4 0x00007ffff39d3e8b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/local/Qt-5.4.2/lib/libQt5Core.so.5 #5 0x00007ffff39db516 in QCoreApplication::exec() () from /usr/local/Qt-5.4.2/lib/libQt5Core.so.5 #6 0x00000000004240fe in ?? () #7 0x00007ffff267caa5 in __libc_start_main () from /lib64/libc.so.6 #8 0x0000000000424790 in ?? () (gdb)So that shows me it was in the processEvents loop when I broke in. Maybe (especially since you are crashing) you could get a useful bt. Post it here if you get one and I can take a peek at it, see if I notice something.
Oh one last thing, I noticed in procmon you were running in a virtualbox. I have had issues with qt creator in virtualbox/windows before. It was a long time ago, 2 or 3 years, so I don't remember the exact problem. It had something to do with drawing and 3D or opengl or something like that. Like I said I can't remember, just remember having an issue. Of course I don't remember my resolution either. :/ It also didn't cause a crash but just caused the welcome page not to load. But just throwing that out there in case that sparks something in your head.
-
-
@ambershark said:
Surprisingly werfault.exe should be displaying a "this app has crashed" type message with debugging information. Weird that it isn't. From your original post you said it wasn't displaying any error.
Finally my last advice would be to start qtcreator in a debugger, then you could get a backtrace and hopefully that might have a clue as to what is going on.Ok, I'm starting to think that definitively its not a problem of Qt Creator, but a Windows thing. After running qtcreator with GDB, after a few seconds of running, qtcreator start some threads, then GDB show a message that says sect_index_data not initialized, and finally, GDB dies with a dialog box and a message in console that says the apps stopped working, thats all, no debugging trace, no nothing :/
Oh one last thing, I noticed in procmon you were running in a virtualbox. I have had issues with qt creator in virtualbox/windows before. It was a long time ago, 2 or 3 years, so I don't remember the exact problem. It had something to do with drawing and 3D or opengl or something like that. Like I said I can't remember, just remember having an issue. Of course I don't remember my resolution either. :/ It also didn't cause a crash but just caused the welcome page not to load. But just throwing that out there in case that sparks something in your head.
A few hours before all this happens, I was running Qt Creator normally (I don't remember what version was then), and after a full system update, it stopped working. But when working, my app started with a blank window and showing this messages:
Qt: Untested Windows version 10.0 detected! QML debugging is enabled. Only use this in a safe environment. QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::allocate(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::allocate(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::allocate(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLShader: could not create shader QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLShaderProgram::uniformLocation( imageTexture ): shader program is not linked QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::allocate(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLShader: could not create shader QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLShaderProgram::uniformLocation( imageTexture ): shader program is not linked QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::allocate(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: ""But when working in Windows 8.1, it worked flawlessly in VirtualBox. I will try a downgrade to Windows 8.1.
Anyway, thank you very much @ambershark, your responses where very helpful :)
-
Ah that makes sense then. VirtualBox is a bit behind when coming to upgrades for windows, especially ones that aren't officially released yet.
It looks like it is having problems with OpenGL again which was a problem I noticed before in my vm using qt creator.
I would definitely blame virtualbox at this point. Good news is they are pretty quick to get things working well within a month of official releases. Usually they are ready before the official release.
