komorebi is not starting

[potterbl]

UBUNTU 22.04

potter@potter:/System/Applications$ sudo ./komorebi
[sudo] пароль для potter:
Welcome to Komorebi

** (process:19698): CRITICAL **: 01:24:35.935: string_contains: assertion 'self != NULL' failed
No configuration file found. Creating one..
[INFO]: loading Gst

** (komorebi:19698): CRITICAL **: 01:24:36.437: file /home/potter/komorebi/build/src/OnScreen/DesktopIcons.c: line 426: uncaught error: Error opening directory '/root/Desktop': Нет такого файла или каталога (g-io-error-quark, 1)

(komorebi:19698): Gdk-ERROR **: 01:24:37.600: The program 'komorebi' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadDrawable'.
(Details: serial 1069 error_code 160 request_code 152 (GLX) minor_code 29)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Ловушка трассировки/останова

or

potter@potter:/System/Applications$ ./komorebi
Welcome to Komorebi
Reading config file..
[INFO]: loading Gst

(komorebi:19630): Gdk-ERROR **: 01:24:28.699: The program 'komorebi' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadDrawable'.
(Details: serial 1102 error_code 160 request_code 152 (GLX) minor_code 29)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Ловушка трассировки/останова (образ памяти сброшен на диск)

[SakuraBlossomTree]

Same error here don't know what is going on

[carlos-kennedy]

Same error..

[kapoor-codes]

The issue might persist because of the multi monitor setup. Try disconnecting the monitor and install again.