
PKGNAME: tightvnc Flavors: there is no flavor information for this port.

NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
Remotix and tightvnc 1.3.10 problems install#
To install the port: cd /usr/ports/net/tightvnc/ & make install clean To add the package, run one of these commands: There are no Conflicts Matches for this port.

Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15) All times are UTCġ.3.10_6 net =67 Version of this port present on the latest quarterly branch.

Remotix and tightvnc 1.3.10 problems how to#
I see the XKB_RULES_NAMES error but can't figure out how to fix it or if this is related to my problem.FreshPorts - net/tightvnc: Enhanced version of VNCĪs an Amazon Associate I earn from qualifying purchases. This is my ~/.vnc/xstartup file: #!/bin/bashĪnd my i3 version is: i3 version 4.14.1 () © 2009 Michael Stapelberg and contributorsĪny help would be appreciated. Note the i3 config fails to come up over vnc as well, but I copied over the default config manually. The config file "/home/ray/.config/i3/config" already exists. 12:56:09 PM - ERROR: Could not get _XKB_RULES_NAMES atom from root window, falling back to defaults. If I kick off a terminal in my ~/.vnc/xstartup file it will come up and be functional, but if I use this terminal to make a new one like ctrl+shift+n then it brings up the new terminal on top of the old one and doesn't tile. mod+enter doesn't bring up a new terminal, mod+d doesn't let me run a new program, etc. I can start an i3 desktop on the server that is fully functional, but when I try to setup the VNC session to run i3 I can't do basically anything. I am having trouble getting i3 working over a VNC session.
