@Axel-Spoerl Thank you for your answer

Hi, A missing SQL plugin should not crash your application unless you do some strange things. At best your queries will fail because no connection can be established. However, running your application as root might explain. By default recent Linux distributions forbid running GUI application as root user.

It was in typing the original question that I thought "what does QtCreator do"? - and got the command line from there

@JackMyson You don't actually show the message box being shown (exec()?). Nothing special here. Try not subclassing the QMessageBox and using that directly, so you can rule that out. Try a standalone application without anything of your own. Try passing nullptr as parent to the constructor, any difference? Are you sure you are not using Wayland rather than Xorg, that might make its position or behaviour different.

I had the same problem upgrading from 6.6 to 6.7, I resolved it by using the correct NDK (26.1.10909125), see https://doc.qt.io/qt-6/android-getting-started.html

@Basile_Starynkevitch I don't know what your command is or how you are presently sending it to QProcess as you do not show these. You can normally leave the correct quoting to QProcess with an argument list. If, for some reason, you have a string and want to split it into arguments for QProcess you can use QStringList QProcess::splitCommand(QStringView command). Also void QProcess::startCommand(const QString &command, QIODeviceBase::OpenMode mode = ReadWrite) presumably uses that internally. Note however that you reference https://docs.gtk.org/glib/func.shell_quote.html and that says Quotes a string so that the shell (/bin/sh) will interpret the quoted string to mean unquoted_string. Quoting to a shell like /bin/sh can have its own rules. For example, echo '$HOME' and echo "$HOME" behave differently. I don't know how/whether you deal with that. And your GLib shell_quote ignores this.

OP's Ubuntu should support stat file for Birth. See e.g. How to Find Out When a File Was Created in Linux for a recent discussion of the issues.

@rsmwall hi and welcome to devnet, Did you already check the projects I linked (agreed they are non trivial) ? Do you really intend to create a new DE or do you just need something more fancy than a single window application in which case the Qt Wayland module might be of interest.

@Yash001 this is just general advice. on linux, to run commands as part of the installation is usually handled by postinst.src if deb based, or under %dir section (.spec file) if centos based distro, which are part of respective .rpm or .deb files.

One possible alternative could be to use a Docker container to build your application with a suitably old Ubuntu or maybe a VM which would be even simpler,

@jsulm I finally found my mistake, I'm missing the install qtspeech5-flite-plugin Thank you

I am also facing the same issue. Have you found any solution for this?

@Imeshsps This issue does not seem to come with qt-everywhere-src-6.5.0-rc. I was able to succesfully compile it.

@amrhus There are a lot of question with exactly your problem. Please use the search function and search for "Could not load the Qt platform plugin "xcb" in "" even though it was found.".

@laozeng1982 Write a one program which just creates a QWIdget and show()s it before app.exec(). Try that. Find out whether no Qt program runs or whether it's something in your actual application.

@jsulm void MainWindow::on_pushButton_clicked() { TestDialog *test = new TestDialog (); test->setAttribute(Qt::WA_DeleteOnClose); test->show(); } #include "testdialog.h" #include "ui_testdialog.h" TestDialog::TestDialog(QWidget *parent) : QDialog(parent), ui(new Ui::TestDialog) { ui->setupUi(this); connect(ui->pushButton_2,&QPushButton::clicked,this,&TestDialog::pushButton_2_clicked); } TestDialog::~TestDialog() { delete ui; } void TestDialog::closeEvent(QCloseEvent *event) { event->accept(); } void TestDialog::pushButton_2_clicked() { this->close(); } Does qt have requirements for computers? Computers with high configuration will not get stuck.

@jsulm @sierdzio Thank you both so much. I will try that out.