search for: vinos

I am trying to get vino going on CentOS 7.1 I run this command: gsettings set org.gnome.Vino require-encryption false Then this one: gsettings list-recursively org.gnome.Vino org.gnome.Vino notify-on-connect true org.gnome.Vino alternative-port uint16 5900 org.gnome.Vino disable-background false org.gnome.Vino use-alternative-port false org.gnome.Vino icon-visibility 'client'

Hi, The vino-server take too much cpu and memory, how to fix it? Cheers, M.

CentOS Errata and Security Advisory 2013:1452 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1452.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6f9e41d0b9e7dc36736a76d4e13e637faade333740eb51478580177461b631f7 vino-2.13.5-10.el5_10.i386.rpm x86_64:

CentOS Errata and Security Advisory 2013:1452 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1452.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ba60630e41e8c8341218d49294c94402ad59e251f1e4ef5b458aa2da7fc160cc vino-2.28.1-9.el6_4.i686.rpm x86_64:

sorry i figured this out after deleting the other parts of the thread. just run vino-preferences as the user who runs the main x display. it will have various options to enable and as soon as you do that you can get to hostname:0 via vnc. works quite well.

I have the vncserver running on CentOS 4, but when I log in using vncviewer from another box, I don't see my gnome desktop, just a fancy terminal. I suspect I need to edit the ~/.vnc "xstartup file, but what do I add to fix this. On all other distros I have tried, the vncserver serves up my gnome desktop by default. -- Lee Parmeter Emperor, linXos - The Flying Penguin

On 10/08/2015 09:53 AM, Milton Plasencia wrote: > The vino-server take too much cpu and memory, how to fix it? Turn off screen sharing in the gnome control panel?

Excuse me, i not find the gnome control panel, where is it? or how to call from the command line? i have gnome-control-center, but there i not see screen sharing. M. > On Oct 8, 2015, at 19:51, Gordon Messmer <gordon.messmer at gmail.com> wrote: > > On 10/08/2015 09:53 AM, Milton Plasencia wrote: >> The vino-server take too much cpu and memory, how to fix it? > >

The Vino package is installed on my CentOS 4 server, but I am unable to connect to it using vncviewer (vncviewer srvhost:0) from a client. However, I am not sure if it is "running" or how to "start" it if this is needed. The client machine in this case is running Ubuntu Hoary (gnome 2.10). The connection is just rejected. So, I am now wondering what else needs to be done to

On 10/08/2015 11:41 AM, Milton Plasencia wrote: > Excuse me, i not find the gnome control panel, where is it? or how to call from the command line? System ? Preferences ? Remote Desktop from the user menu. Under Sharing, uncheck the box labeled Allow other users to view your desktop.

On 10/08/2015 05:43 PM, Milton Plasencia wrote: > I uncheck only Allow other users ?view? and leave without change ?control? your desktop, > and the screen (active session) remain freeze, close the connection and now i can not > do a new connection, i remain out. > > i must wait the next Monday when i back to office or i can do something through ssh? You can re-enable it over ssh.

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi all, I'm looking for pointer for setting up VNC so that access to the system is via gdm/kdm. Yes, I know about vino, and /etc/sysconfig/vncservers but what I'm looking for is a sertup that allows me to see the *dm login screen instead of being dropped direct into a desktop. Thanks in advance

On Fri, Oct 9, 2015 at 12:29 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 10/08/2015 05:43 PM, Milton Plasencia wrote: > >> I uncheck only Allow other users ?view? and leave without change >> ?control? your desktop, >> and the screen (active session) remain freeze, close the connection and >> now i can not >> do a new connection, i remain

I uncheck only Allow other users ?view? and leave without change ?control? your desktop, and the screen (active session) remain freeze, close the connection and now i can not do a new connection, i remain out. i must wait the next Monday when i back to office or i can do something through ssh? M. > On Oct 9, 2015, at 01:42, Gordon Messmer <gordon.messmer at gmail.com> wrote: >

On Sun, 2007-01-14 at 18:38 +0000, Jason_Meers wrote: > Christoph Maser wrote: > > >> > > Actually the default logins (text mode and gdm) both show the hostname. > > Don't tell me you leave logged in sessions. > > > > No not normally, only on a few specific machines on the LAN that are > only accessible from another machine on the LAN. > >

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hello! I'm investigating a case where x11vnc (or RealVNC server or vino) on a _real_ X11 server seems to be broken with any VNC viewer. By broken I mean: it seems to keep old frames in memory, in such a way that in every three frames, two are from the past and one is the current one. This is easily spotted when using gnome-shell and looking at the clock at the top. Besides being

Hi. I don''t know if this one is known, but I can''t recall seeing anything about it. If it is old news I apologize. I discovered a bug in the inetd that comes with NetKit-B-0-08 and older. If a single SYN is sent to port 13 of the server, inetd will die of Broken Pipe: write(3, "Sun Jan 12 21:50:35 1997\r\n", 26) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) ---