Re: Vino and Vinagre branched for 2.26
El dt 21 de 04 de 2009 a les 09:11 -0300, en/na Jonh Wendell va escriure: > Branch names are gnome-2-26. > > Development will happen in master. > > Cheers, l10n.gnome.org updated! Cheers, -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Vino and Vinagre branched for 2.26
You can take a look at: http://grdc.sourceforge.net It is a good application El mar, 21-04-2009 a las 15:17 +0200, Andre Klapper escribió: > Hi Jonh, > > Am Dienstag, den 21.04.2009, 09:50 -0300 schrieb Jonh Wendell: > > My friend Jorge Pereira (CC'ed) is working on porting rdesktop to a gtk+ > > widget just like gtk-vnc is. > > > Hopefully it will be done for 2.28 :) > > please add this to http://live.gnome.org/RoadMap . > > andre Pulse para ir al sitio web Jesús Barbero Rodríguez Departamento de Análisis y Programación - Desarrollo tecnológico Zoco Gran Santander, 1ª Planta ■ 39011 Peñacastillo ■ Santander ■ ESPAÑA Tel.: +34 902 233 323 ■ Fax: +34 902 234 280 AVISO LEGAL: Este mensaje contiene información destinada exclusivamente al usuario de destino, pudiendo contener información confidencial o protegida legalmente. Si, por un error de envío o transmisión, ha recibido este mensaje y usted no es el destinatario del mismo, por favor, notifique de este hecho al remitente y no use, informe, distribuya, imprima, copie o difunda este mensaje bajo ningún medio . Cualquier opinión en él contenida, es exclusiva de su autor y no representa necesariamente la opinión de Quiter Servicios Informáticos, S.L. LEGAL WARNING: This e-mail and any attachment, contain information intended solely for the addressee and may contain confidential information or legally protected data. If you are not the intended recipient, please notify the sender and do not use, disclose, distribute, copy, print or rely on this e-mail under any circumstances. The views and opinions expressed are the authorŽs own and do not necessarily reflect those of Quiter Servicios Informáticos, S.L. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Vino and Vinagre branched for 2.26
Hi Jonh, Am Dienstag, den 21.04.2009, 09:50 -0300 schrieb Jonh Wendell: > My friend Jorge Pereira (CC'ed) is working on porting rdesktop to a gtk+ > widget just like gtk-vnc is. > Hopefully it will be done for 2.28 :) please add this to http://live.gnome.org/RoadMap . andre -- mailto:ak...@gmx.net | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Vino and Vinagre branched for 2.26
Em Ter, 2009-04-21 às 13:40 +0100, Alberto Ruiz escreveu: > 2009/4/21 Jonh Wendell : > > Branch names are gnome-2-26. > > > > Development will happen in master. > > Are there any plans for an RDP Gtk+ widget during this cycle? YEP!!! My friend Jorge Pereira (CC'ed) is working on porting rdesktop to a gtk+ widget just like gtk-vnc is. I'm working on turning the vinagre internal structure into a generic one. Currently it works only with VNC. Hopefully it will be done for 2.28 :) Cheers, -- Jonh Wendell http://www.bani.com.br ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Vino and Vinagre branched for 2.26
2009/4/21 Jonh Wendell : > Branch names are gnome-2-26. > > Development will happen in master. Are there any plans for an RDP Gtk+ widget during this cycle? > Cheers, > -- > Jonh Wendell > www.bani.com.br > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > -- Un saludo, Alberto Ruiz ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino branched for 2.16
Updated status pages, thanks El mar, 10-10-2006 a las 08:09 +0100, Mark McLoughlin escribió: > Hi, > vino has branched - 2.16 stuff on the gnome-2-16 branch. > > Hopefully we'll get some of the patches languishing in bugzilla into > HEAD soon. I'd list which ones I'm hoping to get in, including the one I > was just looking at (#333752), but bugzilla has chosen this exact > instant to ban my IP address :-) > > Cheers, > Mark. > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino branched for 2.16
On Tue, Oct 10, 2006 at 08:09:37AM +0100, Mark McLoughlin wrote: > Hopefully we'll get some of the patches languishing in bugzilla into > HEAD soon. I'd list which ones I'm hoping to get in, including the one I > was just looking at (#333752), but bugzilla has chosen this exact > instant to ban my IP address :-) For other readers: Bugzilla had a configuration change to automatically ban spiders ignoring robots.txt. This is done by analysing the URL. When it looks like it comes from a (ignorant) spider, your IP address will be banned. Note that ignorant spiders are usually spammers looking for email addresses. If your IP address was banned, just mail [EMAIL PROTECTED] (specify the IP address in the subject) and we'll give you the details on what caused the ban. This way you can avoid being banned in future. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino
Hi, It would be great if we can get a notification area icon when someone is connected to the vino server and give a context menu to do some operations like killing the connection or some other thing. Vino is very useful for me at my work place, may be I should file a RFE in bugzilla. Cheers, -William El lun, 24-04-2006 a las 18:16 +0100, Calum Benson escribió: > On Sat, 2006-04-22 at 13:44 -0400, Luis Villa wrote: > > Hi, Ted: > > Judging from the changelog: > > http://cvs.gnome.org/viewcvs/vino/ChangeLog?rev=1.133&view=markup > > > > and this bug: > > http://bugzilla.gnome.org/show_bug.cgi?id=159874 > > > > development might best be described right now as 'very slow' :) You > > can find the primary maintainer's email in there by skimming a bit; it > > does look like he is willing to take patches and give advice if one > > can be patient. > > Some Sun guys (led by Steven Zhang) have been doing some > security-related work on vino recently too, to get it into shape for > OpenSolaris... you might try and touch base with them on > [EMAIL PROTECTED] > > Cheeri, > Calum. > __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam �gratis! Reg�strate ya - http://correo.yahoo.com.mx/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino
On Sat, 2006-04-22 at 13:44 -0400, Luis Villa wrote: > Hi, Ted: > Judging from the changelog: > http://cvs.gnome.org/viewcvs/vino/ChangeLog?rev=1.133&view=markup > > and this bug: > http://bugzilla.gnome.org/show_bug.cgi?id=159874 > > development might best be described right now as 'very slow' :) You > can find the primary maintainer's email in there by skimming a bit; it > does look like he is willing to take patches and give advice if one > can be patient. Some Sun guys (led by Steven Zhang) have been doing some security-related work on vino recently too, to get it into shape for OpenSolaris... you might try and touch base with them on [EMAIL PROTECTED] Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]Java Desktop System Group http://ie.sun.com +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino
Hi, Ted: Judging from the changelog: http://cvs.gnome.org/viewcvs/vino/ChangeLog?rev=1.133&view=markup and this bug: http://bugzilla.gnome.org/show_bug.cgi?id=159874 development might best be described right now as 'very slow' :) You can find the primary maintainer's email in there by skimming a bit; it does look like he is willing to take patches and give advice if one can be patient. Sorry, that's the best I can say right now- Luis On 4/21/06, Ted Shab <[EMAIL PROTECTED]> wrote: > I'm trying to find out if anyone is actively developing vino at this > point in time. I had a few questions for them on what would be > involved in introducing true RSA key encryption. > > Thanks. > > --Ted > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino branched
Jeff Waugh wrote: > > > > >>Someone with more perl-fu than me- would it be possible to set up a script >>to watch cvs-commits list and send this kind of mail out automatically, or >>just update a webpage somewhere? Making maintainers do this manually (and >>remember to do it automatically) seems sort of crap... >> >> > >Unless you set up a polling mechanism for branches that exist on particular >important files, you'd never know - there's no hook mechanism for branching >that I know of (and certainly not related to commit). > > There is the CVSROOT/taginfo file, which says what to do when some files are tagged (similar to how CVSROOT/loginfo lists programs to run on commits). I don't know if there are any existing taginfo scripts that could easily be used for what Luis suggested though. James. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino branched
> Someone with more perl-fu than me- would it be possible to set up a script > to watch cvs-commits list and send this kind of mail out automatically, or > just update a webpage somewhere? Making maintainers do this manually (and > remember to do it automatically) seems sort of crap... Unless you set up a polling mechanism for branches that exist on particular important files, you'd never know - there's no hook mechanism for branching that I know of (and certainly not related to commit). - Jeff -- GUADEC 2005: May 29th-31st http://2005.guadec.org/ W.O.R.K: Weekend Over, Resume the Killings. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino branched
On 5/19/05, Mark McLoughlin <[EMAIL PROTECTED]> wrote: > On Thu, 2005-05-19 at 10:50 -0400, Luis Villa wrote: > > Someone with more perl-fu than me- would it be possible to set up a > > script to watch cvs-commits list and send this kind of mail out > > automatically, or just update a webpage somewhere? Making maintainers > > do this manually (and remember to do it automatically) seems sort of > > crap... > > There's no commit message for branching ... Well then. Luis (going back to his cvs-commits-list-free hole) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino branched
On Thu, 2005-05-19 at 10:50 -0400, Luis Villa wrote: > Someone with more perl-fu than me- would it be possible to set up a > script to watch cvs-commits list and send this kind of mail out > automatically, or just update a webpage somewhere? Making maintainers > do this manually (and remember to do it automatically) seems sort of > crap... There's no commit message for branching ... Cheers, Mark. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: vino branched
Someone with more perl-fu than me- would it be possible to set up a script to watch cvs-commits list and send this kind of mail out automatically, or just update a webpage somewhere? Making maintainers do this manually (and remember to do it automatically) seems sort of crap... Luis (Jeff can't even remember to put his pants on, glad he isn't a maintainer ;) On 5/19/05, Mark McLoughlin <[EMAIL PROTECTED]> wrote: > Hi, > I've created a gnome-2-10 branch for vino. > > Thanks, > Mark. > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Vino performance question for an IBM T41 (Radeon M10)
On Wed, 2005-03-30 at 17:10 -0500, Martin Weinberg wrote: > Folks, > > I've been experimenting with vino and have found the following odd > behavior with my dual-head laptop (IBM T41p running Debian testing). > > I have my second card/screen configured at 1024x768 for video > presentations since the main LCD is 1400x1050 which most projectors > can't handle. So I start acroread or whatever on the second screen. > > To see the projected screen on the laptop monitor, one can use VNC in > one of the following three ways: > > 1) Run a vncserver on the second screen (:0.1) and attach a vncviewer >to this. > > 2) Run x11vnc on the second screen and attach a vncviewer >to this. > > 3) Install vino and run a viewer on localhost:1. > > All three of these work. But I find that with vino, the cpu usage is > pegged at 100% with the xserver taking up the lion's share of the > cycles. Whereas with the other two the cpu usage is very low. On the > other hand, the vino response seems better than the other two options. > > I will also point out that it does not have to do with the second > screen directly: if I attach remotely to the laptop on the main > screen the same thing happens. > > This does not happen with other desktops (with different xserver > drivers) so I guess this is somehow XFree86 drv_ati related. > Does anyone know what is going (and what I can do to investigate)? > No additional log message anywhere during the vino server usage. Sounds like a bug .. A debug log might help to figure out what's going on. I think the best way to get that is: 1) gconftool-2 -s /desktop/gnome/remote_access/enabled -t bool false 2) killall vino-server 3) VINO_SERVER_DEBUG=1 /usr/libexec/vino-server 4) gconftool-2 -s /desktop/gnome/remote_access/enabled -t bool true and then connect. Cheers, Mark. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
