Parents (Total: 9)

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

Key	Value
MD5	B3251CCD549354E1CBCD5693D189E2DC
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	lp151.3.1
PackageVersion	0.9.16
SHA-1	E6F41A0A81F08E1BCAD6A4D53E10929E5ADB2478
SHA-256	F38661ABB2962C8E2E20CB71ABCA70AFA10F359632ADEF28DCF3E58E39261C9D

Key	Value
MD5	FD0312E824010F7755705A794A4F94AE
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	C60FFF00A4C91EDBC0F4FE7D2DD3005357422E14
SHA-256	95B914159B1EB75AB6DAD473D4A0A628C49F19DFD580CCE6AD1753CCA3298A2E

Key	Value
MD5	4A47069BDF342B5D988103C3AE35F617
PackageArch	aarch64_ilp32
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	2.2
PackageVersion	0.9.16
SHA-1	C0EB26C435BB03765DC92656E5A4F21F1F067C65
SHA-256	943BCE6EA555D0C2B9A2065625335A920F45711FBFE69BD68435AFF10251542C

Key	Value
MD5	5B783D0DED424F207AD1D0E328E0C3AE
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	3.3
PackageVersion	0.9.16
SHA-1	046D1AB7FD6D4E9C49530F7D2FE9777AC473F9F5
SHA-256	C173C6C1B433A5517955F2344184A91280FE27729807F8D6513CCAD0E12F5324

Key	Value
MD5	132647055C18F6CA977D832852CE1F6E
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	3CF4271433463AB356E04CF1F9512B574CA0605C
SHA-256	CA745869EF2A7A75432EF07627B1847CE8EA314A7C53967E1BF5C2AF2F93A8AE

Key	Value
MD5	95F05D4869096DF8F491DDB554428936
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	2.7
PackageVersion	0.9.16
SHA-1	D09EE0DA220949530E72D59CF474B84B36417A5F
SHA-256	CB79BE4A35C0E4702C12D41045DB5B139E35C56E53A60986A1C022124F332A6F

Key	Value
MD5	5AD19DD78DC6CB2B0FB5BAB891EB49C4
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	D5ACDAB5A81587F7E648489CB5E56A39E69FA673
SHA-256	32C83298CB4D2EF48A3C6FF0024DF29D8635D91EEE944ED1A0F601ED57DF971B

Key	Value
MD5	EF46039ABBB89B974A83D62FA8F8A918
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	3.2
PackageVersion	0.9.16
SHA-1	ADB826A968C6746F41106C27C28623FDB6352CB4
SHA-256	84E5ACA97E9D18EC08E5F2B0519AB22CCAD6380C7759B616995697B886ABE497

Key	Value
MD5	6F5E0C433C02AFBB7057A958F6B70B48
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	2.9
PackageVersion	0.9.16
SHA-1	1FA3BCA886449E85B2CB2D4AE8CF858E70BFA69F
SHA-256	796B3D9A1F23F859F1A7025CFA2C51D955EBB1FF1C5BF7D25AB3767D8782C2AD