Parents (Total: 3)

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

Key	Value
MD5	8407A99CE11ADF8698D9AC764B762C33
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	lp151.2.20
PackageVersion	0.9.13
SHA-1	673917C3CB568DE7EFB2C5AB436C37D873EF3BE9
SHA-256	53B28B7A0C4DAB108C05B606497052F52DADEECDD1BEB412C2015E0FE9C9BBC7

Key	Value
MD5	CA02FDDDCE17EF00C4A98D14F29F1CA9
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	lp150.1.20
PackageVersion	0.9.13
SHA-1	8CC6F10DEE3FA5D02B777906E6FF162B6ABDBD76
SHA-256	8A5EF07EB3046FF5D35939F140B93F6DD3002FDE325BE269D1DCE6D29075468E

Key	Value
MD5	7F4E704D8AD9EA7299912C4A60611BD0
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	lp152.3.31
PackageVersion	0.9.13
SHA-1	8662CCCE86896204BE7DFAD53D0357AB0A79E502
SHA-256	5B19D7043A7F309FF94DF6BCA9557E4F7F32619414EE6247D89F0582C0516161