Parents (Total: 33)

The searched file hash is included in 33 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	1DC3F6CBA537608B45FFA2C8357C0031
PackageArch	i586
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	3.47
PackageVersion	0.9.16
SHA-1	0C428C15537603209FF5B83BFAE7F1EE11DD9355
SHA-256	DFC0CCD5C7ED2099C0934C644FA5E9765C8950E2171A35C3DDDC08A1F2F464D4

Key	Value
MD5	B37C62298F204F9D9472D7DBE63FB176
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	bp153.1.13
PackageVersion	0.9.16
SHA-1	18217A11BC2E5B382135A455A72FC8C572FF3EC8
SHA-256	194075ED4B52E30C92141C92B853AD289258C9D907F56A82D327888F8AF560A3

Key	Value
MD5	B2B82B0C67BDF6FA3FE79C65902010C8
PackageArch	i586
PackageDescription	What WinVNC is to Windows x11vnc is to X Window System, i.e. a server which serves the current X Window System desktop via RFB (VNC) protocol to the user. Based on the ideas of x0rfbserver and on LibVNCServer it has evolved into a versatile and productive while still easy to use program.
PackageMaintainer	ns80 <ns80>
PackageName	x11vnc
PackageRelease	1.1.mga7
PackageVersion	0.9.16
SHA-1	1C17E53F9D97E73753F4ECF73D0882BCF2185DC5
SHA-256	D7ADA6AB1F498480AC6E7417EFADF7F2A2913116D286F70FE985D940DA9C79FA

Key	Value
MD5	2CACF756210F4C69DF13264FCEF2E7F9
PackageArch	i586
PackageDescription	What WinVNC is to Windows x11vnc is to X Window System, i.e. a server which serves the current X Window System desktop via RFB (VNC) protocol to the user. Based on the ideas of x0rfbserver and on LibVNCServer it has evolved into a versatile and productive while still easy to use program.
PackageMaintainer	luigiwalser <luigiwalser>
PackageName	x11vnc
PackageRelease	1.mga7
PackageVersion	0.9.16
SHA-1	240C42F26E4440B099C6FAEBB5FC377C23D40A21
SHA-256	F84605CAF70055415454CA7FEDC18E1E6A9CA3FBF3088DD47512B08D4A2BD25A

Key	Value
MD5	A077A38C5D8432CD1D31FFF1C241D089
PackageArch	s390x
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	bp156.3.8
PackageVersion	0.9.16
SHA-1	342ABC33E45CAE7714C724C9EB7F3EC97201D116
SHA-256	F528ED111BC37E9D41EE64119571B822C97120C58A5DBDB52EFCA3A600F09D65

Key	Value
MD5	CD97055B770529E369BCC433C4153B63
PackageArch	i586
PackageDescription	What WinVNC is to Windows x11vnc is to X Window System, i.e. a server which serves the current X Window System desktop via RFB (VNC) protocol to the user. Based on the ideas of x0rfbserver and on LibVNCServer it has evolved into a versatile and productive while still easy to use program.
PackageMaintainer	umeabot <umeabot>
PackageName	x11vnc
PackageRelease	6.mga9
PackageVersion	0.9.16
SHA-1	38DDC4DFF65DC66A2C0D54591939B74C81D5750D
SHA-256	4F8490A7445CC5D119B7D011DE93ACEC08BF2ADA0C61B85919D6A0B723751C48

Key	Value
MD5	8401224B84F8BBE9AAF416F47468F268
PackageArch	i586
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	2.9
PackageVersion	0.9.16
SHA-1	3D06FC4C3228AE2D4C1B0E265AC9471DBF38C722
SHA-256	E5B7FBB47A1431D2C1A6F90F655E76855B5523E999206A205A53AF652CD830CA

Key	Value
MD5	F6F0C5EFE04DB5539CA1529B2985EB0A
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	lp152.3.3
PackageVersion	0.9.16
SHA-1	484A4E1D2B2E4F70204C2B4CADB833018AFF01FE
SHA-256	BC04CC950130BAABAD409688DCFA9537D20EA96B8823B99852DE0D203AFF4EAB

Key	Value
MD5	865E5A1D89FE232E59476A41FB3D8E23
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	lp153.3.3
PackageVersion	0.9.16
SHA-1	4864EF6685CFEB0225131B32DA404C023509CF8F
SHA-256	28871E91A7CA22D39EC77F1C3C04BC2D74830100FB754640EF15BDFE3B825C7C

Key	Value
MD5	BF5FC2A1D90D294A100888318D9798D2
PackageArch	aarch64
PackageDescription	What WinVNC is to Windows x11vnc is to X Window System, i.e. a server which serves the current X Window System desktop via RFB (VNC) protocol to the user. Based on the ideas of x0rfbserver and on LibVNCServer it has evolved into a versatile and productive while still easy to use program.
PackageMaintainer	umeabot <umeabot>
PackageName	x11vnc
PackageRelease	6.mga9
PackageVersion	0.9.16
SHA-1	49470D865EB7A99F26714C1D974B053CBFD202CF
SHA-256	1965564727DD26BD41EDCD8A003AF2A4E4404370C4A5A285AD3C02942ACB5EBC