QT Creator hangs on opening a file or project

[dashthird]

@mrjj

I had tried 2 approaches:
created a new user "test"

1. in new user, simply tried opening QT Creator of E:(installed by old user) & then "File->Open project/file"
   Still the same issue

2. in old user, deleted the QT from E:
   in new user, installed QT at C: & then "File->Open project/file"
   Still the same issue

@hskoglund
Would try your latest CMD method & would let you know the output

[dashthird]

@hskoglund
Yes, Yes, I am able to see the Open Project/file window when I open from CMD using:

C:\Qt\Qt5.6.1\Tools\QtCreator\bin\qtcreator.exe -noload all -load Core

Here's the screenshot:

:)

Where do you think is the cause?

[hskoglund]

So most likely some Qt Creator plugin is the culprit.
To find which one(s), start Qt Creator (you can start it normally), open the Help\About Plugins dialog box.

Try deselecting (making the plugin not Load) some of the plugins, try first with all the plugins listed under Utilities. Then exit Qt Creator, start it again and try Open File or Project and see if it hangs. If it still hangs, try deselecting more plugins. If it does not hang, then try selecting a few plugins to see which one is the bad boy :-)

[JonB]

@hskoglund
Would this be a case where the user should set

set QT_DEBUG_PLUGINS=1

in CMD before running qtcreator.exe and see if it reveals any plugin problem or suspect?

[hskoglund]

@JonB Might be, but the hang does not occur when launching Qt Creator, but when selecting Open File or Project, and by that time most of the plugins are already loaded.

[JonB]

@hskoglund
Yes, I have no idea, I was hoping with QT_DEBUG_PLUGINS they might speak up as they were called to do something and give a clue as to what was happening :)

[hskoglund]

@JonB QT_DEBUG_PLUGINS will cause qDebug() outputs from the likes of qpluginloader.cpp and qlibrary.cpp but a normal plugin I think is an ignoramus re. that env. variable.

But having a dbgview running before trying that Open File or Project hanging stunt can be a good idea, since there might be a qWarning issued in there somewhere...

[dashthird]

@hskoglund
The culprit is the "Welcome" plugin (of "QT Creator" section)
On disabling that, I am now able to do "File->Open file/project" :-)

Now the starting QT UI seems a lot similar like the QT SDK 1.2.1 (maintained by Nokia), which I was using before upgradation to QT 5+ version.

Thanks a lot!!!
I can finally start coding in C++ now :)

One last question: Is there any alternate way to enable the functionality of that "Welcome" plugin ?

[hskoglund]

Hmm don't know any alternate way, you'll have no "Welcome" icon on the left sidebar, but you can use the File menu to create new projects and load existing ones. And browse the Qt Examples manually using File Explorer.

And F1 context help still works in the editor etc so you'll survive I think :-)

Edit: just realized, you're not using a recent Qt Creator (version right now is 4.12.3)?
Some years ago, the Welcome plugin in those old Qt Creator versions relied on OpenGL functionality, so it was a common cure to disable it like you did today (just google for "Qt Creator Welcome plugin problem")
The Welcome plugin was rewritten to not rely on OpenGL, maybe 3 years ago? So you could try update your Qt Creator and re-enable the Welcome plugin...

[dashthird]

@hskoglund
Okay, would try that.

I had actually downloaded a single all-in-one installation package qt-opensource-windows-x86-mingw492-5.6.1-1.exe

I had not edited any QTCreator version in that. The QT Creator 4.0.1 is bundled with v 5.6.1, so may be the latest Creator v4.12.3 is bundled with v5.15. Would check that also

Thanks a lot!
Have marked your answer as the solution :)

[mrjj]

Hi
Holy crap it was the welcome screen that did it ?
That used to stop Creator from running at all if OpenGL support was to weak.
I had never imagined it would affect the file open.
As @hskoglund says, it used to be a common issue.

[jsulm]

@mrjj Looks like the Welcome plug-in becomes smarter :-D

[mrjj]

@jsulm
Hehe yes, thats is clever. Start up and then make native dialog not work. True ninja :)