<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFCC">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 07/11/2018 01:41 PM, Nikos
Chantziaras wrote:<br>
</div>
<blockquote type="cite"
cite="mid:mailman.2335.1531334497.3940.interest@qt-project.org">
<pre wrap=""><div class="moz-txt-sig">On 10/07/18 06:08, Alan Ezust wrote:
</div></pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap="">I just installed Qt Creator 4.5.2 from kubuntu apt sources.
It installed qmlscene + qt development files at the same time.
I can see clearly there is a qmlscene executable right next to qmake in
the same directory: /usr/lib/qt5/bin
How do I get rid of the "no qmlscene installed" warning?
</pre>
</blockquote>
<pre wrap="">I've been using Creator from distro repos for a while in the past, and
quite often this would result in some weirdness or breakage. I recommend
installing Creator using the online installer instead.
</pre>
</blockquote>
This happens due to many reasons.<br>
<br>
1) Some fool used qml to create the welcome screen thus first
introducing the problem. qml should never be used for anything.<br>
2) The 12 year old boys who crow about being "maintainers" of
packages do little in the way of actual maintenance and testing.
They simply remove anything someone complains about or which doesn't
compile.<br>
3) Ubuntu doesn't test shit. They rely on the YABUs (Yet Another
uBUntu) to provide fixes for them<br>
4) Virtual Machines tend to hose QtCreator, or at least historically
did.<br>
<a class="moz-txt-link-freetext" href="https://bugreports.qt.io/browse/QTCREATORBUG-9586">https://bugreports.qt.io/browse/QTCREATORBUG-9586</a><br>
<br>
<br>
Assuming you don't have a great investment in KUbuntu with
installation, configuration,etc. Your simplest fix would be to move
to KDE Neon <br>
<br>
<a class="moz-txt-link-freetext" href="https://neon.kde.org">https://neon.kde.org</a><br>
<br>
The people who used to be creating KUbuntu but had __severe__ issues
with the lack of testing and general state of life at/with Canonical
jumped ship and created KDE Neon based on a YABU core. Far more
testing is done and they are migrating to their own repos. I say
this because what Canonical has creating KUbuntu now reminds me of
"The Replacements"<br>
<a class="moz-txt-link-freetext" href="https://www.imdb.com/title/tt0191397/?ref_=nv_sr_1">https://www.imdb.com/title/tt0191397/?ref_=nv_sr_1</a><br>
And, because I'm typing this on KDE Neon where I have QtCreator
4.6.2-1 installed from the repos without the welcome screen issue.
Like I said, KDE Neon does something which can actually be called
testing.<br>
<br>
If you are really in love with KUbuntu or married to it because it
was documented via government filings as "the" development
environment, you should know there are tons of "fixes" and "work
arounds" out there.<br>
<br>
Assuming you are a good Qt developer and not allowing QML within
10,000 miles of your project, you can simply skip loading the
Welcome screen. I do believe the virus known as QML has also wormed
its way into the examples display pages, so you will have the same
problems there.<br>
<br>
<pre>qtcreator -noload Welcome</pre>
<br>
Please note the capital W on Welcome. Sorry, nobody has been polite
enough to add -list to qtcreator so you could see a list of plugins
to be loaded. They did add -profile, but, you really need to
redirect that output to a text file you can search with Jed or some
other editor for plugins.<br>
<br>
Once you've determined this works, you can save yourself trouble by
clicking on Help->About Plugins then scrolling down until you
find Welcome to turn off the loading of it.<br>
<br>
Of course, you might want to determine your particular 12 year old
boy didn't just hose the pluginpath once again. From the -help
output<br>
<br>
-pluginpath <path> Add a custom search path for
plugins<br>
<br>
start qtcreator from the command line providing the full path to the
plugin and see if the problem also goes away. If so<br>
<br>
cd /<br>
sudo find -iname qt.conf<br>
<br>
cat out the file and look for plugins, here is what mine shows<br>
<br>
<pre>roland@roland-I5-HP-Compaq-8300-Elite-SFF-PC:/$ cat ./usr/lib/x86_64-linux-gnu/qt5/qt.conf</pre>
<pre>[Paths]</pre>
<pre>Prefix=/usr</pre>
<pre>ArchData=lib/x86_64-linux-gnu/qt5</pre>
<pre>Binaries=lib/qt5/bin</pre>
<pre>Data=share/qt5</pre>
<pre>Documentation=share/qt5/doc</pre>
<pre>Examples=lib/x86_64-linux-gnu/qt5/examples</pre>
<pre>Headers=include/x86_64-linux-gnu/qt5</pre>
<pre>HostBinaries=lib/qt5/bin</pre>
<pre>HostData=lib/x86_64-linux-gnu/qt5</pre>
<pre>HostLibraries=lib/x86_64-linux-gnu</pre>
<pre>Imports=lib/x86_64-linux-gnu/qt5/imports</pre>
<pre>Libraries=lib/x86_64-linux-gnu</pre>
<pre>LibraryExecutables=lib/x86_64-linux-gnu/qt5/libexec</pre>
<pre>Plugins=lib/x86_64-linux-gnu/qt5/plugins</pre>
<pre>Qml2Imports=lib/x86_64-linux-gnu/qt5/qml</pre>
<pre>Settings=/etc/xdg</pre>
<pre>Translations=share/qt5/translations</pre>
Either your plugin isn't in the correct directory, or the value here
is incorrect. Common 12 year old boy problem. I must confess to not
knowing the syntax of or even if it is possible to have 2 different
paths on one of these lines. You can set the environment variable
QT_PLUGIN_PATH<br>
<br>
Linux != Linux != Linux<br>
<br>
Each and every distro decides "they have a better layout" when it
comes to storing stuff. This then makes 90% of the "maintainer's"
job bulk editing scripts to change locations with each update. They
miss stuff. QtCreator tends to be one of the most abused and least
tested packages when it comes to "maintainers."<br>
<br>
KDE Neon will make your life a touch easier because they use Qt.<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Roland Hughes, President
Logikal Solutions
(630)-205-1593
<a class="moz-txt-link-freetext" href="http://www.theminimumyouneedtoknow.com">http://www.theminimumyouneedtoknow.com</a>
<a class="moz-txt-link-freetext" href="http://www.infiniteexposure.net">http://www.infiniteexposure.net</a>
<a class="moz-txt-link-freetext" href="http://www.johnsmith-book.com">http://www.johnsmith-book.com</a>
<a class="moz-txt-link-freetext" href="http://www.logikalblog.com">http://www.logikalblog.com</a>
<a class="moz-txt-link-freetext" href="http://www.interestingauthors.com/blog">http://www.interestingauthors.com/blog</a>
<a class="moz-txt-link-freetext" href="http://lesedi.us/">http://lesedi.us/</a>
<a class="moz-txt-link-freetext" href="http://onedollarcontentstore.com">http://onedollarcontentstore.com</a></pre>
</body>
</html>