Barrier Server is Ubuntu 22.04, service won't start, stuck at "Barrier is Starting"

[surfrock66]

What happened?

Barrier, when installed via snap or repo package on Ubuntu 22.04, will not start. It gets stuck at "Barrier is Starting." I never got far enough to try to connect a client to it.

This is a fairly standard system running X with nvidia drivers and 4 screens, USB keyboard and mouse. I got the same result starting barrier as my regular user and as a root user.

Looking at the debug logs, I'm worried it's a screen configuration thing, but I can't validate further.

I have been through the steps in the following past issues to no avail:
#181
#480

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Ubuntu repository, Ubuntu 22.04

What OSes are you seeing the problem on? (Check all that apply)

Linux

What OS versions are you using?

Ubuntu 22.04

Relevant log output

Log from the application (Debug Level):

[2022-07-29T11:00:09] INFO: starting server
[2022-07-29T11:00:09] DEBUG: command: /usr/bin/barriers -f --no-tray --debug DEBUG --name HOSTNAME --disable-client-cert-checking -c /tmp/Barrier.vxjGet --address :24800
[2022-07-29T11:00:09] INFO: config file: /tmp/Barrier.HLarXW
[2022-07-29T11:00:09] INFO: log level: DEBUG
[2022-07-29T11:00:09] DEBUG: opening configuration "/tmp/Barrier.vxjGet"
[2022-07-29T11:00:09] DEBUG: configuration read successfully
[2022-07-29T11:00:09] DEBUG: XOpenDisplay(":0")
[2022-07-29T11:00:09] DEBUG: xscreensaver window: 0x00000000
[2022-07-29T11:00:09] DEBUG: screen shape: 0,0 3840x2160 (xinerama)
[2022-07-29T11:00:09] DEBUG: window is 0x09200004
[2022-07-29T11:00:09] DEBUG: adopting new buffer
[2022-07-29T11:00:09] DEBUG: opened display
[2022-07-29T11:00:09] ERROR: process exited with error code: 11
[2022-07-29T11:00:09] INFO: detected process not running, auto restarting

Relevant syslog during the run, this is looping:

Jul 29 10:54:07 HOSTNAME kernel: [ 1346.118289] barriers[13198]: segfault at 1c4f1 ip 000000000001c4f1 sp 00007ffe83a75ff8 error 14 in barriers[559237a05000+16000]
Jul 29 10:54:07 HOSTNAME kernel: [ 1346.118300] Code: Unable to access opcode bytes at RIP 0x1c4c7.

Any other information

Screen info, as I suspect that's the issue here:

# xrandr --listmonitors
Monitors: 4
 0: +*HDMI-0 1920/521x1080/293+0+1080  HDMI-0
 1: +DP-1 1920/521x1080/293+1920+1080  DP-1
 2: +DP-3 1920/477x1080/268+1920+0  DP-3
 3: +DP-5 1920/477x1080/268+0+0  DP-5

# lshw -c video
  *-display                 
       description: VGA compatible controller
       product: TU104 [GeForce RTX 2070 SUPER]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:09:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:120 memory:fb000000-fbffffff memory:d0000000-dfffffff memory:e0000000-e1ffffff ioport:e000(size=128) memory:c0000-dffff
  *-graphics
       product: EFI VGA
       physical id: 1
       logical name: /dev/fb0
       capabilities: fb
       configuration: depth=32 resolution=1024,768

# glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 8192 MB
    Currently available dedicated video memory: 6983 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.129.06
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 470.129.06
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 470.129.06
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

[surfrock66]

Solved, screen was a red herring, this comment was the answer: #1283 (comment)