Hi The normal way to find out what is going on is using the debugger. So compile the app In debug mode and start it. When it crashes you should be able to see what it was doing in the call stack. The call stack is the area under the editor window when starting in debug mode As you can see it shows where the program was running. The function list. This should give a hint as to why it does crash.

See for example QTextCurso::setCharFormat.

@sierdzio It doesn't work for me with Qt Creator 6.0.1 either.

This is indeed a known issue, see e.g. https://bugreports.qt.io/browse/QTCREATORBUG-26647. It will be fixed in Qt Creator 6.0.1. Meanwhile, you can try using a snapshot from https://download.qt.io/snapshots/qtcreator/6.0/ .

Solved it. The solution was very easy: sudo mkdir /root/Downloads/

I forgot about that one ! It has also bitten me on several occasions. Glad you found out and thanks for sharing :-)

Hi As far as i understand from google its a LLVM bug but should be fixed a long time ago. Would it be possible to update to a newer version? Also, between it worked. and then stopped. can it be that you reboot the WM ? (versus pausing it)

Ok it was resolved. I don't know why exactly. Error message showing as normal string at debug mode.

Too bad, it is very annoying to work in one instance and always have to switch between kits. Makes it quite uncomfortable to work on multiple projects in parallel.

Solved by: adb kill-server sudo cp ~/Android/Sdk/platform-tools/adb /usr/bin/adb sudo chmod +x /usr/bin/adb adb start-server thanks to this

There is also the following pop-up when opening test.c in the sample project: Warning: The code model could not parse an included file, which might lead to incorrect code completion and highlighting, for example. stdio.h:33:10: fatal error: 'stddef.h' file not found test.c:1:1: note: in file included from /home/user/CODE/test/test.c:1: test.c:2:10: note: in file included from /home/user/CODE/test/test.c:2: stddef.h is in the same directory as omp.h.

Hi @magartor, thanks for the feedback. So please mark this topic as SOLVED. Thanks!

If possible maybe somebody could clone the repository and try it his computer to open project and run CMake. Not necessary to build the project (it may take 9 hours) but before launching CMake set build dir path as short as possible (I have build folder C:\S\b and the source C:\S\Slicer) because Slicer has some problems with path length and CMake will throw an error if build folder path is too long. I'm very interested in working on this project in QtCreator and not in Visual Studio but that QtCreator's behavior doesn't leave me any chances.

Thanks, I am distributing my source code via GitHub and GPL. I think that so long as I do that, it doesn't matter whether or not I use static linking in so far as licensing is concerned. My code is open-source, at least that's my intent. I did find that I was able to easily modify the makefile emitted by Qt Creator to force static linking of most, but not all of the Linux system dependencies. Apparently, some of the OS libraries were available only as shared libraries and in some cases Qt libraries called shared Linux OS libraries so that I was not able to use all the available static libraries offered by Linux. Too bad that it doesn't appear that one can roll up a desktop app all into one executable with no shared library calls. I'm thinking this would be nice since then, it could be distributed to any Linux machine without consideration of the distribution or kernel version? Thanks, Phil

@TUStudi said: I actually have 6 QLabels, so I now have 6 timer and so on Derive a class from QLabel and add that functionality to it. Don't write the same code 6 times! My QLabels have the sizePolicy horizontal: preferred and vertical: fixed and a vertical length of 20. When a text is displayed, the QLabel expands so that the elements above the QLabel are also moved upwards and after the text disappears, they go back to their initial place. Fixed size policy means that widget uses its sizeHint() as the size. If you change the text the size hint also changes, so label grows/shrinks.

It was my fault, the right .pro syntax is: QMAKE_CFLAGS_DEBUG += -Wno-cpp QMAKE_CXXFLAGS_DEBUG += -Wno-cpp The precedent syntax removes the -g gcc option from Makefile.

Hi @TUStudi, just to add that this problem is tracked as QTCREATORBUG-24561.

@kevinguo said in qtcreator and QT apps fail to launch in CentOS with root privilege: Hi: I am using CentOS 8.1. For some reason, I must run my app with root permission. I tried #sudo myapp or #sudo su #myapp Both failed with following output: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 No protocol specified qt.qpa.screen: QXcbConnection: Could not connect to display :1 Could not connect to any X display. Then I tried launching qtcreator, but failed with the same error. Please note that I am able to launch QT apps in Ubuntu 18.04 with root permission in the same way. Ubuntu outputs the following warning but continues to run the app: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 The failing platform is CentOS 8.1. The XWindows is wayland. Now, the workaround is to log in GUI with root user name. But I still prefer logging in as normal user then run app in sudo mode. I appreciate if anyone gives some advice. Kevin I found the solution already. Just run this: xhost +SI:localuser:root Thanks Kevin

@noone said in no "Initial CMake parameters" field in Qt creator: what should I do ? Update to 4.13 :-)

@TBRZ said in Fix for build error "member access into incomplete type 'const clang::FileEntry'": notify the developers about a problem This is user forum. If you want to communicate with developers you should either use bug tracker or the mailing list.

@Coop4Free said in Picking input from a LineEdit fails: long long decLabel; getData(decTokens); ServerNet serverNet; serverNet.sendData(decLabel); decLabel is an uninitialized variable. What else is there to say?

@Dariusz said in QtCreator - some basics questions...: maybe how to change initial type of file from QWidget to QDialog/etc/etc? If you mean how to change the .h, cpp and UI file to be other type ? You will have to change in 3 places .h class MainWindow : public QMainWindow <<< change here .cpp MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent) <<<< change here to new type .ui This you have to do outside creator, and its best if you close it. Open the ui file in other editor. ( its text)

I checked out the ratio of the main frame on the embedded system, which is the same as on my desktop. The fixed pixel width and height of the main window are exactly the same. The high dpi scaling attribute has no influence. Also switching from font.pixelSize to font.pointSize has the same unwanted effect. How can the font proportions turn out different? If the main windows height is defined as 1080px, a font size of 20px must be clearly defined relative to it (1/54 of the main window height). But why does it take, let's say, 24px on my embedded system (which is 1/45)? I can find many posts about scaling, but what I want is no automatic, random scaling at all.

Cleaning PATH variable and MSYS2 Environment solve that. I think that it might be caused by different version of some library that was used (because I had a lot of paths in the PATH), but for now it is over and I am happy with that.