CentOS 7 ships with Qt 5.6, is there a way of upgrading to Qt 5.9?. current version. QMake version 3.0 Using Qt version 5.6.2 in /usr/lib64 I dont want to install Qt from qt.io , as I am not going to develop applications, the application I'm trying to run requires QtQuick version 2.9 which is available in Qt 5.9.

I am trying to use Translation feature in QT. There are more than 4000 translation needed to be done for one language. And I have to do this for more than 15 different languages. So, I decide to write language.ts files by shell scripts. After generating my language.ts succesfully, I open the file in notepad++ (in windows) and I can see the expected translation in the file. For example, in Brazilian language, following is the translation code is language.tsfile:- Cancel Отказ Now when I try open the file in QT Linguist tool, I got following error:- Parse error at lang_Brazil.ts:1:38:Encountered incorrectly encoded content. As details provided in this website , I replace encoding value utf-8 with ISO-8859-1 . Now I can open the file in QT Linguist but the translation is showing wrong characters, ex:- for Cancel it is showing Îòêàç (expected translation is Отказ). Please confirm why it is not taking right translation in QT linguist while I can see it if I open language.ts file in notepad++.

Recently I have installed Zorin os and qt creator from enter link description here I am using qt creator and here is my sample code to connect the MySQL database. QSqlDatabase db = QSqlDatabase::addDatabase("QMYSQL"); db.setHostName("localhost"); db.setDatabaseName("csms"); db.setUserName("root"); db.setPassword(""); bool ok = db.open(); if(ok) { qDebug() << "Database connected." << Qt::endl; } else { qDebug() << "Database connection error." << db.lastError ()<< Qt::endl; } But failed. I am googling the last two days but no luck. Now I am here. I need help.

I feel like there should be a simple way of doing this, but my googlefu is failing so I'd really appreciate some info on how to switch (or even permanently change) which version of Qt is used when doing qmake. If I ask which version I get the following: ~ $ qmake --version QMake version 3.0 Using Qt version 5.0.1 in /usr/lib/x86_64-linux-gnu I've install QtCreator, but I'm not sure where to go from here.

I am using a Core i7 PC with NVIDIA GM107 GeForce GTX 750 Ti video card running Linux Mint 18.3. "Valgrind Memory Analyzer" crashes when running a blank "Qt Widgets Application" project in Qt Creator 4.10.1 with the "external error" message: 286,959 bytes in 1 blocks are possibly lost in loss record 78 of 78 in calloc in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so 1: calloc in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so 2: /usr/lib/nvidia-384/libGL.so.384.130 3: /usr/lib/nvidia-384/libnvidia-glcore.so.384.130 4: /usr/lib/nvidia-384/libnvidia-glcore.so.384.130 5: /usr/lib/nvidia-384/libGL.so.384.130 6: /usr/lib/nvidia-384/libGL.so.384.130 7: /usr/lib/nvidia-384/libGL.so.384.130 8: call_init.part.0 in /build/glibc-LK5gWL/glibc-2.23/elf/dl-init.c:58 9: call_init in /build/glibc-LK5gWL/glibc-2.23/elf/dl-init.c:30 10: _dl_init in /build/glibc-LK5gWL/glibc-2.23/elf/dl-init.c:120 11: /lib/x86_64-linux-gnu/ld-2.23.so Here's the run log: 19:17:40: valgrind --child-silent-after-fork=yes --xml- socket=127.0.0.1:41595 --log-socket=127.0.0.1:37293 --xml=yes --smc- check=stack --tool=memcheck --gen-suppressions=all --track-origins=yes --leak-check=summary --num-callers=25 /home/daniel/Documents/QtNew/build- TestWidgets-Desktop_Qt_5_12_5_GCC_64bit-Debug/TestWidgets 19:17:44: The program has unexpectedly finished. 19:17:44: Process exited with return value Process crashed 19:17:44: Analyzing finished. I don't get any warning / error if I run the program normally i.e. without Valgrind. **Update** I upgraded Valgrind from source to version "3.15.0" and the crash problem went away.

I use KDE, I have a HiDPI display, so I made changes to ~/.Xresources to change the system DPI. After that, the fonts in some applications began to look pixelated. In QtCreator, with QT_SCALE_FACTOR=1.2, icons become pixelated. How to fix this problem? My ~/.Xresources: Xft.dpi: 120 Xft.antialias: true Xft.rgba: rgb Xft.hinting: true Xft.hintstyle: hintslight Output of xrdb -q: Xft.antialias: 1 Xft.dpi: 120 Xft.hinting: -1 Xft.hintstyle: hintslight Xft.rgba: none **UPD:** My system:
Operating System: Arch Linux
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
Kernel Version: 5.2.1-arch1-1-ARCH

