[SOLVED] Unable to install Qt-5.2 on debian or ubuntu
-
bq. If you have all non-gui parts working then I would suggest to verify the graphics configuration of your Linux.bq.
What would you suggest?
This problem has occured over several installs and builds on different OS's, running different kernels
I have nouveau as the driver for a nvidia card, every other program including Qt 4.8.2 works perfectly.
When I first tried this I was using a different video chip (on-board)
and the i915 driverI tried building from sources some while back and it was only when building a sample program to test the build, that I realised anything GUI wise did not work.
I could build a commandline program no problem and all the build tools work (uic qmake moc etc) -
[quote author="Schooner" date="1398100757"]
What would you suggest?This problem has occured over several installs and builds on different OS's, running different kernels
[/quote]I'm out of ideas.
You can try something like
@
strace qtcreator > strace.log 2>&1
and
ltrace qtcreator > ltrace.log 2>&1
@
to see on what system and library call it stopped. -
I think I am getting somewhere now
I bought a new computer, long overdue, and after the initial install of Debian 7.4 and before even fetching build-essentials, I installed Qt-5.2 from the binary installer.
It worked, creator, designer etc all displayed.
However when I fetched all the pre-requisite packages for my development, Qt had stopped working.
The suspicion is on libglu1-mesa-dev which is required by the openGL plot rendering widget used in the project
New install in progress, this time will add packages incrementally until Qt breaks to confirm which one it is.
Looks like I am going to have to have separate Qt5 and linux development partitions, rather a pain, but when I get to the bottom of it a bug report will be following swiftly after.
regards
-
Well, I have found the problem, or what causes it and it is nothing to do with libs that are installed.
On a completely clean install of debian 7.4, I did a fresh install of Qt 5.2
Tested and it worked fine and then log out.
Next time you log in, it does not work!The error I got trying to open creator was
@
./qtcreator.sh
"Warning reading /home/mick/.config/QtProject/qtcreator/profiles.xml:12: Failed to read element "value"."
"Warning reading /home/mick/.config/QtProject/qtcreator/profiles.xml:12: Failed to read element "value"."
No tool chain set from kit "Desktop Qt 5.2.1 GCC 32bit".
SOFT ASSERT: "tc" in file /work/build/qtsdk/qt-creator/src/plugins/debugger/debuggerkitinformation.cpp, line 62
No tool chain set from kit "Desktop Qt 5.2.1 GCC 32bit".@The first 2 lines are because that file includes a reference to android stuff but I did not even install that.
The rest, who knows.
I can only imagine that whatever environment is set up in the install works and as soon as you log out and log in again, that enviroment is not present.
I have wasted days of my life and am pissed off beyond measure that Qt have f******d a perfectly good system that existed until now with this rubbish.
If I had not needed this to try to participate in a project which uses QtQuick, I would have just deleted it and stuck with 4.8.2 a long while back
-
Hi, I'm not sure if it helps as I had absolutely no problems installing on Debian derivates.
The error messages point to the profile file in .config/QtProject/qtcreator. AFAIK this file will be updated when closing the Creator.
You can check it if you delete profile.xml and start the Creator again.The next lines point to the Kit Desktop Qt 5.2.1 GCC 32bit that is configured in the Creator and appearantly got lost when closing.
I suggest to delete the .xml and look at the kits after restart.
-
That didn't work, even with all copies of the xml deleted, just would not open.
I cloned the git repo and built from sources.
Now when I try to open designer I get
bq. QXcbIntegration: Cannot create platform offscreen surface, neither GLX nor EGL are enabledI have built the full nvidia-glx drivers for my card and now when I use configure it shows
@
OpenGL / OpenVG:
EGL .................. no
OpenGL ............... desktop
OpenVG ............... no
PCRE ................... yes (bundled copy)
pkg-config ............. yes
PulseAudio ............. no
QPA backends:
DirectFB ............. no
EGLFS ................ no
KMS .................. no
LinuxFB .............. yes
XCB .................. yes (system library)
EGL on X ........... no
GLX ................ yes
MIT-SHM ............ yes
Xcb-Xlib ........... yes
Xcursor ............ yes (loaded at runtime)
Xfixes ............. yes (loaded at runtime)
Xi ................. no
Xi2 ................ yes
Xinerama ........... yes (loaded at runtime)
Xrandr ............. yes (loaded at runtime)
Xrender ............ yes
XKB ................ no
XShape ............. yes
XSync .............. yes
XVideo ............. yes@So building again, maybe this will fix it, or maybe it will just give me different errors, who knows
-
I would suggest to rename the directory /home/mick/.config/QtProject/ to something else and then start QtCreator.
Also, as Clochydd pointed, you need to take care of Qt Kit.
Take a look in QtCreator options "Build & Run" page.
Verify that Debuggers, Compilers, Qt Version, and Kits tabs have configured correctly or change them to make them configured correctly.[EDIT]: I typed this too long and this answer suppose to go to your post above last one.
-
Finally some light at the end of the tunnel, or is it just another lost soul with a torch?
Building from git repo with GLX definately enabled - that error went away and the apps just hung with no error.
So the repo will not build and the sources will not build, despite having every library mentioned anywhere in configure installed, plus the -dev version.
bq.
Also, as Clochydd pointed, you need to take care of Qt Kit.
Take a look in QtCreator options “Build & Run” page.
Verify that Debuggers, Compilers, Qt Version, and Kits tabs have configured correctly or change them to make them configured correctly.bq.Thank you for this, because I really was going to throw it all in
I re-installed via the downloader for about the 10th time and deleted every trace from previous attempts.
Whilst open for the first time went into Build and Run and found the 'Automatically Detected' tool chain etc was crap, empty paths, unable to find gdb, but had not ever complained about it,
no system root set, even though it knew where it had installed everything etc etcCloned it and filled it all in manually and apart from the value
'Android-gdb-server' which it keeps filling in in the profile.xml and then complaining about next time it is run, appears to be OKI have logged out and back in and created a silly 'Hello World' app through creator and it displays.
The whole thing regards the installed version, appears to have been prevented from running by its own useless configuration scripts and programs.
-
Now hopefully reached the end of the tunnel, after further setbacks.
The binary installation is hugely sensitive, slightest thing it does not like about the xml files etc, it just refuses to open.
In the course of compiling and running from sources(see below), that changed something again and the binary install would not work until I created a new user dir and did a clean installation and then changed all the same mistakes that Qt made to the build and tool chain, before saving and closing.
I now keep a clone of a fresh install and a corrected install to save wearing out my broadband connection re installing again and again.
The build from sources (git repo) builds fine
Courtesy of my new i7 box, I did it in 24 mins, compared to nearly 2 hrs on the old one!The problem is with make install
You cannot do that as a user because /usr/local was created by root, so you have to sudo make install
This is fine, except that now the build is owned by root and shared with group 'staff'
Making my user a member of 'staff' allowed user access to the compiled sources, which worked.
On closing they overwrote previous configs and next time around neither the binary install or the sources (which had presumably also completely ballsed up the config for build etc) would work.
This has been a frustrating experience to say the least.
What I am taking away from this is that Qt have completely f*****d up a perfectly good system (4.8.x) by trying to be too clever.
Automatic configuration is fine if all your clients are windoze clones running the same system, but if you can't cater for every flavour and configuration of *nix (which no-one can), don't even try, ask questions during the install so that it is done right.
Hopefully this is my last post.
I am leaving the thread [Partially Solved] because the same thing will happen to everyone else until Qt 5 is sorted out.
I am sure the only reason there are not more similar threads is that most people just give up in disgust and never go back to it.
-
[quote author="andreyc" date="1398362735"]Correction. It is
@
./configure -prefix $HOME/Qt ...
@[/quote]Thanks, I am aware of config options, it is a side issue really, just an illustration of the screwy install that by default it installs to a dir that the user may well not have write access to, without doing anything to ensure it suceeds.
My binary install stopped working AGAIN yesterday, so I have removed all traces of it and built from git sources in the proper place (/usr/local/src not a user home dir, which to my mind should only contain config files, never binaries) and installed in /usr/local.
After setting up .bashrc with paths, deleting qtcreator.sh to stop it screwing them up and setting correct permissions, it APPEARS to be working properly.
An encouraging point was that having built creator from sources, its default generated toolkit entries were actually correct.Heres hoping
-
Solved at last
Qt5 is incompatable with icewm.
Apps launched through it cannot get the current X server.There is a bug report
http://sourceforge.net/p/icewm/bugs/909/
which says it is fixed, but it is not, built from sources and still does not workQt5 obviously does something different regards X to all previous versions
I have used icewm for upwards of 15 years, it is the first thing I install on a new system.
The installation process for Qt5 is screwy, some default entries in the configs are rubbish, but what was stopping it running was being invoked when running icewm.
I only discovered this because my user uses lightdm by default and I logged in without switching to icewm.
Having previously hung without any error, qtcreator now ran.When I had built and installed by download, I probably just used the defaults as well as I was just doing that one thing in a terminal then leaving it to complete.
This needs flagging up somewhere prominant, so that other people do not have weeks of problems as I had.
The information is out there, but only if you have a suspicion where to look first