[Bug 1135336] Re: Qt Creator misconfigures itself if qt4-qmake is installed or if the whole ubuntu-sdk isn't installed before the first run

Timo Jyrinki timo.jyrinki at canonical.com
Sat Mar 9 06:29:52 UTC 2013


** Description changed:

  Qt Creator only auto-detects Qt 4 and not Qt 5, if both are installed.
  If qt4-qmake is then removed, Qt 5 will be automatically detected,
  although only if the old Qt Creator configuration is first removed.
  
  If you are having this bug, multiple things in Qt Creator configuration
  may be broken. You can either try to fix the problems manually, or
  remove the qt4-qmake package and reset the Qt Creator configuration.
  
  == Similar misconfiguration causes ==
  
  The following cases cause the same problem, even though they are not
  related to having Qt 4 development binaries (qt4-qmake especially)
  installed:
  
  - Qt Creator also misconfigures itself if not all of ubuntu-sdk has been installed before the first launch, and these same problems come up then. Either the Qt Creator configuration resetting or manual fixing is needed also in this case.
  - Qt Creator also misconfigures itself if a proper removal of the old Qt 5 Beta 1 PPA has not been done: http://askubuntu.com/questions/254800/how-can-i-update-the-ubuntu-sdk-preview-from-the-qt-5-beta-ppa-to-the-qt-5-relea
  
  == Symptoms ==
  
  Symptoms of having the problem include:
  - Not being able to "Run" QML projects
  - Getting QML Import complaints when going to the Design tab
  - Missing Ubuntu UI wizard options (this can also be cause by not having the special package ubuntu-qtcreator-plugins from ubuntu-sdk-ppa installed)
  
  == Methods of fixing ==
  
  === Automatically fixing Qt Creator settings by resetting configuration
  ===
  
  If you can or want to reset all the Qt Creator configuration:
  1. Quit Qt Creator
- 2. Remove the files .config/Trolltech.conf .config/Qt*.
+ 2. Remove the following files rm -r .config/Trolltech.conf .config/Qt* .config/Nokia*
  3. Remove the qt4-qmake package if you didn't already remove it.
  4. Check that ubuntu-sdk is installed.
  5. Now start Qt Creator, and it should have everything functional.
  
  === Manually fixing Qt Creator settings ===
  
  You can go through the manual route if you don't want to remove all your
  Qt Creator settings, or just want to learn about how to configure Qt
  Creator in general.
  
  As a first step you need to go Tools -> Options -> Qt Versions -> Add...
  and add the /usr/bin/qmake which then identifies itself as Qt 5.0.0 or
  5.0.1. Remove Qt 4 references if you don't need those.
  
  If still having problems, you need to check the Kits tab as well to
  double-check that the "Desktop (default)" has Qt version "Qt 5.0.1
  (System)" set. Not having it set can for example result in Build -> Run
  being greyed out when having qmlproject like lp:~dpm/+junk/ubuntu-app-
  dev-cookbook opened.
  
  If the Build -> Run is still greyed out after this when you've a
  CurrencyConverter.qmlproject open from above link, but Tools -> Options
  settings seem fine, open the "Projects" from the left pane in Qt
  Creator. Check that you have a kit defined (use the "Add Kit" dropdown
  if not), after which you should have the Desktop -> Run tab filled with
  "Run configuration: "QML Scene" for example. Now the Run should work.
  
  Also the QML Import Path might be broken if qt4-qmake package was
  installed during the time of first run of Qt Creator. This is shown in
  the Design tab from the left pane not functioning for Ubuntu UI
  projects.
  
  TODO: how to reset the QML Import Path from the UI without resetting all
  configuration?

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qtcreator in Ubuntu.
https://bugs.launchpad.net/bugs/1135336

Title:
  Qt Creator misconfigures itself if qt4-qmake is installed or if the
  whole ubuntu-sdk isn't installed before the first run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1135336/+subscriptions




More information about the kubuntu-bugs mailing list