Hi
Ok, thanks for the information.
Best regards,
// Ola
Quoting Frédéric Boiteux :
Le Sat, 21 Feb 2009 16:01:08 +0100,
Ola Lundqvist a écrit :
Hi
You have pinpointed the problem very well.
Please try vnc4server, I think that actually support this.
Hello,
I've tried vnc4server and
Le Sat, 21 Feb 2009 16:01:08 +0100,
Ola Lundqvist a écrit :
> Hi
>
> You have pinpointed the problem very well.
> Please try vnc4server, I think that actually support this.
Hello,
I've tried vnc4server and yes it works with Gnome, but looking at its
X11 info with xdpyinfo, I've found that
Hi
You have pinpointed the problem very well.
Please try vnc4server, I think that actually support this.
Best regards,
// Ola
On Fri, Feb 20, 2009 at 06:45:45PM +0100, Frédéric Boiteux wrote:
> Hello,
>
> I've also been hit by this problem, making my VNC connexions useless
> as I uses
Hello,
I've also been hit by this problem, making my VNC connexions useless
as I uses Gnome on my Lenny system, with a specific keyboard layout
(french dvorak variant). I guess that the problem comes from Xvnc not
providing XKB support : Gnome widely uses it to configure the keyboard,
as
Hi Julian
Thanks a lot for the information.
I think you have spotted the problem and I do not think vnc can be blamed
for that one.
The problem is that gnome tries to bypass the X configuration and load
something else.
The question is how to fix that... Your workaround is a way forward but
as y
A better workaround (but still less than ideal) to the ones mentioned above:
It seems that gnome is trying to load a default keymap when it
initializes, but tightvnc requires a specific one that's nothing like
the one gnome loads. By running the following command while logged in
with a twm se
I'm seeing this too, on lenny/amd64. Hopefully this should be enough
info to reproduce:
I installed a fresh copy of lenny using the beta2 network install disc
image, and ran an update via the update manager applet from the gnome
desktop.
Then I installed tightvncserver and set up gdm to acc
tags 476727 + help
thanks
Hi
This sounds like a strange problem. As for the original report I have
tried to reproduce this problem myself but failed. As I can not reproduce
it I do not really know how to handle this problem.
Help is much appriciated!
Best regards,
// Ola
On Tue, Nov 04, 2008
To clarify and in case it isn't obvious from the original report, the
gdm login screen works fine - it's only after login that the keyboard
map gets weird.
I'm using xvnc4viewer: if I use tightvncviewer or realvncviewer then the
vnc viewer never receives the input focus, perhaps again because I'm
I also see this in version 1.3.9-4 (testing).
I'm connecting from a Debian etch box using xvnc4viewer under Gnome; my
keyboard is a Logitech cordless US keyboard with windows keys, and I'm
using the "evdev" keyboard driver on the client - perhaps that's the
common element?
John.
--
[EMAIL PROT
Hi
This is strange. Do you connect from windows or some other operating system?
Begards,
// Ola
On Fri, Apr 18, 2008 at 07:58:25PM +0200, tortureduck wrote:
> Package: tightvncserver
> Version: 1.2.9-22
> Severity: important
>
> after installing tightvncserver and login to gnome the keyboard-l
Package: tightvncserver
Version: 1.2.9-22
Severity: important
after installing tightvncserver and login to gnome the keyboard-layout is
completely weird (/ = return)
on etch it worked without any troubles
as workaround i tried to install vnc4server and then everything works fine
i can reprodu
12 matches
Mail list logo