patrikolausson / dispmanx_vnc Goto Github PK

Is it possible to change resolution only of VNC, without messing around with /boot/config.txt?

The new debian release stretch has changed some of the library files that dispmanx_vnc uses, namely libGLESv2.so and libEGL.so. This causes dispmanx_vnc to failed to build because of the missing libraries. after installing libgles2-mesa and libsdl2-dev with "apt-get install libgles2-mesa libsdl2-dev", the missing library error is gone but there is new undefined reference error. The following is the output of "make":

g++ -Wall -std=c++11 -O3 -DHAVE_LIBBCM_HOST -DUSE_EXTERNAL_LIBBCM_HOST -DUSE_VCHIQ_ARM -I/opt/vc/include/ -I/opt/vc/include/interface/vcos/pthreads -I/opt/vc/include/interface/vmcs_host/linux -o dispmanx_vncserver main.o UFile.o DMXResource.o DMXDisplay.o DMXKeyboard.o DMXMouse.o DMXVNCServer.o -L/opt/vc/lib/ -lGLESv2 -lEGL -lopenmaxil -lbcm_host -lvcos -lvchiq_arm -lpthread -lrt -lvncserver -lconfig++
main.o: In function ReadConfigFile(char const*, std::string const&, ConfigData&)': main.cpp:(.text+0x6dc): undefined reference to libconfig::Config::lookupValue(char const*, std::string&) const'
main.cpp:(.text+0x71c): undefined reference to `libconfig::Config::lookupValue(char const*, std::string&) const'
collect2: error: ld returned 1 exit status
Makefile:25: recipe for target 'dispmanx_vncserver' failed
make: *** [dispmanx_vncserver] Error 1

I think maybe the new library installed is not exactly the same as the old library used to be on debian jessie, so not compatible?
Is there any plan on supporting debian stretch?

Hi,
maybe not an Issue, not sure. On my system the keyboard layout is mixed up. It's not US, it's not the local config. And I can't change it. I created a file (/etc/X11/xorg.conf.d/10-evdev.conf) for the evdev config.

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "xkb_layout" "de"
EndSection

Without success. Any idea how to fix the layout issue? Tried two different VNC clients.
System info: freshly installed raspbian jessie.

Best
Sesc

running dispmanx_vnc on a RPi (model 3B) using the official 800x480 touchscreen, the Y-axis mouse coordinates are inverted. adding in y = info.height - y into DoPtr() resolves this.

here is a a patch to add a '--flip-y' command line and configuration option:

flipy.patch.txt

This is on Rasbian stretch and the vnc client is tigervnc-1.8.0 on linux. The keyboard presses are not being picked up on the vnc server.

Evdev is loaded on RPI,

$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      SEM HCT Keyboard
/dev/input/event1:      SEM HCT Keyboard
/dev/input/event2:      Media Center Ed. eHome Infrared Remote Transceiver (1934:5168)

Here is the log

$ sudo /usr/local/bin/dispmanx_vncserver 
Open display[0]...
info: 1920, 1080, 0, 0
Display is 1920 x 1080
Server bpp:16
Server bigEndian:0
Server redShift:0
Server blueShift:10
Server greeShift:5
19/10/2017 05:46:30 Listening for VNC connections on TCP port 5900
19/10/2017 05:46:30 Listening for VNC connections on TCP6 port 5900
open /dev/uinput returned 6.
First write returned 1116.
ioctl UI_DEV_CREATE returned 0.
19/10/2017 05:46:40 Got connection from client 192.168.1.128
19/10/2017 05:46:40   other clients:
19/10/2017 05:46:40 Normal socket connection
Open display[0]...
info: 1920, 1080, 0, 0
Display is 1920 x 1080
19/10/2017 05:46:40 Client Protocol Version 3.8               
19/10/2017 05:46:40 Protocol version sent 3.8, using 3.8
19/10/2017 05:46:41 rfbProcessClientSecurityType: executing handler for type 1
19/10/2017 05:46:41 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
19/10/2017 05:46:42 Pixel format for client 192.168.1.128:
19/10/2017 05:46:42   32 bpp, depth 24, little endian
19/10/2017 05:46:42   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
19/10/2017 05:46:42 Enabling X-style cursor updates for client 192.168.1.128
19/10/2017 05:46:42 Enabling full-color cursor updates for client 192.168.1.128
19/10/2017 05:46:42 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
19/10/2017 05:46:42 Enabling NewFBSize protocol extension for client 192.168.1.128
19/10/2017 05:46:42 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC)
19/10/2017 05:46:42 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECD)
19/10/2017 05:46:42 Enabling LastRect protocol extension for client 192.168.1.128
19/10/2017 05:46:42 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC7)
19/10/2017 05:46:42 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC8)
19/10/2017 05:46:42 Using image quality level 8 for client 192.168.1.128
19/10/2017 05:46:42 Using JPEG subsampling 0, Q92 for client 192.168.1.128
19/10/2017 05:46:42 Using tight encoding for client 192.168.1.128
19/10/2017 05:47:00 Enabling X-style cursor updates for client 192.168.1.128
19/10/2017 05:47:00 Enabling full-color cursor updates for client 192.168.1.128
19/10/2017 05:47:00 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
19/10/2017 05:47:00 Enabling NewFBSize protocol extension for client 192.168.1.128
19/10/2017 05:47:00 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC)
19/10/2017 05:47:00 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECD)
19/10/2017 05:47:00 Enabling LastRect protocol extension for client 192.168.1.128
19/10/2017 05:47:00 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC7)
19/10/2017 05:47:00 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC8)
19/10/2017 05:47:00 Using image quality level 6 for client 192.168.1.128
19/10/2017 05:47:00 Using JPEG subsampling 0, Q79 for client 192.168.1.128
19/10/2017 05:47:00 Switching from tight to tight Encoding for client 192.168.1.128
^C19/10/2017 05:47:11 Client 192.168.1.128 gone         
19/10/2017 05:47:11 Statistics             events    Transmit/ RawEquiv ( saved)
19/10/2017 05:47:11  FramebufferUpdate   :      3 |         0/        0 (  0.0%)
19/10/2017 05:47:11  LastRect            :      1 |        12/       12 (  0.0%)
19/10/2017 05:47:11  tight               :     39 |    449265/  8301644 ( 94.6%)
19/10/2017 05:47:11  RichCursor          :      2 |       510/      510 (  0.0%)
19/10/2017 05:47:11  TOTALS              :     45 |    449787/  8302166 ( 94.6%)
19/10/2017 05:47:11 Statistics             events    Received/ RawEquiv ( saved)
19/10/2017 05:47:11  KeyEvent            :     10 |        80/       80 (  0.0%)
19/10/2017 05:47:11  FramebufferUpdate   :      4 |        40/       40 (  0.0%)
19/10/2017 05:47:11  SetEncodings        :      2 |       136/      136 (  0.0%)
19/10/2017 05:47:11  SetPixelFormat      :      1 |        20/       20 (  0.0%)
19/10/2017 05:47:11  PointerEvent        :     44 |       264/      264 (  0.0%)
19/10/2017 05:47:11  TOTALS              :     61 |       540/      540 (  0.0%)

Hello I love this server, so lightweight, I put it on all my PI's

My question is how would you allow cut and paste with this build of libvncserver

The package for this, autocutsel, works with other VNC builds, but this build is compiled differently

https://raspberrypi.stackexchange.com/questions/4474/tightvnc-copy-paste-between-local-os-and-raspberry-pi

I tried passing it with vnc-params in /etc/dispmanx_vncserver.conf

ie:
vnc-params = "autocutsel -fork";

Do you know how best to implement this? I don't have x11 installed as it's not required with Kodi and I think that could be why...

More of a feature request than a issue ...

Thanks

inetd is a handy way to start service instances without having one to listening in the background. Can inetd mode be enabled in dispmanx_vnc via the '-inetd' switch, similar to what already exists in x11vnc?

That way, a dispmanx_vnc instance would only be started by systemd at connection time, without having one to listen to traffic on a port. This saves up memory on environments with precious little resources (raspberry pi zero for instance).

For x11vnc, where inetd can be enabled, my x11vnc setup up consists of two files. Only the socket needs to be enabled to listen for a vnc connection.

$ cat /etc/systemd/system/x11vnc.socket
[Unit]
Description=x11vnc Socket for Per-Connection Servers

[Socket]
ListenStream=5900
Accept=true

[Install]
WantedBy=sockets.target

$ cat /etc/systemd/system/[email protected]
[Unit]
Description=x11vnc server daemon
Requires=blackbox.service x11vnc.socket
After=blackbox.service

[Service]
Environment=DISPLAY=:99
Environment=XAUTHORITY=/tmp/xvfb.auth 
Environment=ARGS="-forever -no6 -rfbport 5900 -nopw -shared -inetd"
Type=simple
ExecStart=/usr/bin/x11vnc -auth $XAUTHORITY -display $DISPLAY $ARGS
RemainAfterExit=no
StandardInput=socket
StandardOutput=journal
StandardError=journal
User=pi
Group=pi

[Install]
WantedBy=multi-user.target
Also=x11vnc.socket

Hi, I've been using your program for some years now and it has been working very good until recently. From time to time I receive this error [1]+ Segmentation fault sudo dispmanx_vncserver and not sure what is the cause. I didn't do any updates on my system. Have the latest version installed on my RPI3, running latest version of Raspbian. Please help.

When option display_rotate=2 is set the vnc windows appears upside down on client.

Is there a config option to rotate screen?

We are using dispmanx_vnc for one of our QT, Embedded OpenGL application.
Please find below our setup

Server side
QT application + dispmanx vnc server

Client side
RealVNC client - viewer (Control the QT application over VNC client)

Now client side we have touch+mouse sync issue. Mouse not synchronize with touch so touch is not working at client side. Sometime it work and synchronize if we touch upper left corner when r_x1 & r_y2 set to 0 by server. So can you help us to resolve the same?

Thanks

hanzelpeter used some kind of MIT with 'The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.'
Please include a licence file, to make it possible to contribute to the project.

Hello and great job that can bring kodi VNC control on my Pi,

There is a kind of glitch with Mojave that I think the wrong protocol version is detected on connexion

My question is: is there a way to force dispmanx to use another protocol version ? (hope that it might work)

here are the lines when i connect using Mojave (connexion not possible with built in screen sharing app)
trying: /etc/dispmanx_vncserver.conf
Read config file: /etc/dispmanx_vncserver.conf
Running vnc server with the following settings
frame-rate = 23
downscale = false
fullscreen = false
localhost = false
multi-threaded = false
password =
port = 5900
relative = false
screen = 0
unsafe = false
vnc-params =
Open display[0]...
info: 1920, 1080, 0, 0
Display is 1920 x 1080
Server bpp:16
Server bigEndian:0
Server redShift:0
Server blueShift:10
Server greeShift:5
27/01/2019 19:44:34 Listening for VNC connections on TCP port 5900
27/01/2019 19:44:34 Listening for VNC connections on TCP6 port 5900
open /dev/uinput returned 7.
First write returned 1116.
ioctl UI_DEV_CREATE returned 0.
open /dev/uinput returned 8.
First write returned 1116.
ioctl UI_DEV_CREATE returned 0.
27/01/2019 19:44:41 Got connection from client 192.168.1.3
27/01/2019 19:44:41 other clients:
27/01/2019 19:44:41 Normal socket connection
Open display[0]...
info: 1920, 1080, 0, 0
Display is 1920 x 1080
27/01/2019 19:44:41 Client Protocol Version 3.32
27/01/2019 19:44:41 Protocol version sent 3.3, using 3.3
27/01/2019 19:45:05 rfbProcessClientInitMessage: client gone
27/01/2019 19:45:05 Client 192.168.1.3 gone
27/01/2019 19:45:05 Statistics events Transmit/ RawEquiv ( saved)
27/01/2019 19:45:05 TOTALS : 0 | 0/ 0 ( 0.0%)
27/01/2019 19:45:05 Statistics events Received/ RawEquiv ( saved)
27/01/2019 19:45:05 TOTALS : 0 | 0/ 0 ( 0.0%)
27/01/2019 19:45:05 Got connection from client 192.168.1.3
27/01/2019 19:45:05 other clients:
27/01/2019 19:45:05 Normal socket connection
Open display[0]...
info: 1920, 1080, 0, 0
Display is 1920 x 1080
27/01/2019 19:45:05 Client Protocol Version 3.32
27/01/2019 19:45:05 Protocol version sent 3.3, using 3.3
Picture (006 fps) x0=0, y0=0, x1=0, y1=0

and here is the code when I connect with Snow Leopard (which works perfectly)
27/01/2019 19:42:16 Got connection from client 192.168.1.51
27/01/2019 19:42:16 other clients:
27/01/2019 19:42:16 Normal socket connection
Open display[0]...
info: 1920, 1080, 0, 0
Display is 1920 x 1080
27/01/2019 19:42:16 Client Protocol Version 3.889
27/01/2019 19:42:16 Protocol version sent 3.889, using 3.889
27/01/2019 19:42:16 rfbProcessClientSecurityType: executing handler for type 1
27/01/2019 19:42:16 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x000003F3)
27/01/2019 19:42:16 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x000003EA)
27/01/2019 19:42:16 Enabling full-color cursor updates for client 192.168.1.51
27/01/2019 19:42:16 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000450)
27/01/2019 19:42:16 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000044C)
27/01/2019 19:42:16 Enabling NewFBSize protocol extension for client 192.168.1.51
27/01/2019 19:42:16 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000044D)
27/01/2019 19:42:16 Using zlib encoding for client 192.168.1.51
27/01/2019 19:42:16 Pixel format for client 192.168.1.51:
27/01/2019 19:42:16 32 bpp, depth 32, little endian
27/01/2019 19:42:16 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
Picture (003 fps) x0=0, y0=0, x1=0, y1=0

Thanks for helping

Hi
I normally use the dispmanx-vnc to remotely control my graphic environment Xfce from raspberry.
However, since a few days ago I am unable to do so.
The service starts, I can see the remote computer monitor but I can't control it using the mouse or keyboard. The cursor simply don't move.
Regards

Hi,
Thanks for this software! It works a treat on a Raspberry Pi B model 2, with OSMC_TGT_rbp2_20151027.img.gz (based on Jessie, I believe).

One suggestion: In the README, put instructions on modifying the screen resolution. It's 720x480 out of the box. I went here: http://raspmer.blogspot.com/2015/07/vnc-server-for-raspberry-pi-with.html and here: https://www.raspberrypi.org/documentation/configuration/config-txt.md to figure out what to do. These are the settings I used in the /boot/config.txt:

#HDMI force hotplug
hdmi_force_hotplug=1
# Group DMT
hdmi_group=2
# mode 39 - 1360x768    60Hz
hdmi_mode=39

I rebooted after changing the file.

So note that this means you use the DMT table. Also, a higher sceen resolution means fewer frames per second.

Finally, note that you must remove the lines and reboot if you want to plug in a real screen.

PR #25 includes a sample debian package build configuration and a set of instructions on building a package.

The configuration includes a systemd listening socket that is activated on port 5901 (one port above the default vnc socket) without user interaction when the package is installed.

The listening port may be overriden with a systemd drop-in.

I'm on OSMC
built using the instructions in the readme...
and when i run the server everything seems legit,
but alas nothing but spinners when i try to connect from my client...

Heres the output from sudo ./dispmanx_vncserver

`
trying: /etc/dispmanx_vncserver.conf
No config file found
Running vnc server with the following settings
frame-rate = 15
downscale = false
fullscreen = false
multi-threaded = false
password =
port = 0
relative = false
screen = 0
unsafe = false
Open display[0]...
info: 640, 480, 0, 0
Display is 640 x 480
Server bpp:16
Server bigEndian:0
Server redShift:0
Server blueShift:10
Server greeShift:5
24/02/2016 17:42:23 Listening for VNC connections on TCP port 5900
24/02/2016 17:42:23 Listening for VNC connections on TCP6 port 5900
open /dev/uinput returned 7.
First write returned 1116.
ioctl UI_DEV_CREATE returned 0.
24/02/2016 17:44:23 Got connection from client 192.168.0.102
24/02/2016 17:44:23 other clients:
24/02/2016 17:44:23 Normal socket connection
Open display[0]...
info: 640, 480, 0, 0
Display is 640 x 480
24/02/2016 17:44:23 Client Protocol Version 3.3
24/02/2016 17:44:23 Protocol version sent 3.3, using 3.3
24/02/2016 17:44:26 rfbProcessClientInitMessage: client gone
24/02/2016 17:44:26 Client 192.168.0.102 gone
24/02/2016 17:44:26 Statistics events Transmit/ RawEquiv ( saved)
24/02/2016 17:44:26 TOTALS : 0 | 0/ 0 ( 0.0%)
24/02/2016 17:44:26 Statistics events Received/ RawEquiv ( saved)
24/02/2016 17:44:26 TOTALS : 0 | 0/ 0 ( 0.0%)
24/02/2016 17:44:26 Got connection from client 192.168.0.102
24/02/2016 17:44:26 other clients:
24/02/2016 17:44:26 Normal socket connection
Open display[0]...

