Bug#242987: xfree86-common: strange shift key behavior when caps-lock on
Works great, thanks. Denis Barbier wrote: here is the upstream fix (latest chunk has been removed since it is unrelated). I tested it and it works, but please confirm that it also works for you.
Processed: Re: Bug#242987: xfree86-common: strange shift key behavior when caps-lock on
Processing commands for [EMAIL PROTECTED]: > tags 242987 + patch Bug#242987: xlibs: strange shift key behavior when caps lock on with dvorak/japanese keyboard There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#242987: xfree86-common: strange shift key behavior when caps-lock on
tags 242987 + patch
thanks
On Sat, Apr 10, 2004 at 01:08:58AM -0400, John V. Belmonte wrote:
> Package: xfree86-common
> Version: 4.3.0-7
> Severity: normal
>
> I'm not confident if this is a bug, or if I've chosen the correct package.
> In any case, some package that has entered testing during the past week
> or so has caused my keyboard to behave badly under XFree86. Namely,
> when caps-lock is enabled, the shift key fails to produce the expected
> symbols on non-alphabetic keys. For example, Shift-5 yields '5' rather
> than '%'. The alphabetic keys work as expected (Shift-A yields 'a'). The
> console works correctly.
>
> I'm using a Dvorak layout and Japanese keyboard.
Hi,
here is the upstream fix (latest chunk has been removed since it is
unrelated). I tested it and it works, but please confirm that it
also works for you.
Denis
Index: dvorak
===
RCS file: /cvs/xc/programs/xkbcomp/symbols/pc/dvorak,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- dvorak 26 Nov 2002 01:43:25 - 1.1
+++ dvorak 19 Apr 2003 12:22:11 - 1.2
@@ -1,7 +1,7 @@
// based on a keyboard map from an 'xkb/symbols/dk' file
//
-// $XFree86: xc/programs/xkbcomp/symbols/pc/dvorak,v 1.1 2002/11/26 01:43:25
dawes Exp $
+// $XFree86: xc/programs/xkbcomp/symbols/pc/dvorak,v 1.2 2003/04/19 12:22:11
pascal Exp $
partial default alphanumeric_keys
xkb_symbols "basic" {
@@ -9,7 +9,6 @@
name[Group1]= "Dvorak";
// Alphanumeric section
-key.type[Group1] = "FOUR_LEVEL_ALPHABETIC";
key { [ grave,asciitilde, dead_grave, dead_tilde
] };
Bug#242987: xfree86-common: strange shift key behavior when caps-lock on
I've confirmed that this problem does not exist when I use the default QWERTY layout.
Processed: Re: Bug#242987: xfree86-common: strange shift key behavior when caps-lock on
Processing commands for [EMAIL PROTECTED]: > reassign 242987 xlibs Bug#242987: xfree86-common: strange shift key behavior when caps-lock on Bug reassigned from package `xfree86-common' to `xlibs'. > retitle 242987 xlibs: strange shift key behavior when caps lock on with > dvorak/japanese keyboard Bug#242987: xfree86-common: strange shift key behavior when caps-lock on Changed Bug title. > tag 242987 + moreinfo Bug#242987: xlibs: strange shift key behavior when caps lock on with dvorak/japanese keyboard There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#242987: xfree86-common: strange shift key behavior when caps-lock on
reassign 242987 xlibs retitle 242987 xlibs: strange shift key behavior when caps lock on with dvorak/japanese keyboard tag 242987 + moreinfo thanks On Sat, Apr 10, 2004 at 01:08:58AM -0400, John V. Belmonte wrote: > Package: xfree86-common > Version: 4.3.0-7 > Severity: normal > > I'm not confident if this is a bug, or if I've chosen the correct package. I've reassigned it accordingly. > In any case, some package that has entered testing during the past week > or so has caused my keyboard to behave badly under XFree86. Namely, > when caps-lock is enabled, the shift key fails to produce the expected > symbols on non-alphabetic keys. For example, Shift-5 yields '5' rather > than '%'. The alphabetic keys work as expected (Shift-A yields 'a'). The > console works correctly. > > I'm using a Dvorak layout and Japanese keyboard. Please excuse the impersonality of the following, but it will help if you do what it asks. :) [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more informtion is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xlibs > /tmp/output 3>&1 $ mailx -s "Re: Bug#242987" [EMAIL PROTECTED] < /tmp/output If you do not have a "mailx" command on your system, you can get by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you'r receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <[EMAIL PROTECTED]>. Thank you! -- G. Branden Robinson|I must confess to being surprised Debian GNU/Linux |by the magnitude of incompatibility [EMAIL PROTECTED] |with such a minor version bump. http://people.debian.org/~branden/ |-- Manoj Srivastava signature.asc Description: Digital signature
Bug#242987: xfree86-common: strange shift key behavior when caps-lock on
Package: xfree86-common Version: 4.3.0-7 Severity: normal I'm not confident if this is a bug, or if I've chosen the correct package. In any case, some package that has entered testing during the past week or so has caused my keyboard to behave badly under XFree86. Namely, when caps-lock is enabled, the shift key fails to produce the expected symbols on non-alphabetic keys. For example, Shift-5 yields '5' rather than '%'. The alphabetic keys work as expected (Shift-A yields 'a'). The console works correctly. I'm using a Dvorak layout and Japanese keyboard. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.5-patched Locale: LANG=C, LC_CTYPE=C Versions of packages xfree86-common depends on: ii debconf 1.4.16 Debian configuration management sy ii debianutils 2.8.1 Miscellaneous utilities specific t -- debconf information: xfree86-common/experimental_packages:
