Skip to content

Conversation

@v4hn
Copy link
Contributor

@v4hn v4hn commented Jul 8, 2025

When running on wayland with Ogre without wayland support, explicitly force Qt to use the XCB protocol running through Xwayland.

Backported with adaptations from ros2/rviz#847 .

@rhaschke as discussed in person.
Tested on Debian trixie to run under X11 as well as wayland.

Copy link
Contributor

@rhaschke rhaschke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR. I need to look into CI. Looks like OSRF broke Noetic by removing the urdf package key ☹️

@simonschmeisser
Copy link
Contributor

What version of ogre are you using? From Debian package? Maybe wayland support can be enabled?

When running on wayland with Ogre without wayland support,
explicitly force Qt to use the XCB protocol running
through Xwayland.

Backported with adaptations from ros2/rviz#847 .
@v4hn v4hn force-pushed the pr-wayland-xcb-fallback branch from 2117c32 to 0b23861 Compare August 4, 2025 12:20
@v4hn
Copy link
Contributor Author

v4hn commented Aug 4, 2025

Hi Simon, great to hear from you!

What version of ogre are you using? From Debian package?

Yes, the native packages from Debian bookworm/trixie.
Of course I could build ogre myself with adapted features, and that might work.
But I'm mostly interested in the out-of-the-box ROS-O experience, and the default build (also on the buildfarms) results in an RViz that will fail to start on any wayland installation (which is the default for a while already!).

@rhaschke

  • the jammy builds seem do break due to invalid repository signatures key configs.
  • for noetic, "urdf" cannot be resolved, but that's a regular package. The problem might only be that rosdep rejects eol distributions by default, but has an additional flag to include them.

Personally, I'm also fine with moving this (and any future) PR to a new ros-o branch. What do you think?

@rhaschke
Copy link
Contributor

rhaschke commented Aug 4, 2025

I didn't have time to look into the (general) build issues yet. Just returned from holidays...
Going for a ros-o branch seems to be the right choice if those Noetic build issues cannot be resolved.

@simonschmeisser
Copy link
Contributor

Wayland support was actually only added super recently in 14.something in Ogre so this workaround will likely be needed forever

@rhaschke rhaschke changed the base branch from noetic-devel to main August 7, 2025 22:25
@rhaschke rhaschke merged commit b62f00d into ros-visualization:main Aug 8, 2025
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants