Closed fxzxmicah closed 2 months ago
There needs to be much more context here for this to be useful.
Info: Capturing output HEADLESS-2
Info: >> Headless output 2 1536x864+0x0 Power:ON
DEBUG: ../src/server.c: 1939: Trying address: 127.0.0.1
DEBUG: ../src/server.c: 1959: Successfully bound to address
Info: Listening for connections on 127.0.0.1:5900
DEBUG: ../src/ctl-server.c: 808: Initializing wayvncctl socket: /run/user/1000/wayvncctl
Info: New client connection from 127.0.0.1: 0x559d822983f0 (ref 1)
DEBUG: ../src/server.c: 825: Client chose security type: 1
Info: Starting screen capture
DEBUG: ../src/main.c: 1337: Client connected, new client count: 1
DEBUG: ../src/ctl-server.c: 940: Enqueueing client-connected event: {"id":"1","address":"127.0.0.1","username":null,"seat":"Hyprland","connection_count":1}
DEBUG: ../src/ctl-server.c: 967: Enqueued client-connected event for 0 clients
DEBUG: ../src/server.c: 993: Using color palette for client 0x559d822983f0
DEBUG: ../src/server.c: 1008: Client 0x559d822983f0 chose pixel format: XRGB8888
DEBUG: ../src/server.c: 1079: Client 0x559d822983f0 set encodings: open-h264,tight,zrle,copyrect,hextile,rre,raw,qemu-extended-key-event
Info: Choosing tight encoding for client 0x559d822983f0
Info: Choosing open-h264 encoding for client 0x559d822983f0
Info: Opened DRM device /dev/dri/renderD128: driver i915 version 1.6.0.
ERROR: ../src/server.c: 1291: Failed to encode current frame
Info: Opened DRM device /dev/dri/renderD128: driver i915 version 1.6.0.
ERROR: ../src/server.c: 1291: Failed to encode current frame
Info: Opened DRM device /dev/dri/renderD128: driver i915 version 1.6.0.
ERROR: ../src/server.c: 1291: Failed to encode current frame
Info: Opened DRM device /dev/dri/renderD128: driver i915 version 1.6.0.
ERROR: ../src/server.c: 1291: Failed to encode current frame
Info: Opened DRM device /dev/dri/renderD128: driver i915 version 1.6.0.
ERROR: ../src/server.c: 1291: Failed to encode current frame
The error was resolved using parameter -e tight
, but the displayed screen remains black. Normal use can only be achieved after using the parameter -s
. So this may be a wlvncc issue.
When the screen remains black, there are the following error:
Oops, back-buffer is still attached.
You're probably running neatvnc v0.8.1 and it's failing to encode using h.264 and not falling back to the next encoding. This is fixed in neatvnc master. It would have been useful to also get the version info like suggested by the issue template.
GPU mode on wlvncc might fail when people have multiple GPUs on the system. It doesn't know how to select the right one, but like it says in the readme, wlvncc not considered production grade software.
OK, thanks.
wlvncc is built on fedora.