On a ThinkPad X201s you have some extra keys on the tablet: one which looks like a round circle, which triggers an evdev event KEY_CYCLEWINDOWS. There is no unanimous interpretation of the meaning of the icon, but cycling windows (aka Alt+Tab) seemed the most useful to have there. Another key has a portrait and landscape screen symbol with arrows in between, i. e. change between portrait and landscape screen rotation; it is currently triggering a KEY_DIRECTION evdev event.
Pressing the latter does nothing, pressing the former key causes screen rotation. It should be the other way around.
/usr/share/X11/xkb/symbols/inet maps <I162> (which is KEY_CYCLEWINDOWS) to XF86RotateWindows.
The problem here is that there is unclear terminology on all three levels of the stack here:
* "Rotating windows" is a misnomer and doesn't make sense; what we really want is either cycling windows or rotating screens. I think xkb-data shouldn't map cycling windows to rotating windows, so I file this against xkb-data.
* KEY_DIRECTION is a bit underspecified, too. It could be used for screen rotation just as well as for changing the direction your turtle is walking in your Logo interpreter.
* gnome-settings-daemon causes screen rotation on XF86RotateWindows. But as there is no XF86RotateScreen, that's the closest xkbsym to use.
I think it would be best to fix it in the xkb-data layer and map <I161> (KEY_DIRECTION) to XF86RotateScreen and don't define <I162> (KEY_CYCLEWINDOWS).
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xkb-data 2.2.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
Uname: Linux 3.0-1-generic x86_64
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: compiz
Date: Mon Jun 27 16:21:11 2011
Dependencies:
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:215a]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
MachineType: LENOVO 3323REG
PackageArchitecture: all
ProcEnviron:
LANGUAGE=de_DE:en
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0-1-generic root=UUID=272e96ff-bdea-4dc8-94ae-7bb1a90e049e ro quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: xkeyboard-config
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET46WW (1.16 )
dmi.board.name: 3323REG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3323REG:pvrThinkPadX201:rvnLENOVO:rn3323REG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3323REG
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu4
version.ia32-libs: ia32-libs 20090808ubuntu13
version.libdrm2: libdrm2 2.4.25-2ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.3-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.3-0ubuntu4
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu5
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1
Hey pitti,
Hi, thanks for reporting this issue during the development period of
Ubuntu.
I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?
Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?