Summary: | ctrl:swapcaps doesn't work (fully) correctly | ||
---|---|---|---|
Product: | xkeyboard-config | Reporter: | Mohammed Adnène Trojette <adn> |
Component: | General | Assignee: | xkb |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | waste.manager |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
URL: | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410060 | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Mohammed Adnène Trojette
2007-07-09 15:20:11 UTC
If you output your XKB configuration using "xkbcomp :0 -xkb out.xkb" - is there any difference in mapping between keys 1 and 2? Ok. After looking for around 10 minutes in this file, I really can't find the info you are looking for. I put the output you asked on a website [1], because I was not sure what the policy here is for big attachments (>40k). I'll add it here as an attachment, if it is wanted/allowed. Just in case, the output was procudeced on an up-to-date debian unstable computer. Peter [1]: http://wwwcip.informatik.uni-erlangen.de/~siprbaum/out.xkb(In reply to comment #1) > If you output your XKB configuration using "xkbcomp :0 -xkb out.xkb" - is there > any difference in mapping between keys 1 and 2? > (In reply to comment #1) > If you output your XKB configuration using "xkbcomp :0 -xkb out.xkb" - is there > any difference in mapping between keys 1 and 2? > Funny enough, I just loaded your out.xkb to my X server (so my configuration is exact copy of yours) - and Ctl-Alt-1 works the same way as Ctl-Alt-4 (I mean, both work correctly). It is not reproducable for me :( Also, looking at out.xkb itself, I see keys 1 - 4 are really same. There must be something with fvwm. May be, you'd try reproducing the behavior with other WM/app? Ok. I tried it again here with an empty session consisting only of an xterm, no window manager involved. And <Key labeled CTRL>+<ALT>+1 produces some output in xev, whereas <Key labeled CapsLock>+<ALT>+1 does not. If this would only appear on my pc, I'd say I messed up with the xkb files (had some errors there from a packaging bug and had to fix those), but I double checked on another computer at universitity, (also with a session only consisting of an xterm) and it was totally reproducible. So blaming the window manager should be ruled out. From your comment it doesn't stand out if you pressed <CTRL>+<ALT>+1 or <CapsLock>+<ALT>+1, because only the later fails to produce the keysym ctrl+alt+1. Interesting enough. What version of xkeyboard-config do you have? Though ... It should not matter - because once you created out.xkb, xkeyboard-config is not involved any more (and your version works ok for me). May be, there is something special about your X server? What version is it? Sure I pressed Caps-Alt-1. (In reply to comment #4) > Ok. I tried it again here with an empty session consisting only of an xterm, no > window manager involved. And <Key labeled CTRL>+<ALT>+1 produces some output in > xev, whereas <Key labeled CapsLock>+<ALT>+1 does not. If this would only > appear on my pc, I'd say I messed up with the xkb files (had some errors there > from a packaging bug and had to fix those), but I double checked on another > computer at universitity, (also with a session only consisting of an xterm) and > it was totally reproducible. So blaming the window manager should be ruled out. > > From your comment it doesn't stand out if you pressed <CTRL>+<ALT>+1 or > <CapsLock>+<ALT>+1, because only the later fails to produce the keysym > ctrl+alt+1. > I have a standard Debian unstable here. (those at the uni have Debian Etch) Debian programm versions: xserver-xorg 1:7.2-5 xkb-data 1.0~cvs.20070721-1 Ok. Now wandering off to my brothers Ubuntu Feisty PC to see if I could reproduce it there, too. Some problem there. Could this be in any way related to the brand of keyboard itself? As I stated, on the sun keyboards at university it worked, but not on those with the FSC keyboards. Me and my brother have one of those FSC keyboads, too. > Some problem there. Could this be in any way related to the brand of keyboard > itself? It would be difficult to imagine such thing.. > As I stated, on the sun keyboards at university it worked, but not on those > with > the FSC keyboards. Me and my brother have one of those FSC keyboads, too. Well, try to find another keyboard (just for testing) and see whether you see that problem... Really odd one. Ok. It took me a while to get another keyboard, but I tried this with a logitech keyboard and I can't reproduce the strange behaviour there, so it seems that this is really a hardware problem with the FSC keyboards (I have tried at least 3 of them). So I changed the bug status to "NOTABUG" (not sure if this is the right thing), but at least other people should be able to find this strange hardware problem. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.