When you say "screens", do you mean the alternate command-line-output that doesn't have to be actively displayed on a graphical desktop? Such as is typically used for direwolf, a "headless" command-line app that reports its log data to standard output?

If so, that is why "screens" won't work with YAAC. YAAC is a graphical app that must be displayed on a graphical desktop, not in a command-line-only environment. The only information that YAAC writes to command-line standard output is debug and error log data which is also copied to a rolling disk file. And "screens" doesn't tell the apps hosted in it where its desktop is (because screens doesn't know, and may not even have a desktop at any given time).

Now, if you are trying run the graphical displays of YAAC in a virtual desktop (such as a VNC remote desktop), when you launch YAAC, you need to tell it which desktop to use for its displays. On Linux and other Unix derivatives, this is done with the DISPLAY environment variable, whose value defines the X Windows address of the X server (screen server) to use. Graphical desktops and terminal windows upon such a desktop inherit the desktop's setting of this environment variable. For security reasons, X servers do not by default allow access from apps not launched from their desktops, so you may have to not only define the DISPLAY environment variable correctly, but also use the xhost command to authorize non-desktop app processes to access the screens of the desktop.

If your system is using Wayland instead of X, the desktop is deliberately not remotely accessible. You will have to either switch from Wayland back to X, or find an X server emulator for Wayland that will provide the off-system access capabilities of X.

Hope this explains why your attempts aren't working.

Andrew, KA2DDO

author of YAAC

---

[Edited Message Follows]