v4.14.16 (not listed in version drop down) but standard on 16.04LTS Reproducible: Always Steps to Reproduce: 1. install real-vnc on Pi (as part of the standard desktop now) 2. attempt to connect via discovered .local or same ip:port displayed in Pi's GUI Actual Results: nothing happens for minutes, then a disconnect message Expected Results: connection using the realvnc client on the same machine connects without issue.
Running krdc from the command line only outputs tp-qt 0.9.6 DEBUG: Register StreamTubeClient with name "krdc_rfb_handler" tp-qt 0.9.6 DEBUG: Client registered - busName: "org.freedesktop.Telepathy.Client.krdc_rfb_handler" objectPath: "/org/freedesktop/Telepathy/Client/krdc_rfb_handler" interfaces: ("org.freedesktop.Telepathy.Client.Handler") krdc(9834)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory! krdc(9834)/krdc (VNC backend): rfbInitClient failed
Same problem. Raspberri Pi 2 Model B: realvnc-vnc-server-5.3.2.22164 My Computer: x86_64 openSUSE 42.1 Leap krdc 15.12.3-17.1 (in the "about KRDC" info: 4.14.18) libvncclient0 0.9.9-13.1 libvncserver0 0.9.9-13.1 Same console output.
I have the same problem too. Raspberry pi 3: realvnc-vnc-server/stable 5.3.2.22164 armhf My computer: KRDC 4.14.18, KDE 4.14.20 Or KRDC 16.11.70 (from git: af24d8d45ce74c299bd13bd1b881bc967f8f482f) KRDC 16.11.70 Log: KRDC: ########## KRDC ready: 1181 ms ########## KRDC: --------------------- trying init --------------------- KRDC: "VNC server supports protocol version -889997280.-772219232 (viewer 8.0)" KRDC: "We have -889998176 security types to read" KRDC: "-889998176) Received security type -772220976" KRDC: "-889998176) Received security type -772220976" KRDC: "-889998176) Received security type -772220976" KRDC: "-889998176) Received security type -772220976" KRDC: "Unknown authentication scheme from VNC server: \b" KRDC: rfbInitClient failed KRDC: --------------------- Starting main VNC event loop --------------------- Final part of vnc log: sudo vncserver-x11 Log=*:stderr:100 <13> 2016-10-01T18:34:24.307Z raspberrypi Xvnc[917]: Connections: connected: 192.168.1.33::43418 <15> 2016-10-01T18:34:24.310Z raspberrypi Xvnc[917]: SConnection: reading protocol version <14> 2016-10-01T18:34:24.310Z raspberrypi Xvnc[917]: SConnection: Client needs protocol version 3.8 <15> 2016-10-01T18:34:24.310Z raspberrypi Xvnc[917]: RfbConnection: Peer does not support sync, KeepAlive disabled <13> 2016-10-01T18:34:24.311Z raspberrypi Xvnc[917]: Connections: disconnected: 192.168.1.33::43418 ([EndOfStream] Disconnection by client) <15> 2016-10-01T18:34:24.311Z raspberrypi Xvnc[917]: FdIo: shutdown 0xfc1cd0 (fd=28), flush true (tellHandler true) <15> 2016-10-01T18:34:24.311Z raspberrypi Xvnc[917]: FdIo: shutdown complete 0xfc1cd0 (fd=28) <15> 2016-10-01T18:34:24.311Z raspberrypi Xvnc[917]: FdIo: shutdown 0xfc1cd0 (fd=28), flush true (tellHandler false) Which logs should i add to help with this problem?
If possible, it would probably help if you could post VNC server logs.
How would I get server logs ? Do you mean packet traces (e.g. wireshark) ? Or something else ?
@Tom Chiverton: I don't know if this server writes any logs, but you could check the log directory on your Pi. Log files should be easier to analyze than packet traces.
Trying to connect via (Real) VNC Viewer for Windows: Oct 11 22:57:21 raspberrypi vncserver-x11[637]: Connections: connected: 192.168.1.42::4381 Oct 11 22:57:30 raspberrypi vncserver-x11[637]: Connections: authenticated: 192.168.1.42::4381, as pi (f permissions) Result: success! Trying to connect via KRDC (openSUSE): Oct 11 23:08:58 raspberrypi vncserver-x11[637]: Connections: connected: 192.168.1.35::34209 Oct 11 23:08:58 raspberrypi vncserver-x11[637]: Connections: disconnected: 192.168.1.35::34209 ([EndOfStream] Disconnection by client) Result: failure. All messages are taken from the /var/log/syslog on the Pi device. https://www.realvnc.com/docs/logging.html
Ignat Awwit, thanks. It looks like a bug in the VNC library. KRDC VNC support is based on LibVNC: http://libvnc.github.io/success.html If you could try another client based on it to reproduce, it would be great. You can find other clients on the bottom of the page linked above. If you can reproduce it, please report the bug upstream and post a link here in this bug tracker: https://github.com/LibVNC/libvncserver
Urs Wolfer, thanks for you help. Trying to connect via Remmina (openSUSE). Pi log: Oct 13 02:22:30 raspberrypi vncserver-x11[624]: Connections: connected: 192.168.1.35::52260 Oct 13 02:22:30 raspberrypi vncserver-x11[624]: Connections: disconnected: 192.168.1.35::52260 ([EndOfStream] Disconnection by client) Remmina error message: "Unknown authentication scheme from VNC server: 13, 5, 6, 130" That's right, it is a bug in LibVNC. Anyway, KRDC does not show any messages, but simply stuck on connection stage. It's not very good =)
Created attachment 120748 [details] Real VNC is working on Raspberry Pi, KRDC doesn't work When I run KRDC using console, I also see message: "KRDC: rfbInitClient failed" VNC server: Raspberry Pi 2 Model B Rev 1.1 Linux raspberrypi 4.19.42-v7+ Debian GNU/Linux VNC(R) Server 6.4.1 (r40826) ARMv6 (Mar 13 2019 16:35:06) VNC client: Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-51-generic OS Type: 64-bit KRDC 19.04.2 gir1.2-gtk-vnc-2.0:amd64 0.7.2-1 libgtk-vnc-2.0-0:amd64 0.7.2-1 libgvnc-1.0-0:amd64 0.7.2-1 libvncclient1:amd64 0.9.11+dfsg-1ubuntu1.1
I tried several times with different formats (using "IP", "IP:1", "IP:5901"), but I saw only blank screen.
I'm seeing the same problem. It seems that KRDC is closing the connection. I see these logs in the raspi: ago 04 11:38:34 raspi vncserver-x11[524]: Connections: connected: 192.168.1.55::54706 (TCP) ago 04 11:38:34 raspi vncserver-x11[524]: Connections: disconnected: 192.168.1.55::54706 (TCP) ([EndOfStream] Disconnection by client And these messages in KRDC's console output: QWidget::setMaximumSize: (/VncView) Negative sizes (-2147483648,-2147483648) are not possible QWidget::setMaximumSize: (/VncView) Negative sizes (-2147483648,-2147483648) are not possible QWidget::setMaximumSize: (/VncView) Negative sizes (-2147483648,-2147483648) are not possible QWidget::setMaximumSize: (/VncView) Negative sizes (-2147483648,-2147483648) are not possible KRDC: rfbInitClient failed I'm running KRDC in a Wailand session, if it makes any difference. Client information: Operating System: Debian GNU/Linux (unstable) KRDC version: 21.12.3 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-3-amd64 (64-bit) Graphics Platform: Wayland Server information: Raspberry PI 4 Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.53-v8+ Architecture: arm64 Thanks.
I can confirm that - I get the same messages as in the post from Jose Couto above. Client information: Operating System: MX Linux 23.1 KDE x64 Libretto KRDC version: 22.12.3 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-10-amd64 (64-bit) Graphics Platform: X11 Server information: Raspberry Pi 3 Model B Rev 1.2 Operating System: Raspbian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v7+ Architecture: arm
(In reply to nutzloserwerbemuell from comment #13) > I can confirm that - I get the same messages as in the post from Jose Couto > above. > > Client information: > > Operating System: MX Linux 23.1 KDE x64 Libretto > KRDC version: 22.12.3 > KDE Plasma Version: 5.27.5 > KDE Frameworks Version: 5.103.0 > Qt Version: 5.15.8 > Kernel Version: 6.1.0-10-amd64 (64-bit) > Graphics Platform: X11 > > Server information: > > Raspberry Pi 3 Model B Rev 1.2 > Operating System: Raspbian GNU/Linux 11 (bullseye) > Kernel: Linux 6.1.21-v7+ > Architecture: arm Edit: The Raspi runs RealVNC Server 7.5.1 (r50075)