Activity log for bug #1164504

Date Who What changed Old value New value Message
2013-04-04 13:31:06 Timo Jyrinki bug added bug
2013-04-04 13:34:30 Timo Jyrinki description Continuation from bug #1135336. Now the system default Qt is correctly recognized by Qt Creator at first run. However if the system was not correctly set up on the first run, or if the configuration changes, Qt Creator does not notice this and multiple things in Qt Creator configuration may be broken. Removing the configuration files is currently the only "easy" way to make Qt Creator autodetect system environment again: rm -r .config/Trolltech.conf .config/Qt* .config/Nokia* Otherwise you can see the bug #1135336 description on how to manually fix various pieces of Qt Creator configuration via settings dialogs. Continuation from bug #1135336 (as is bug #1164508). Now the system default Qt is correctly recognized by Qt Creator at first run. However if the system was not correctly set up on the first run, or if the configuration changes, Qt Creator does not notice this and multiple things in Qt Creator configuration may be broken. Removing the configuration files is currently the only "easy" way to make Qt Creator autodetect system environment again: rm -r .config/Trolltech.conf .config/Qt* .config/Nokia* Otherwise you can see the bug #1135336 description on how to manually fix various pieces of Qt Creator configuration via settings dialogs.
2013-04-04 13:34:38 Timo Jyrinki summary No automatic reconfiguration / reconfiguration option when system environment changes No automatic reconfiguration / reconfiguration feature when system environment changes
2013-04-04 13:34:44 Timo Jyrinki qtcreator (Ubuntu): importance Undecided Wishlist
2013-04-04 13:34:46 Timo Jyrinki qtcreator (Ubuntu): status New Won't Fix
2013-04-04 13:34:49 Timo Jyrinki qtcreator (Ubuntu): status Won't Fix Confirmed
2013-04-05 06:01:35 Timo Jyrinki description Continuation from bug #1135336 (as is bug #1164508). Now the system default Qt is correctly recognized by Qt Creator at first run. However if the system was not correctly set up on the first run, or if the configuration changes, Qt Creator does not notice this and multiple things in Qt Creator configuration may be broken. Removing the configuration files is currently the only "easy" way to make Qt Creator autodetect system environment again: rm -r .config/Trolltech.conf .config/Qt* .config/Nokia* Otherwise you can see the bug #1135336 description on how to manually fix various pieces of Qt Creator configuration via settings dialogs. Continuation from bug #1135336 (as is bug #1164508). Now the system default Qt is correctly recognized by Qt Creator at first run. However if the system was not correctly set up on the first run, or if the configuration changes, Qt Creator does not notice this and multiple things in Qt Creator configuration may be broken. It would be useful to have some sort of "reconfigure" button, overwriting old config. Removing the configuration files is currently the only "easy" way to make Qt Creator autodetect system environment again: rm -r .config/Trolltech.conf .config/Qt* .config/Nokia* Otherwise you can see the bug #1135336 description on how to manually fix various pieces of Qt Creator configuration via settings dialogs.
2013-05-08 13:50:52 Timo Jyrinki description Continuation from bug #1135336 (as is bug #1164508). Now the system default Qt is correctly recognized by Qt Creator at first run. However if the system was not correctly set up on the first run, or if the configuration changes, Qt Creator does not notice this and multiple things in Qt Creator configuration may be broken. It would be useful to have some sort of "reconfigure" button, overwriting old config. Removing the configuration files is currently the only "easy" way to make Qt Creator autodetect system environment again: rm -r .config/Trolltech.conf .config/Qt* .config/Nokia* Otherwise you can see the bug #1135336 description on how to manually fix various pieces of Qt Creator configuration via settings dialogs. Continuation from bug #1135336 (as is bug #1164508). Now the system default Qt is correctly recognized by Qt Creator at first run. However if the system was not correctly set up on the first run, or if the configuration changes, Qt Creator does not notice this and multiple things in Qt Creator configuration may be broken. It would be useful to have some sort of "reconfigure" button, overwriting old config. Removing the configuration files is currently the only "easy" way to make Qt Creator autodetect system environment again: rm -r .config/Trolltech.conf .config/Qt* .config/Nokia* Otherwise you can see the bug #1135336 description on how to manually fix various pieces of Qt Creator configuration via settings dialogs.
2014-09-09 13:58:57 nightsparc bug added subscriber Marc Schmitt
2015-08-11 09:35:53 Launchpad Janitor branch linked lp:~kubuntu-packagers/kubuntu-packaging/qtcreator
2015-08-16 22:42:24 Launchpad Janitor qtcreator (Ubuntu): status Confirmed Fix Released