Details
-
Bug
-
Resolution: Invalid
-
P4: Low
-
None
-
5.15.7
-
DragonFly BSD, Mageia Linux
Description
I had to update my workstation after many years and had two minor issues. Yet I feel like I should report them, because qt is to me a serious development toolkit, used for countless applications, including KDE. So, I kind of expect it to be very professionnal, if I may say.
Both issues costed me a lot of time, because as I was building a new system and had to rebuild my applications on it. The issues lead me falsy to think that something was very bad with all of it.
I tested the first issue on both DragonFly BSD (FreeBSD in a sense) and Linux. The second one was tested only on DFBSD, but is trivial, so I'm very sure that its widespread too. Most systems won't have the issues, because they appear in abnormal situations.
First, when I start a qt application with the DISPLAY variable undefined, instead of having that clean behavior (xterm example here):
«xterm: Xt error: Can't open display:
xterm: DISPLAY is not set»
I always get that:
«qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: bsdfb, minimal, offscreen, vnc, webgl, xcb.
Abort (core dumped)»
The second issue, which was combined with the first one, was that I had to move my tmp folder and forgot to assign 1777 as folder permissions. As a result, any qt application that I started was hanging the X server, nothing less! You may say that the issue was the folder permissionw, but no other type of program was behaving that bad in the same situation. There is no excuse.
Otherwise, thanks for qt, which is nothetheless really a great toolkit.
Attachments
Issue Links
- duplicates
-
QTBUG-53003 QGuiApplication causes crash when there is no display available
-
- Closed
-