Archi fails to start on Ubuntu 22.04

[ldesousa]

Hi all,

I just downloaded Archi. When I run the bash script the splash screen appears for a split second and the programme seems to exit immediately. On the command the following message is printed:
```bash
WARNING: Using incubator modules: jdk.incubator.vector, jdk.incubator.foreign
```
And nothing else.

I understand Archi ships with its own JRE, but here is the version on my system:
```bash
$ java --version
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing)
```

Let me know if there is any other relevant information I could post. Thank you for reading.

[Phil Beauvoir]

Which version of Ubuntu are you using? Can you run in X11 mode?

This is one of those cases where you'll need to do more detective work to see if there are any error logs (look in the sub-directories of the ~/.archi directory) and narrow the problem.

[ldesousa]

Hi Phil, thank you for the reply. My answers to your questions below:

Which version of Ubuntu are you using? Can you run in X11 mode?

On my system I have Xorg 7.7 by default, not Wayland:

```bash
$ apt policy xorg
xorg:
  Installed: 1:7.7+23ubuntu2
  Candidate: 1:7.7+23ubuntu2
  Version table:
 *** 1:7.7+23ubuntu2 500
        500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
```

This is one of those cases where you'll need to do more detective work to see if there are any error logs (look in the sub-directories of the ~/.archi directory) and narrow the problem.

I searched for logs before posting to the forum, but could not find them. The folder you refer does not contain anything resembling (see below). Nothing in `/var/log` either. Is there any of directing the logs to the standard output? Thank you.

```bash
~/.archi$ tree
.
├── artifacts.xml
└── config
    ├── config.ini
    ├── org.eclipse.core.runtime
    ├── org.eclipse.e4.ui.css.swt.theme
    ├── org.eclipse.equinox.app
    ├── org.eclipse.osgi
    │   ├── 13
    │   │   └── 0
    │   ├── 130
    │   │   └── data
    │   │       └── 2077259261
    │   │           ├── artifacts.xml
    │   │           └── content.jar
    │   ├── 138
    │   │   └── data
    │   │       ├── cache.timestamps
    │   │       ├── listener_1925729951
    │   │       │   ├── artifacts.jar
    │   │       │   └── content.jar
    │   │       └── timestamps692698184
    │   ├── 150
    │   │   └── 0
    │   ├── 163
    │   │   └── 0
    │   ├── 174
    │   │   └── 0
    │   ├── 175
    │   │   └── 0
    │   ├── 179
    │   │   └── 0
    │   ├── 180
    │   │   └── 0
    │   ├── 25
    │   │   └── 0
    │   ├── 6
    │   │   └── 0
    │   ├── 7
    │   │   └── 0
    │   ├── 92
    │   │   └── 0
    │   ├── 93
    │   │   └── 0
    │   ├── 94
    │   │   └── 0
    │   └── framework.info.1
    ├── org.eclipse.update
    │   └── platform.xml
    └── p2
        ├── org.eclipse.equinox.p2.core
        │   └── cache
        │       └── artifacts.xml
        └── org.eclipse.equinox.p2.engine
            └── profileRegistry
                └── DefaultProfile.profile
                    ├── 1705572281682.profile.gz
                    ├── 1705572282251.profile.gz
                    └── state.properties

44 directories, 14 files
```

[Phil Beauvoir]

Take a look in ~/.archi/.metadata (hidden folder) and look for .log file

[ldesousa]

Take a look in ~/.archi/.metadata (hidden folder) and look for .log file

Nothing in there.

```bash
$ ls -la ~/.archi/.metadata
total 20
drwxrwxr-x 3 user user 4096 jan 18 11:04 .
drwxrwxr-x 4 user user 4096 jan 18 11:04 ..
-rw-rw-r-- 1 user user    0 jan 18 11:04 .lock
drwxrwxr-x 4 user user 4096 jan 18 11:04 .plugins

$ find . -name "*.log"
$
$ find . -name ".*.log"
$
```

[Phil Beauvoir]

Sorry, I don't know what else to suggest as I don't have access to your machine or setup. I've tested Archi on Ubuntu 23.04, and no-one else has reported the problem. Maybe try a fresh download, or on another Linux setup? Did you try launching by double-clicking the "Archi" executable (not the Archi.sh script)?

[ldesousa]

Hello again,

a quick update on this issue. Eventually I understood that under certain circumstances Archi was able to start and function correctly, especially right after a system reboot. But at some point Archi starts freezing. It happen in two ways:
- The splash screen shows up for a few seconds and the programme immediately freezes, without ever starting the GUI.
- The programme starts and the GUI is portrayed, but the programme freezes once the Open menu is accessed.

In the end it all comes down to network volumes. As soon as I mount one of those Archi no longer functions, yielding the behaviour above. I mount those volumes with `sshfs`, if that is relevant. Easy to solve, as a rule I do not need access to network volumes to work with Archi. But what is exactly happening here? Is Archi trying to access mounted volumes somehow?

I hope this helps improving the software. Regards.

[Phil Beauvoir]

Archi is not doing anything special with network volumes, unless you've set a preference somewhere to access data on a volume. As Archi is built on the Eclipse platform, you'd likely see the same behaviour if you used the Eclipse IDE.