To work around this error message in directvnc 0.7.7, provide an
invalid filename (name of a nonexistent file). For example:
# directvnc 192.168.0.1 -m invalid-filename
where no file named 'invalid-filename' exists.
See bug #677204 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677204):
>Ok, that's actually a bug (!) that should be fixed in directvnc 0.7.8.
>I will prepare a new package with that version. Otherwise, the
>keyboard mapping file is optional (and documented in directvnc (1),
>directvnc-kbmapping (7) and directvnc-xmapconv (1)).
I'm running a debian derivative called r
Hi,
On Sun, Apr 8, 2012 at 12:42 PM, Frank lin Piat wrote:
> when I run directvnc, I get the error:
>
> Couldn't parse the keyboard mapping file
>
Ok, that's actually a bug (!) that should be fixed in directvnc 0.7.8.
I will prepare a new package with that version. Otherwise, the
keyboard mappi
Package: directvnc
Version: 0.7.7-1
Severity: normal
Dear Maintainer,
when I run directvnc, I get the error:
Couldn't parse the keyboard mapping file
Could you explain in the README.Debian how build those mapping.
(or even better... build them when the package is installed)
Regards,
Frankl
4 matches
Mail list logo