Open madduck opened 2 years ago
Describe the bug
x11vnc exits shortly after a client connects, which only gets to briefly show the desktop. If I remove -ncache …, then the connection stays.
-ncache …
To Reproduce
ssh -L 5930:localhost:5900 desktop -X "pkill x11vnc && x11vnc -display :0 -nopw -localhost -ncache 10 -gone 'xscreensaver-command -lock'"
ssvnc
remmina
localhost:5930
Log data below. I have also tried with -norepeat but it made no difference.
-norepeat
If I remove -ncache …, it works as expected
Expected Behavior
Well, I expect the session to prevail, and be able to use -ncache 10.
-ncache 10
Desktop (please complete the following information):
Additional context
Here is the x11vnc output:
x11vnc
14/07/2022 13:05:12 Got connection from client ::1 14/07/2022 13:05:12 0 other clients 14/07/2022 13:05:12 Normal socket connection 14/07/2022 13:05:12 check_access: client addr ::1 is local. 14/07/2022 13:05:12 Disabled X server key autorepeat. 14/07/2022 13:05:12 to force back on run: 'xset r on' (3 times) 14/07/2022 13:05:12 incr accepted_client=1 for ::1:46226 sock=10 14/07/2022 13:05:12 Client Protocol Version 3.8 14/07/2022 13:05:12 Protocol version sent 3.8, using 3.8 14/07/2022 13:05:12 rfbProcessClientSecurityType: executing handler for type 1 14/07/2022 13:05:12 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 14/07/2022 13:05:12 copy_tiles: allocating first_line at size 61 14/07/2022 13:05:12 Pixel format for client ::1: 14/07/2022 13:05:12 32 bpp, depth 24, little endian 14/07/2022 13:05:12 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 14/07/2022 13:05:12 no translation needed 14/07/2022 13:05:12 Using compression level 1 for client ::1 14/07/2022 13:05:12 Enabling X-style cursor updates for client ::1 14/07/2022 13:05:12 Enabling full-color cursor updates for client ::1 14/07/2022 13:05:12 Enabling cursor position updates for client ::1 14/07/2022 13:05:12 Enabling KeyboardLedState protocol extension for client ::1 14/07/2022 13:05:12 Enabling NewFBSize protocol extension for client ::1 14/07/2022 13:05:12 Enabling SupportedMessages protocol extension for client ::1 14/07/2022 13:05:12 Enabling SupportedEncodings protocol extension for client ::1 14/07/2022 13:05:12 Enabling ServerIdentity protocol extension for client ::1 14/07/2022 13:05:12 Using zlib encoding for client ::1 14/07/2022 13:05:13 client 1 network rate 1138.8 KB/sec (149289.3 eff KB/sec) 14/07/2022 13:05:13 client 1 latency: 53.2 ms 14/07/2022 13:05:13 dt1: 0.3126, dt2: 0.3807 dt3: 0.0532 bytes: 759236 14/07/2022 13:05:13 link_rate: LR_BROADBAND - 53 ms, 1138 KB/s 14/07/2022 13:05:13 client_set_net: ::1 0.0000 14/07/2022 13:05:13 created xdamage object: 0x400040 14/07/2022 13:05:15 Battling with something for -norepeat!! (1 resets left) 14/07/2022 13:05:15 Disabled X server key autorepeat. 14/07/2022 13:05:15 to force back on run: 'xset r on' (2 times) 14/07/2022 13:05:16 set_ncache_xrootpmap: loading background pixmap: 0x2600000 14/07/2022 13:05:17 Battling with something for -norepeat!! (0 resets left) 14/07/2022 13:05:17 Disabled X server key autorepeat. 14/07/2022 13:05:17 to force back on run: 'xset r on' (1 times) 14/07/2022 13:05:21 created selwin: 0x400041 14/07/2022 13:05:21 called initialize_xfixes()
Describe the bug
x11vnc exits shortly after a client connects, which only gets to briefly show the desktop. If I remove
-ncache …
, then the connection stays.To Reproduce
ssh -L 5930:localhost:5900 desktop -X "pkill x11vnc && x11vnc -display :0 -nopw -localhost -ncache 10 -gone 'xscreensaver-command -lock'"
on the laptop;ssvnc
orremmina
to connect tolocalhost:5930
;Log data below. I have also tried with
-norepeat
but it made no difference.If I remove
-ncache …
, it works as expectedExpected Behavior
Well, I expect the session to prevail, and be able to use
-ncache 10
.Desktop (please complete the following information):
Additional context
Here is the
x11vnc
output: