![]() ![]() It may worth trying to install vncconfig to see if it works for you. TightVNC is a free and open-source remote desktop software server and client application for Linux and Windows.A server for macOS is available under a commercial source code license only, without SDK or binary version provided. The issue I have with installing vncconfig is probably due to some package repositoriy config issue (do not have much time to figure that one out). I believe vncconfig would work if vncconfig is installed. From screenshot I see only two problems - grey screen and missing indicators. Both provides window manager and you need only one. You need to install few packages: sudo apt-get install metacity gnome-panel UPDATE 1: You need only x-window-manager or metacity. Tested copy and paste between VNC client and Windows 10 – it works! Your vnc log file tells you about problem.Note “-depth 24” setting the colour depth to 24 – this is required in my case to get VNC to work properly.Next to edit xstart, comment out vncconfig and add autocutselĬhecked “man autocutsel”, the purpose of switch “-fork” is to run autocutsel as daemon in the background. ![]() All in one connected experience - not a maze of charts. Use WinRAR or similar to extract the host folder from that file, which is in fact a zip archive. Web search did not return much useful information hence attempt to install autocutsel next Get a live and in-depth view of your network, infrastructure, applications, end-user experience, machine learning models and more. TightVNC Portable Edition 1.3.Because vncconfig is already included in the ~./vnc/xstart hence attempt to install vncconfig.Back to the issue, did web search and found a lot of references to adding the following to the xstartup to resolve the issue.Xresources is not really have any impact so workaround / suppress the error by creating an empty file /home/username/.vnc/xstartup: 8: /home/username/.vnc/xstartup: vncconfig: not found TightVNC 1.3.10 for Windows Requirements: Windows 2003, Windows 7, Windows XP, Windows 8, Windows 2000, Windows Vista, Windows NT Language: English Available languages: English, German, Spanish, French, Italian, Japanese, Polish, Chinese License: Free Latest update: Friday, January 28th 2022 Author: TightVNC.Xrdb: can’t open file ‘/home/username/.Xresources’ This graph shows which files directly or indirectly include this file: Go to the source code of this file. Checked the log file (~./vnc/machine:1.log) generated after vncserver started and found the following two errors Fossies Dox: tightvnc-1.3. ('inofficial' and yet experimental doxygen-generated source code documentation) Macros.Issue – cannot copy and paste from TightVNC Client to Windows 10.Client – Windows 10 Professional running TightVNC Client.After installing Xfce on Debian server and confirmed working, TightVNC Server is installed. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |