qt tools freeze on startup
-
I can't start qt creator (version 13.0.2). I've noticed that I can start, but not open .ui files, using designer 6.7.2 (but have no problems with 5.15.14). This is a fairly recent problem...
I'm running gentoo linux with qt 6.7.2 and 5.15.14 both installed. My project is using 6.7.2, but given I can't use designer or creator, now that I'm making UI files I'm being forced to use designer 5, which is sub-optimal. I'd also like to use creator, as it's actually capable of peeking at Qt variable names while CLion is not currently working for that purpose.
Running qtcreator with QT_DEBUG_PLUGINS=1 gives many thousands of lines of output (which apparently cannot be redirected to a file as it is neither stdout nor stderr, so 2>&1 >/some/file does not work)... but here's the last bit if that helps anyone try to debug this mess:
qt.core.plugin.factoryloader: Got keys from plugin meta data QList("QMYSQL", "QMARIADB") qt.core.plugin.factoryloader: checking directory path "/usr/bin/sqldrivers" ... qt.core.library: "/usr/lib64/qt6/plugins/sqldrivers/libqsqlite.so" loaded library qt.core.plugin.factoryloader: checking directory path "/usr/lib64/qt6/plugins/wayland-decoration-client" ... qt.core.plugin.factoryloader: looking at "/usr/lib64/qt6/plugins/wayland-decoration-client/libbradient.so" qt.core.plugin.loader: Found metadata in lib /usr/lib64/qt6/plugins/wayland-decoration-client/libbradient.so, metadata= { "IID": "org.qt-project.Qt.WaylandClient.QWaylandDecorationFactoryInterface.5.4", "MetaData": { "Keys": [ "bradient" ] }, "archlevel": 3, "className": "QWaylandBradientDecorationPlugin", "debug": false, "version": 395008 } qt.core.plugin.factoryloader: Got keys from plugin meta data QList("bradient") qt.core.plugin.factoryloader: checking directory path "/usr/bin/wayland-decoration-client" ... qt.core.library: "/usr/lib64/qt6/plugins/wayland-decoration-client/libbradient.so" loaded library
Any hints on how to get a functional environment again?
-
I can't start qt creator (version 13.0.2). I've noticed that I can start, but not open .ui files, using designer 6.7.2 (but have no problems with 5.15.14). This is a fairly recent problem...
I'm running gentoo linux with qt 6.7.2 and 5.15.14 both installed. My project is using 6.7.2, but given I can't use designer or creator, now that I'm making UI files I'm being forced to use designer 5, which is sub-optimal. I'd also like to use creator, as it's actually capable of peeking at Qt variable names while CLion is not currently working for that purpose.
Running qtcreator with QT_DEBUG_PLUGINS=1 gives many thousands of lines of output (which apparently cannot be redirected to a file as it is neither stdout nor stderr, so 2>&1 >/some/file does not work)... but here's the last bit if that helps anyone try to debug this mess:
qt.core.plugin.factoryloader: Got keys from plugin meta data QList("QMYSQL", "QMARIADB") qt.core.plugin.factoryloader: checking directory path "/usr/bin/sqldrivers" ... qt.core.library: "/usr/lib64/qt6/plugins/sqldrivers/libqsqlite.so" loaded library qt.core.plugin.factoryloader: checking directory path "/usr/lib64/qt6/plugins/wayland-decoration-client" ... qt.core.plugin.factoryloader: looking at "/usr/lib64/qt6/plugins/wayland-decoration-client/libbradient.so" qt.core.plugin.loader: Found metadata in lib /usr/lib64/qt6/plugins/wayland-decoration-client/libbradient.so, metadata= { "IID": "org.qt-project.Qt.WaylandClient.QWaylandDecorationFactoryInterface.5.4", "MetaData": { "Keys": [ "bradient" ] }, "archlevel": 3, "className": "QWaylandBradientDecorationPlugin", "debug": false, "version": 395008 } qt.core.plugin.factoryloader: Got keys from plugin meta data QList("bradient") qt.core.plugin.factoryloader: checking directory path "/usr/bin/wayland-decoration-client" ... qt.core.library: "/usr/lib64/qt6/plugins/wayland-decoration-client/libbradient.so" loaded library
Any hints on how to get a functional environment again?
@kshots said in qt tools freeze on startup:
Running qtcreator with QT_DEBUG_PLUGINS=1 gives many thousands of lines of output (which apparently cannot be redirected to a file as it is neither stdout nor stderr, so 2>&1 >/some/file does not work)..
You have your redirections back-to-front. Reading left-to-right you need to send stdout somewhere and then redirect stderr to the same place:
chrisw@newton:/tmp$ QT_DEBUG_PLUGINS=1 ~/Qt/Tools/QtCreator/bin/qtcreator > debug.txt 2>&1 chrisw@newton:/tmp$ ls -l debug.txt -rw-rw-r-- 1 chrisw chrisw 251763 Jun 22 14:39 debug.txt
(Or just redirect stderr alone in this case)
Are you using a Wayland or X11 session in Gentoo?
-
@kshots said in qt tools freeze on startup:
Running qtcreator with QT_DEBUG_PLUGINS=1 gives many thousands of lines of output (which apparently cannot be redirected to a file as it is neither stdout nor stderr, so 2>&1 >/some/file does not work)..
You have your redirections back-to-front. Reading left-to-right you need to send stdout somewhere and then redirect stderr to the same place:
chrisw@newton:/tmp$ QT_DEBUG_PLUGINS=1 ~/Qt/Tools/QtCreator/bin/qtcreator > debug.txt 2>&1 chrisw@newton:/tmp$ ls -l debug.txt -rw-rw-r-- 1 chrisw chrisw 251763 Jun 22 14:39 debug.txt
(Or just redirect stderr alone in this case)
Are you using a Wayland or X11 session in Gentoo?
@ChrisW67 said in qt tools freeze on startup:
Reading left-to-right you need to send stdout somewhere and then redirect stderr to the same place:
You learn something new every day! In all my years of using UNIX I thought
2>&1 >file
would work, I thought it would connect #2 to "logical" #1 and then #1 to file, taking #2 with it....so 2>&1 >/some/file does not work
Assuming you are using bash (or csh), it's simpler to type and you don't have to worry about order if you use:
command >& file command |& less
:)
-
@kshots said in qt tools freeze on startup:
Running qtcreator with QT_DEBUG_PLUGINS=1 gives many thousands of lines of output (which apparently cannot be redirected to a file as it is neither stdout nor stderr, so 2>&1 >/some/file does not work)..
You have your redirections back-to-front. Reading left-to-right you need to send stdout somewhere and then redirect stderr to the same place:
chrisw@newton:/tmp$ QT_DEBUG_PLUGINS=1 ~/Qt/Tools/QtCreator/bin/qtcreator > debug.txt 2>&1 chrisw@newton:/tmp$ ls -l debug.txt -rw-rw-r-- 1 chrisw chrisw 251763 Jun 22 14:39 debug.txt
(Or just redirect stderr alone in this case)
Are you using a Wayland or X11 session in Gentoo?
@ChrisW67 said in qt tools freeze on startup:
@kshots said in qt tools freeze on startup:
Running qtcreator with QT_DEBUG_PLUGINS=1 gives many thousands of lines of output (which apparently cannot be redirected to a file as it is neither stdout nor stderr, so 2>&1 >/some/file does not work)..
You have your redirections back-to-front. Reading left-to-right you need to send stdout somewhere and then redirect stderr to the same place:
chrisw@newton:/tmp$ QT_DEBUG_PLUGINS=1 ~/Qt/Tools/QtCreator/bin/qtcreator > debug.txt 2>&1 chrisw@newton:/tmp$ ls -l debug.txt -rw-rw-r-- 1 chrisw chrisw 251763 Jun 22 14:39 debug.txt
(Or just redirect stderr alone in this case)
Are you using a Wayland or X11 session in Gentoo?
Huh - I always thought that was the order. Evidently not - thanks for the suggestion. Here's a pastebin of the full output.
I'm using Wayland under gentoo at the moment.
-
@ChrisW67 said in qt tools freeze on startup:
@kshots said in qt tools freeze on startup:
Running qtcreator with QT_DEBUG_PLUGINS=1 gives many thousands of lines of output (which apparently cannot be redirected to a file as it is neither stdout nor stderr, so 2>&1 >/some/file does not work)..
You have your redirections back-to-front. Reading left-to-right you need to send stdout somewhere and then redirect stderr to the same place:
chrisw@newton:/tmp$ QT_DEBUG_PLUGINS=1 ~/Qt/Tools/QtCreator/bin/qtcreator > debug.txt 2>&1 chrisw@newton:/tmp$ ls -l debug.txt -rw-rw-r-- 1 chrisw chrisw 251763 Jun 22 14:39 debug.txt
(Or just redirect stderr alone in this case)
Are you using a Wayland or X11 session in Gentoo?
Huh - I always thought that was the order. Evidently not - thanks for the suggestion. Here's a pastebin of the full output.
I'm using Wayland under gentoo at the moment.
-
How does Qt Creator 13.0.2 from https://download.qt.io/official_releases/qtcreator/13.0/ work?