Open headbank opened 3 years ago
I found what appears to be the root of the issue with TigerVNC. It now depends on a systemd session scope. I assume this is something that just hasn't hit Debian yet.
I would close this, but I suspect this is also why it's not possible to launch an Arch/VNC session from the UI. If so, a solution or an advisory might be in order.
Describe the bug
I wanted to launch tigervnc vncserver from within an Arch/SSH session (I've been able to do this in UserLAnd Debian) but something is amiss with the vncserver perl script I think, as any attempted command, for example
vncserver -geometry 1920x1080 -securitytypes none
(which is sufficient to launch Xtigervnc in Debian) returns only
Usage: vncserver <display>
In addition I was unable to launch the Arch install as a VNC session from the UserLAnd UI either - the process hung on "starting session..."
This is with a new-installed Arch filesystem and session, which I have only added
pacman -Syu
andpacman -S fluxbox
Steps to reproduce the behavior:
su -; pacman -Syu; pacman -S fluxbox
vncserver -geometry 1920x1080 -securitytypes none
Screenshots
N/A
Device Information
Device: Samsung Galaxy S10 5G.
Android Version: 10/Q.
UserLAnd Version: Latest from Play Store (sorry, no idea how to find version number).
Whether the device is rooted. NO Whether the device is running LineageOS (NO)