Skip to content

Latest commit

 

History

History
76 lines (50 loc) · 2.8 KB

troubleshooting.adoc

File metadata and controls

76 lines (50 loc) · 2.8 KB
Raw

Troubleshooting

Known issues

  • Connect only supports sharing a single, primary display of your Raspberry Pi. When a Raspberry Pi is connected to multiple HDMI screens, Connect sometimes shares the contents of the secondary screen. You can work around this by right-clicking the desktop and changing the location of the taskbar in Desktop Preferences…​.

  • Connect does not support on-screen keyboards. For full functionality, use a physical keyboard.

  • Connect requires a browser that implements ECMAScript 2020 (ES11) as it makes use of features unavailable in older browsers.

  • Browsers intercept certain keys and key combinations. As a result, you can’t type these keys into your Connect window. Connect provides a toolbar to simulate some of the most popular intercepted keys.

Enable enhanced logging

You can enable debug logging for both rpi-connect and its dedicated WayVNC server for a detailed account of local operations on your Raspberry Pi.

Enable enhanced logging in rpi-connect

Open the rpi-connect configuration file for editing with the following command:

$ systemctl --user edit rpi-connect

Enter the following lines of configuration between the comments:

ExecStart=
ExecStart=/usr/bin/rpi-connect-env /usr/bin/rpi-connectd -socket=%t/rpi-connect-wayvnc.sock -v
Note
 You need both lines that begin with ExecStart=.

Finally, restart the service with the following command:

$ systemctl --user restart rpi-connect

Enable enhanced logging in the dedicated wayvnc server

Open the configuration file for the dedicated WayVNC server associated with Connect:

$ systemctl --user edit rpi-connect-wayvnc

Enter the following lines of configuration between the comments:

ExecStart=
ExecStart=/usr/bin/rpi-connect-env /usr/bin/wayvnc --config /etc/rpi-connect/wayvnc.config --render-cursor --unix-socket --socket=%t/rpi-connect-wayvnc-ctl.sock -Ldebug %t/rpi-connect-wayvnc.sock
Note
 You need both lines that begin with ExecStart=.

Finally, restart the service with the following command:

$ systemctl --user restart rpi-connect-wayvnc

View Connect logs

To view logs for the Connect service and its dedicated WayVNC server, run the following command:

$ journalctl --user --follow --unit rpi-connect --unit rpi-connect-wayvnc