-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qt platform error on yarpmanager #1568
Comments
I am not really familiar with that functionality of the clusterwidget. Just to understand, are you able to run |
Not familiar with this error. Maybe some apt get install libxcb (or similar) is missing? Check these as well:
|
@lindalastrico any update on your issue? |
@randaz81 not yet. I haven’t had the chance to access the lab pc to test it again! I will update you on Thursday, thank you! |
Hello @randaz81, @traversaro |
Can you run via manger a non-qt, non-yarp GUI? For example gedit, which should be based on GTK |
No! On the terminal it says: |
To debug further the problem, can you try to launch |
Hello,
We are using the latest superbuild stable release with yarp 3.8.1 on Ubuntu 22.04.
When launching yarpmanager, we face this warning:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Yarpmanager works fine anyway, except when trying to launch a command from the GUI:
While the Yarpmanager GUI reports "command successfully executed on... ", the command is not actually executed and there is the following error in the yarpmanager terminal:
t.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: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
It looks like a Qt issue, what do you suggest?
Thank you!
The text was updated successfully, but these errors were encountered: