Upgrading console-setup in a chroot breaks X keymap
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| console-setup (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: console-setup
I've seen this frustrating problem before but couldn't identify the cause. Just seen it again now, and I think I've sussed it.
I'm using Maverick on amd64. I have a chroot setup for building things (natty amd64). Just after doing an upgrade in that chroot (using chroot in an xterm), my X keymap has just been broken. Normally to switch from X to a console, I need to use Ctrl-Alt-F<key>. Now, if I use Alt-<cursor left> (e.g. to go backwards or a page in Firefox) it appears that key combination is passed through X to the underlying console *and* to Firefox. So, I'm switched to VT6. When I switch back to X, Firefox has also gone back a page as instructed. I'm seeing similar effects with Alt-<cursor right> and Alt-<F key>, i.e. they're switching to the console.
Is this switching VT7 back out of raw mode?
| Steve McIntyre (steve-mcintyre) wrote | #1 |
In fact, that looks to be exactly the problem. In an xterm:
$ sudo kbd_mode
The keyboard is in Unicode (UTF-8) mode
On another machine, I get
$ sudo kbd_mode
The keyboard is in raw (scancode) mode