I am trying to find the .desktop file for qtcreator, so I write this: $ for p in ${XDG_DATA_DIRS//:/ }; do grep -rni 'qtcreator' $p; done And here is the most relevant lines: /usr/share/app-install/desktop/qtcreator-plugin-ubuntu:ubuntusdk.desktop:2:X-AppInstall-Package=qtcreator-plugin-ubuntu /usr/share/app-install/desktop/qtcreator-plugin-ubuntu:ubuntusdk.desktop:6:Exec=qtcreator %F /usr/share/app-install/desktop/qtcreator-plugin-ubuntu:ubuntusdk.desktop:7:Icon=ubuntu-qtcreator /usr/share/app-install/desktop/qtcreator:qtcreator.desktop:2:X-AppInstall-Package=qtcreator /usr/share/app-install/desktop/qtcreator:qtcreator.desktop:6:Exec=qtcreator %F /usr/share/app-install/desktop/qtcreator:qtcreator.desktop:7:Icon=QtProject-qtcreator /usr/share/app-install/desktop/qhimdtransfer:qhimdtransfer.desktop:12:#Icon=qtcreator_logo_32 I think the qtcreator:qtcreator.desktop is the desktop entry for QtCreator, so I open it and find out: [Desktop Entry] X-AppInstall-Package=qtcreator X-AppInstall-Popcon=292 X-AppInstall-Section=universe Exec=qtcreator %F Icon=QtProject-qtcreator Type=Application Terminal=false Name=Qt Creator GenericName=Integrated Development Environment MimeType=text/x-c++src;text/x-c++hdr;text/x-xsrc;application/x-designer;application/vnd.nokia.qt.qmakeprofile;application/vnd.nokia.xml.qt.resource; Categories=Qt;Development;IDE; InitialPreference=9 X-Ubuntu-Gettext-Domain=app-install-data **qtcreator is not in the variable $PATH of the shell**. But I can still launch QtCreator in gnome unity. From the [freedesktop-exec-variables](https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#exec-variables) I noticed > If no full path is provided the executable is looked up in the $PATH environment variable used by the desktop environment. ### Question Is $PATH environment variable of a desktop environment different from that is a shell? If so, where is the config file containing the $PATH variable for desktop environment? I install a newer version of QtCreator then launch QtCreator in desktop and find out it references to the newer version without changing the qtcreator:qtcreator.desktop file. I think there is something to with the path of qt? Desktop environment: gnome OS: ubuntu16.04 **Edit** The actual problem I encountered was not about $PATH(see my answer blow). Gilles' answer is actually the answer to `Is $PATH environment variable of a desktop environment different from that in a shell?' so I accepted it in case that someone has the same doubt as me.

I tried to use KDE's Konsole to start console applications from QtCreator. The application works as intended, but any new instance of Konsole started during or after the execution just shows this: Cannot read creator env file /tmp/QtCreator.UiK966: No such file or directory Press to close this window... or a similar error Cannot connect creator comm socket Qt Creator console The second one is not complete because it didn't occur anymore and I can't find the text anymore. Closing ALL instances of Konsole fixes the problem until I start any console project from QtCreator again. QtCreator Tools/Options/Environment/System/Terminal is set to /usr/bin/konsole -e QtCreator appends the following to the command set in Terminal: /usr/bin/../libexec/qtcreator/qtcreator_process_stub run /tmp/QtCreator.GJt966/stub-socket "Press to close this window..." /home/zzt/.build/untitled-Desktop-Debug /tmp/QtCreator.UiK966 966 /home/zzt/.build/untitled-Desktop-Debug/untitled There was a known bug in QtCreator that resulted in the described behaviour, but only in the Konsole instance that was started by QtCreator and that is supposedly fixed. The problem occurs on a Oracle VirtualBox VM running Arch, but does not occur on my laptop running the same OS and the same Konsole&QtCreator versions. Configuration is similar on both systems but can definitely differ. $ konsole --version konsole 16.08.3 $ qtcreator -version Qt Creator 4.1.0 based on Qt 5.7.0 ... $ uname -a Linux archvm 4.8.8-2-ARCH #1 SMP PREEMPT Thu Nov 17 14:51:03 CET 2016 x86_64 GNU/Linux

I am trying to run qtcreator. It powers up fine on the local (Ubuntu 16.4) box, but when I try to run it over X to a Mac I get this: (qtcreator:3893): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-LglOS2bxyZ: Connection refused libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Unrecognized OpenGL version Unrecognized OpenGL version Searching these messages usually suggests that this is a driver problem and suggest a fix on the (local) box, but that doesn't seem relevant here. Any ideas as to how I might fix this so I can run it remotely? (NB: the qtcreator process is still running when this happens, just 'headless' and useless)

I've read plenty of discussions on various possibilities why such a thing can happen however all are about some missing library on the system where the binaries are deployed. This is not my case. I have a Raspberry Pi 2 with latest Raspbian and a Debian 8 notebook with x86-64 Intel architecture and a Qt Creator 3.2.1 installed on the second, where I cross-compile my binaries using the **arm-linux-gnueabihf-g++** (using the Emdebian repository). I am not using the optimized compiler provided in the official RPi github repository . Here is the prequal to my problem . After much sweat and swearing I managed to cross-compile and deploy my binary from the notebook onto the RPi2. And here is the problem: - When I try to run my binary from withing Qt Creator (which connects to the RPi2 via SSH, transfers files via SFTP and is logged in as my only RPi user (hence "access issue" is excluded here for sure)) on **my notebook** I get: Syntax error: word unexpected (expecting ")") - When I try to run my binary **directly on my RPi** it runs without a single issue. As I've posted on stackoverflow my code contains only pure C++ writing a text file to the directory where the binary is upon execution. Nothing weird going on there. So the main question here is is this a Qt Creator related issue or something that goes much deeper? I have no idea how exactly Qt Creator internally **runs** the binary on the remote system. If I connect via SSH to my RPi via terminal and execute the binary it works fine. So it has to do something with the way Qt Creator executes it. Note that executing the ARM binary on my notebook returns what we all expect (RPiCrossCompileRemoteTest is the name of my binary): bash: ./RPiCrossCompileRemoteTest: cannot execute binary file: Exec format error So Qt Creator neither starts the binary straight onto the RPi nor tries to start it on my notebook (otherwise it would have given me the format error from above). Any ideas how I can proceed towards resolving this? I have been fighting with this issue for a couple of days all in vain. :-/ **EDIT:** As suggested by @steve running ldd on both executables: - On the RPi: /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0x76f84000) libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0x76ea3000) libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x76e32000) libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x76e0a000) libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76cda000) /lib/ld-linux-armhf.so.3 (0x76f91000) - On the notebook: not a dynamic executable The second one is correct. I don't know that to think about the first one though. Also I used the g++-arm-linux-gnueabihf that is in my Raspbian to compile a new binary in order to compare both. The **output of ldd is literally the same** with the small exception that I have different memory addresses (the HEX numbers in brackets) where the libs will be loaded. **EDIT 2:** As @gogoud suggested: - Changed to key authentification - Checked shell on my RPi - it is bash - Added RequestTTY=force to a newly created **~/.ssh/config** No change at all. Same old story. I did however notice the actual exit code: **2**. From TLDP : > 2: Misuse of shell builtins (according to Bash documentation) > Example: empty_function() {} > Comments: Missing keyword or command, or permission problem (and diff return code on a failed binary file comparison). This doesn't make sense for my binary (I think). I have also checked the permissions on it: drwxr-xr-x. This means that all can execute and read it.

My system is running Ubuntu 16.04 LTS. I seem to have installed Qt in two places. 4.8.7 is installed in /usr and 5.5.1 is installed in my home directory for reasons which probably seemed sensible at the time. $ /usr/bin/qmake -v QMake version 2.01a Using Qt version 4.8.7 in /usr/lib/x86_64-linux-gnu $ ~/Qt/5.5/gcc_64/bin/qmake -v QMake version 3.0 Using Qt version 5.5.1 in /home/jsd/Qt/5.5/gcc_64/lib $ which qmake /usr/bin/qmake Qt Creator sees the home-directory version and thinks it's running 5.5.1, but when it runs qmake in the build process it runs the 4.8.7 version and minor annoyances follow. How can I clean this up? Also, is it normal for Qt to be installed in my home directory? **Edit:** The reason this was an issue is Qt Creator was ignoring CONFIG += c++14 and refusing to allow C++14 syntax like auto foo = [](const a, const b){return a when compiling with Clang 3.7, which should support C++14. qmake only supported CONFIG += c++14 since 5.4 hence I thought the problem was my old qmake version.