Missing Properties in ArmarX gui Scenario Manager; Components Fail to Start
Bug Report
Summary and Bug Description
On Ubuntu 22.04, many components cannot be started. For some components, the list of properties in the scenario manager is incomplete. The mongo db cache complains about missing xml files, although this seems not to be the cause of the problem.
Current Behavior
On Ubuntu 22.04, the scenario manager does not show all properties of a component in VisionX, and several applications (both in VisionX and in other modules) fail to start. Example of the latter:
[72628][09:51:56.984][ArmarXGui-1676278101182][Exec::Executor::asyncApplicationRestart(...)]: Starting application `DebugObserver` which is `/[...]/armarx/ArmarXCore/build/bin/DebugObserverRun`
[72629][09:51:57.822][ArmarXGui-1676278101182][std::cout]: Application RemoteGuiProviderApp is not running
[72629][09:51:58.822][ArmarXGui-1676278101182][std::cout]: Application RemoteGuiProviderApp is not running
Expected Behavior
The entries for all properties should be created. Components should start, or give a reason while they fail to start.
Steps to Reproduce
- Setup axii on Ubuntu 22.04
- Checkout the VisionX branch
feature/PlaybackImageProvider-remote-control
(derived fromfeature/ak-body-tracking-sdk
) - Build the workspace
- Try to start, e.g., the DebugObserver or the MemoryNameSystem via the scenario manager of an ArmarX gui
Diagnosis
Investigated with @kartmann. At least, an entry of coin in the LD_LIBRARY_PATH was incorrect. However, it seemed to be incorrect on his Ubuntu 18.04 system as well, without causing problems there. See merge request !512 (merged). After changing the path and restarting ArmarX etc., the problem at first still occurred (for multiple times), but vanished after some time. The reason is unclear. Currently, the problem is resolved.