`

I noticed that when I start dispmanx_vnc it creates an "event" node on /dev/input for the keyboard and a "mouse" node for the mouse.
However, when I plug in a physical mouse it creates both an "event" and a "mouse" node for the mouse.
Is there any reason why dispmanx_vnc doesn't also create an event node for the mouse?

I am asking because OpenFrameworks explicitly looks for an event node for the mouse, and thus I am unable to pass my vnc clients cursor to OpenFrameworks apps via dispmanx_vnc.

Hi,
I'm trying to compile on rpi/wheezy with gcc version 4.9.2 (Raspbian 4.9.2-10) and I'm getting this error:

Logger.hpp: In destructor ‘Logger::~Logger()’:
Logger.hpp:33:16: error: ‘put_time’ is not a member of ‘std’
   std::cerr << std::put_time(&bt, "%F %X") << "." << std::setfill('0') << std::setw(3) << ms.count() << std::setw(0)
                ^

Using 4.8 (as per your instructions!) I get different problems:

# make CXX=g++-4.8
g++-4.8 -Wall -std=c++11 -O3 -DHAVE_LIBBCM_HOST -DUSE_EXTERNAL_LIBBCM_HOST -DUSE_VCHIQ_ARM -I/opt/vc/include/ -I/opt/vc/include/interface/vcos/pthreads -I/opt/vc/include/interface/vmcs_host/linux -c DMXVNCServer.cpp -o DMXVNCServer.o
In file included from /usr/include/rfb/rfb.h:44:0,
                 from DMXVNCServer.hpp:11,
                 from DMXVNCServer.cpp:1:
/usr/include/c++/4.8/bits/sstream.tcc: In member function ‘virtual std::basic_stringbuf<_CharT, _Traits, _Alloc>::int_type std::basic_stringbuf<_CharT, _Traits, _Alloc>::overflow(std::basic_stringbuf<_CharT, _Traits, _Alloc>::int_type)’:
/usr/include/c++/4.8/bits/sstream.tcc:110:39: error: expected unqualified-id before ‘(’ token
    const __size_type __opt_len = std::max(__size_type(2 * __capacity),
                                       ^
In file included from DMXVNCServer.cpp:4:0:
Logger.hpp: In destructor ‘Logger::~Logger()’:
Logger.hpp:33:16: error: ‘put_time’ is not a member of ‘std’
   std::cerr << std::put_time(&bt, "%F %X") << "." << std::setfill('0') << std::setw(3) << ms.count() << std::setw(0)
                ^
In file included from /usr/include/rfb/rfb.h:44:0,
                 from DMXVNCServer.hpp:11,
                 from DMXVNCServer.cpp:1:
DMXVNCServer.cpp: In member function ‘void DMXVNCServer::Run(int, const string&, int, bool, bool, bool, bool, bool, bool, const string&)’:
DMXVNCServer.cpp:243:17: error: expected unqualified-id before ‘(’ token
            std::max(m_frameRect.left / 2, x * m_imageMap.pixelsPerRegion / 2),
                 ^
DMXVNCServer.cpp:244:17: error: expected unqualified-id before ‘(’ token
            std::max(m_frameRect.top / 2, y * m_imageMap.pixelsPerRegion / 2),
                 ^
DMXVNCServer.cpp:250:17: error: expected unqualified-id before ‘(’ token
            std::max(m_frameRect.left, x * m_imageMap.pixelsPerRegion),
                 ^
DMXVNCServer.cpp:251:17: error: expected unqualified-id before ‘(’ token
            std::max(m_frameRect.top, y * m_imageMap.pixelsPerRegion),
                 ^
DMXVNCServer.cpp:271:35: error: expected unqualified-id before ‘(’ token
       auto idleSleepFactor = std::max(std::chrono::seconds{1}.count(), std::chrono::duration_cast<std::chrono::seconds>(std::chrono::steady_clock::now() - m_timeLastFrameChange).count());
                                   ^
DMXVNCServer.cpp:300:21: error: expected unqualified-id before ‘(’ token
    sleep_for = std::max(timeToTakePicture, std::chrono::steady_clock::duration{std::chrono::milliseconds{m_server->deferUpdateTime}});
                     ^
DMXVNCServer.cpp: In member function ‘std::chrono::_V2::steady_clock::duration DMXVNCServer::TimeToTakePicture()’:
DMXVNCServer.cpp:322:14: error: expected unqualified-id before ‘(’ token
  return std::max(std::chrono::steady_clock::duration{}, m_pictureTimeout - elapsed);
              ^
DMXVNCServer.cpp:323:1: warning: control reaches end of non-void function [-Wreturn-type]
 };
 ^
Makefile:29: recipe for target 'DMXVNCServer.o' failed
make: *** [DMXVNCServer.o] Error 1

(I must have had this working before as I sent you a note in Jan 2017 about inverted Y axis)

I was trying to edit a file in nano and when I hit Ctrl-X I just got an X.

It seems control isn't sent.