Opened 4 years ago

Closed 3 years ago

Last modified 2 years ago

#834 closed issue (handled)

Crash when starting ARB

Reported by: guest Owned by: devel
Priority: normal Milestone:
Component: no idea Version:
Keywords: crash start error1 Cc:

Description (last modified by westram)

Hello,

I've been trying to install ARB this morning and keep getting this error. I've tried the Macport and homewbrew methods of installation, but both give the same error.

(base) MACP80253:~ u1993000$ arb
Ignoring set ARBHOME '/opt/local/share/arb' (overridden by explicit call of '/opt/local/bin/arb')
Using ARBHOME='/opt/local/share/arb'
Using properties from /Users/u1993000/.arb_prop
Please wait while the program ARB is starting .....
Waiting for '/Users/u1993000/.arb_tmp/sockets/arb_launcher.76876'..
[arb_launcher[0]: Starting 'arb_ntree'..]
Using properties from '/opt/local/share/arb/lib/arb_default/ntree.arb'
Using properties from '/opt/local/share/arb/lib/arb_default/status.arb'
Error: Can't open display: :0
ARB: Loading 'ntree.arb'
ARB: Loading '/opt/local/share/arb/lib/arb_default/ntree.arb' done

Error: Can't open display: :0
[arb_launcher[0]: 'arb_ntree' has terminated with error 1]
[arb_launcher[0]: Still have 1 arb processes..]
[arb_launcher[0]: All launched processes terminated]

Session log has been stored in /Users/u1993000/.arb_prop/logs/session.20201123_131203.76880.tgz
    and is also accessible via /Users/u1993000/ARB_last_session.tgz

ARB terminated abnormally
[press ENTER]

Looking at previous bug tickets there seems to be a crash when they have already loaded data, which I haven't gotten to the GUI to do. When I try another install using Macport, it gives me this output.

(base) MACP80253:~ u1993000$ sudo port install arb
Password:
--->  Computing dependencies for arb
--->  Cleaning arb
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.

I am running MacOS Catalina 10.15.7.

Thanks and stay safe!

Change History (3)

comment:1 in reply to: ↑ description Changed 4 years ago by westram

Replying to guest:

Error: Can't open display: :0

This is not an ARB-specific problem. I think there is a general problem with your X11 server installation and/or configuration.

You should run into the same problem when e.g. trying to start a terminal using the command

xterm

When you fixed the problem for xterm, arb will most likely run as well.

We currently recommend the homebrew version of arb. So you might want to switch back..

comment:2 Changed 3 years ago by westram

  • Resolution set to handled
  • Status changed from new to closed
  • Type changed from defect to issue

comment:3 Changed 2 years ago by westram

  • Cc Nello.Gregori@… removed
  • Description modified (diff)

Similar problems often occur when installing arb via homebrew.

Example error message:

Using ARBHOME='/usr/local/Cellar/arb@7/7.0.1'
Using properties from /Users/macbook/.arb_prop
Please wait while the program ARB is starting .....
Waiting for '/Users/macbook/.arb_tmp/sockets/arb_launcher.26273'..
2022?? 6??10?? ?????? 10??01??55?? CST arb server.log created by arb_launcher
[arb_launcher[0]: log for ARB_PID='26273']
[arb_launcher[0]: Starting 'arb_ntree'..]
Using properties from '/usr/local/Cellar/arb@7/7.0.1/lib/arb_default/status.arb'
Using properties from '/usr/local/Cellar/arb@7/7.0.1/lib/arb_default/ntree.arb'
Error: Can't open display: :0
Error: Can't open display: :0
ARB: Loading 'ntree.arb'
ARB: Loading '/usr/local/Cellar/arb@7/7.0.1/lib/arb_default/ntree.arb' done

[arb_launcher[0]: 'arb_ntree' has terminated with error 1]
[arb_launcher[0]: Still have 1 arb processes..]
[arb_launcher[0]: All launched processes terminated]
[arb_launcher[0]: cleaning up arb session]
  PID TTY           TIME CMD
rmdir: /Users/macbook/.arb_prop/logs/20220610_100155.26289: Directory not empty

Session log has been stored in /Users/macbook/.arb_prop/logs/session.20220610_100155.26289.tgz
    and is also accessible via /Users/macbook/ARB_last_session.tgz

ARB terminated abnormally
[press ENTER]

The problem is not arb specific: your X display does not work. You will get the same error when you start any other X program.

Your problem is similar to https://stackoverflow.com/questions/37826094/xt-error-cant-open-display-if-using-default-display

There the problem had been fixed by rebooting.


If the problem persist after reboot, please send the output of the following commands to arb@…:

xterm

echo $DISPLAY

Note: See TracTickets for help on using tickets.