Vnc server arch linux

DESCRIPTION

vncsession is used to start a VNC (Virtual Network Computing) desktop. vncsession performs all the necessary steps to create a new user session, run Xvnc with appropriate options and starts a window manager on the VNC desktop.

vncsession is rarely called directly and is normally started by the system service manager.

FILES

Several VNC-related files are found in the directory $HOME/.vnc:

/etc/tigervnc/vncserver-config-defaults The optional system-wide equivalent of $HOME/.vnc/config. If this file exists and defines options to be passed to Xvnc, they will be used as defaults for users. The user’s $HOME/.vnc/config overrides settings configured in this file. The overall configuration file load order is: this file, $HOME/.vnc/config, and then /etc/tigervnc/vncserver-config-mandatory. None are required to exist. /etc/tigervnc/vncserver-config-mandatory The optional system-wide equivalent of $HOME/.vnc/config. If this file exists and defines options to be passed to Xvnc, they will override any of the same options defined in a user’s $HOME/.vnc/config. This file offers a mechanism to establish some basic form of system-wide policy. WARNING! There is nothing stopping users from constructing their own vncsession-like script that calls Xvnc directly to bypass any options defined in /etc/tigervnc/vncserver-config-mandatory. The overall configuration file load order is: /etc/tigervnc/vncserver-config-defaults, $HOME/.vnc/config, and then this file. None are required to exist. $HOME/.vnc/config An optional server config file wherein options to be passed to Xvnc are listed to avoid hard-coding them to the physical invocation. List options in this file one per line. For those requiring an argument, simply separate the option from the argument with an equal sign, for example: «geometry=2000×1200» or «securitytypes=vncauth,tlsvnc». Options without an argument are simply listed as a single word, for example: «localhost» or «alwaysshared».

The special option session can be used to control which session type will be started. This should match one of the files in /usr/share/xsessions. E.g. if there is a file called «gnome.desktop», then «session=gnome» would be set to use that session type.

$HOME/.vnc/passwd The VNC password file. $HOME/.vnc/host:display#.log The log file for Xvnc and the session.

SEE ALSO

AUTHOR

Tristan Richardson, RealVNC Ltd., D. R. Commander and others.

VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people have since participated in development, testing and support. This manual is part of the TigerVNC software suite.

Package name: extra/tigervnc Version: 1.13.1-1 Upstream: http://www.tigervnc.org Licenses: GPL Manuals: /listing/extra/tigervnc/ Table of contents

Powered by archmanweb, using mandoc for the conversion of manual pages.

The website is available under the terms of the GPL-3.0 license, except for the contents of the manual pages, which have their own license specified in the corresponding Arch Linux package.

Источник

Arch Linux User Repository

I’m away from my desk, don’t hesitate if you want to suggest a change of pkgbuild.

wongsyrone commented on 2023-04-21 00:46 (UTC) (edited on 2023-04-21 00:48 (UTC) by wongsyrone)

VNC Server 7.1.0 release note:

REMOVED: The vncserver symbolic link (symlink) will no longer be available by default. To launch Virtual Mode sessions, you will instead need to run the command, vncserver-virtual. Learn more here.

If you upgrade to 7.1.0, just remove the previous /usr/bin/vncserver and reinstall 7.1.0.

blackhole commented on 2023-04-21 00:42 (UTC)

pacman -Qo vncserver error: No package owns /usr/bin/vncserver

Kewl commented on 2023-04-20 16:31 (UTC)

Check what package includes the filename: pacman -Qo vncserver

amhainen commented on 2023-04-20 16:16 (UTC) (edited on 2023-04-20 16:17 (UTC) by amhainen)

Same issue as user=blackhole:
error: failed to commit transaction (conflicting files)
realvnc-vnc-server: /usr/bin/vncserver exists in filesystem

blackhole commented on 2023-04-20 08:41 (UTC)

After installing realvnc-vnc-viewer I have this error:

error: failed to commit transaction (conflicting files)

realvnc-vnc-server: /usr/bin/vncserver exists in filesystem

wongsyrone commented on 2023-04-20 00:01 (UTC)

inferno0230 commented on 2023-03-11 07:19 (UTC) (edited on 2023-03-11 07:21 (UTC) by inferno0230)

It seems that realvnc have changed links for downloading on their side,

inferno0230 in ~/apps/realvnc-vnc-server on master λ makepkg -si
==> Making package: realvnc-vnc-server 7.0.1-1 (Saturday 11 March 2023 12:32:28 PM) ==> Checking runtime dependencies. ==> Checking buildtime dependencies. ==> Retrieving sources. -> Downloading VNC-Server-7.0.1-Linux-x64.deb. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0 curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://www.realvnc.com/download/file/vnc.files/VNC-Server-7.0.1-Linux-x64.deb Aborting.

Cross checked with site and links in PKGBUILD and edited PKGBUILD as follows :-

can you make these changes upstream?

Kewl commented on 2023-02-14 10:22 (UTC) (edited on 2023-02-14 10:23 (UTC) by Kewl)

BenTheTechGuy commented on 2022-09-04 17:34 (UTC)

source_aarch64 should have VNC-Server-$-Linux-ARM64.deb instead of VNC-Server-$-Linux-ARM.deb ; ARM.deb is only for armv7h.

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник