Revision history [back]

I think this is caused if one of enabled plugins in rqt is waiting for a service that does not exist. (possibly because the required features are still a work in progress in ROS2?)

Resetting rqt with rqt --clear-config should disable all plugins and allow to reopen rqt in the usual way. This might be advantageous over deleting the whole configuration.

If the issue reappear after adding specific plugin, you know which plugin is causing this. (in my case rqt_tf_tree)