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.
-
wrote on 12 Jul 2022, 19:03 last edited by
@SGaist said in 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.:
do you use the same backend ?
Same backend?? Can you tell me what backend is being asked about?
@SGaist said in 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.:
When starting directly on the BBB
Also I cannot directly start Qtcreator on BBB, since i don't have it installed on the BBB, and only use the cross-compilation on the ubuntu system to compile and deploy the app to the BBB (and nothing else)....don't know if that makes sense.
-
Backed: xcb, eglfs, etc.
No need for Qt Creator on your target, I meant literally starting your application on it, for example through the command line.
-
Backed: xcb, eglfs, etc.
No need for Qt Creator on your target, I meant literally starting your application on it, for example through the command line.
-
So it looks like your X server installation is incomplete to run Qt applications with the xcb backend. I would start by fixing that.
-
So it looks like your X server installation is incomplete to run Qt applications with the xcb backend. I would start by fixing that.
-
Can you help me with how to fix the incomplete X server installation? Or help provide some resource which can be helpful?
@Yash_r Install libxcb-xkb1 package on your target device
-
@jsulm
That package is already installed according to the apt-install as can be seen in the below image:
Also, when i try to run the app (as debian user) from the terminal, i get the following error:
@Yash_r Why do you start it with sudo?! By default starting GUI apps with sudo is not allowed for security reasons.
-
@Yash_r Why do you start it with sudo?! By default starting GUI apps with sudo is not allowed for security reasons.
-
It looks like a warning rather than an error per se.
You might have to configure something on the X server side.
26/26