Hi again Joey
I can not really reproduce the problem. I have problem to get vino
working on my machine and I can not reproduce it without vino.
If it do not help to reconnect with xvnc4viewer, I think this bug
should be reassigned to vino.
Best regards,
// Ola
On Mon, Sep 08, 2008 at 11:34:59A
Ola Lundqvist wrote:
> What command line options did you use for the xvnc4viewer?
> Or more precisely, did you use the -shared option when doing this?
I wasn't using -shared, or any options aside from hostname.
On the vino side, it is configured with a password.
--
see shy jo
signature.asc
D
Hi Joey
This was an interesting bug. I'll see if I can reproduce it when I get
home to my testing machine.
What command line options did you use for the xvnc4viewer?
Or more precisely, did you use the -shared option when doing this?
I think it may be a combination of a gtk/gnome bug and the unex
Package: xvnc4viewer
Version: 4.1.1+X4.3.0-30
Severity: normal
I'm using vncviewer to connect from my laptop to a remote desktop on a
system running debian sid, with gnome. In gnome, vino has been conigured
to allow remote desktop control.
After I connect, I can exit using the popup menu with f8,
4 matches
Mail list logo