You are not logged in.
I recently switched from Manjaro to Arch Linux. I had a separate /home partition, so it was relatively easy. On Manjaro, I had x11vnc installed, and debtapped TurboVNC from the release debian file. Both worked through both native clients and noVNC. However, when I installed TurboVNC and x11vnc on Arch, different patterns happened.
With x11vnc, I could connect to it once. However, sometimes once I connected to it, if I disconnected and tried to connect to it again, I got an infinite "Connecting..." sign. If I terminated the x11vnc server, it would finally give a connection failure. I have tested this to the same results with TigerVNC's vncviewer and noVNC. And sometimes, the server died after the first connection with "Assertion `!xcb_xlib_threads_sequence_lost' failed."
With TurboVNC, I got the infinite "Connecting..." on the first try. When I terminated that, it gave me a connection failure. The vncserver -kill :1 option TurboVNC has didn't work, saying it could not terminate it and asking me to manually kill the process and then restart. This was tested with both the official TurboVNC viewer and noVNC.
To be clear, all of this worked with the exact same configuration files on Manjaro.
I have virtualgl and turbojpeg installed.
My x11vnc script -
x11vnc -extra_fbur 10 -wait 1 -defer 1 -repeat -usepw -threads -forever -solid -speeds ,10,100 -onetile -xwarppointer -xd_area 2073600
My TurboVNC script -
/opt/TurboVNC/bin/vncserver -kill :1
/opt/TurboVNC/bin/vncserver :1 -alr 0.1 -alrqual 10 -alrsamp 4x -economictranslate -interframe -vgl -wm startlxde
~/.vnc/xstartup.turbovnc
exec startlxde
A TurboVNC log -
TurboVNC Server (Xvnc) 64-bit v2.2.6 (build 20210221)
Copyright (C) 1999-2021 The VirtualGL Project and many others (see README.txt)
Visit http://www.TurboVNC.org for more information on TurboVNC
07/04/2021 07:47:56 Using security configuration file /etc/turbovncserver-security.conf
07/04/2021 07:47:56 Enabled security type 'tlsvnc'
07/04/2021 07:47:56 Enabled security type 'tlsotp'
07/04/2021 07:47:56 Enabled security type 'tlsplain'
07/04/2021 07:47:56 Enabled security type 'x509vnc'
07/04/2021 07:47:56 Enabled security type 'x509otp'
07/04/2021 07:47:56 Enabled security type 'x509plain'
07/04/2021 07:47:56 Enabled security type 'vnc'
07/04/2021 07:47:56 Enabled security type 'otp'
07/04/2021 07:47:56 Enabled security type 'unixlogin'
07/04/2021 07:47:56 Enabled security type 'plain'
07/04/2021 07:47:56 Desktop name 'TurboVNC: vaughan-hppavilion:1 (vaughanm)' (vaughan-hppavilion:1)
07/04/2021 07:47:56 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
07/04/2021 07:47:56 Listening for VNC connections on TCP port 5901
07/04/2021 07:47:56 Interface 0.0.0.0
07/04/2021 07:47:56 Listening for HTTP connections on TCP port 5801
07/04/2021 07:47:56 URL http://vaughan-hppavilion:5801
07/04/2021 07:47:56 Interface 0.0.0.0
07/04/2021 07:47:56 Framebuffer: BGRX 8/8/8/8
07/04/2021 07:47:56 New desktop size: 1240 x 900
07/04/2021 07:47:56 New screen layout:
07/04/2021 07:47:56 0x00000040 (output 0x00000040): 1240x900+0+0
07/04/2021 07:47:56 Maximum clipboard transfer size: 1048576 bytes
07/04/2021 07:47:56 VNC extension running!
Xlib: request 55 length 16 would exceed buffer size.
(EE) Segmentation fault at address 0x8
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
** Message: 07:47:57.121: main.vala:102: Session is LXDE
** Message: 07:47:57.121: main.vala:103: DE is LXDE
(lxsession:1051): Gtk-WARNING **: 07:47:57.123: cannot open display: vaughan-hppavilion:1
** Note after initial testing -
During further testing, my window manager disappears, only my background image is visible, two identical scripts have different results, and my screen becomes blue.
The other script for x11vnc resulting in this -
x11vnc -extra_fbur 10 -wait 1 -defer 1 -repeat -usepw -threads -forever -solid -speeds ,10,100 -onetile -xwarppointer -xd_area 2073600;
sleep 1;
$0
Anyway, I have no idea at all what is going on. The error messages change every time, and given the exact same circumstance it does something different. Is this a simple config change, a package that's not installed, or something fundamentally wrong on a very deep level with my computer?
** UPDATE
Running x11vnc with just x11vnc -nodpms -forever -usepw works perfectly.
Last edited by zeroxoneafour (2021-04-28 20:30:11)
Offline
This is no longer a problem for some reason. No idea why. Guess I just had to "break the system in".
Offline