Your message dated Sat, 07 Aug 2021 16:18:47 +0200 with message-id <a019fda739b75720076ec6e03a0082b8e00ae9a4.camel@g-e-u-e-r.de> and subject line Bug#337900: fixed in tightvnc 1:1.3.9-6.1 has caused the Debian Bug report #545939, regarding [tightvncserver] Yields incorrect keyboard chars to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 545939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545939 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---Title: [tightvncserver] Yields incorrect keyboard chars
- To: <submit@bugs.debian.org>
- Subject: [tightvncserver] Yields incorrect keyboard chars
- From: "Conrad, Tom" <tom.conrad@totalems.com>
- Date: Wed, 9 Sep 2009 23:21:57 -0700
- Message-id: <2A63D4CC8864624F9B1D6000B8EB803E44EAC0@exchange03.sd1.smstech.com>
Package: tightvncserver
Subject: tightvncserver: Yields incorrect keyboard chars.
Version: 1.3.9-4
Severity: important
*** Please type your report below this line ***
As installed, tightvncserver converts normal keystrokes to incorrect
characters. Seems to be same as Ubuntu bug #112955 - see link below...
https://bugs.launchpad.net/baltix/+source/tightvnc/+bug/112955
This work-around from that thread appears to solve the problem...
Insert 'export XKL_XMODMAP_DISABLE=1' in $HOME/.vnc/xstartup before the
last line /etc/X11/Xsession (and restart tightvncserver instance)
I am using US-English settings in Lenny.
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages tightvncserver depends on:
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libjpeg62 6b-14 The Independent JPEG
Group's JPEG
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension
librar
ii perl 5.10.0-19 Larry Wall's Practical
Extraction
ii x11-common 1:7.3+18 X Window System (X.Org)
infrastruc
ii xbase-clients 1:7.3+19 miscellaneous X clients -
metapack
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages tightvncserver recommends:
ii xfonts-base 1:1.0.0-5 standard fonts for X
Versions of packages tightvncserver suggests:
pn tightvnc-java <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 545939-close@bugs.debian.org, tom.conrad@totalems.com
- Subject: Bug#337900: fixed in tightvnc 1:1.3.9-6.1
- From: Sven Geuer <debmaint@g-e-u-e-r.de>
- Date: Sat, 07 Aug 2021 16:18:47 +0200
- Message-id: <a019fda739b75720076ec6e03a0082b8e00ae9a4.camel@g-e-u-e-r.de>
- In-reply-to: <2A63D4CC8864624F9B1D6000B8EB803E44EAC0@exchange03.sd1.smstech.com>
- References: <2A63D4CC8864624F9B1D6000B8EB803E44EAC0@exchange03.sd1.smstech.com>
Source: tightvnc Source-Version: 1:1.3.9-6.1 On Wed, 9 Sep 2009 23:21:57 -0700 "Conrad, Tom" <tom.conrad@totalems.com> wrote: [...] > > As installed, tightvncserver converts normal keystrokes to incorrect > characters. Seems to be same as Ubuntu bug #112955 - see link > below... > > https://bugs.launchpad.net/baltix/+source/tightvnc/+bug/112955 > > This work-around from that thread appears to solve the problem... > > Insert 'export XKL_XMODMAP_DISABLE=1' in $HOME/.vnc/xstartup before > the last line /etc/X11/Xsession (and restart tightvncserver instance) > [...] This bug had been fixed with Tightvnc 1:1.3.9-6.1 by adding the proposed line to $HOME/.vnc/xstartup. Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---