Use of REC/RPL makes Capella 1.x/6.x/7.x buggy and unusable

Capella
1

Video showing the bug: https://www.youtube.com/watch?v=anB0WfH97Wo

Any interaction with REC/RPL menu (opening the menu to create a REC, instanciate an RPL or update a RPL from REC) will trigger this bug, which makes capella all buggy (ui elements becoming invisible, Activity Explorer throwing “Failed to create the part’s controls”, etc). The video doesn’t show, but when trying to interact with a diagram view, an error window keep appearing and interrupting workflow if I try to work despite the errors in log console and buggy ui.

This is happening on multiple 6.x and 7.x freshly downloaded Capella Versions, and even in 1.4, running both on Bluefin-dx 40 (based on Fedora Silverblue) natively on my machine and on a fresh Ubuntu 24.04 install on a virtual machine.

Github issue somehow related but unresolved since 2023: REC/REPL seems to be broken · Issue #2660 · eclipse-capella/capella · GitHub

Session Data:
eclipse.buildId=unknown
java.version=23.0.2 AND also java.version=17.0.14 (the one that comes w ith the capella download) AND also java 8 when running capella 1.4
java.vendor=Homebrew
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64

Compilation of some of the errors thrown: Hastebin

1 Like
2

I was not able to reproduce your problem from a blank Capella project.

3

Thanks for the response.

In which OS have you tried reproducing it?

I have now completely wiped out my laptop and freshly installed Windows 11 and Ubuntu 24.04. The problem does not occur on windows 11, but it still happens exactly the same in Ubuntu, with a new blank Capella Project.

I don’t have another hardware with me to test, just my laptop, but if this is not happening consistently on every linux machine, I’d guess this might be a problem with some hardware-specific driver for linux which surpasses even the isolation of a virtual machine… (?)

I have tried enabling and disabling my Nvidia MX 130 with PRIME profiles and tried xorg and wayland, and the bug persists.

1 Like
4

Indeed, I tried it on Windows 11. It is odd that such a problem would be OS dependent. But indeed the bug you pointed to seems relevant. I’ll raise it internally.

5

Thanks.

I’ve tried completely changing the display driver from NVIDIA to Nouveau, and the problem persists.

Since this might be hard to reproduce, I’m available for testing.