Bug#366615: xkb-data: This also is a problem with gb.

[Rob Andrews <rob@choralone.org>]

Package: xkb-data
Version: 0.8-6
Followup-For: Bug #366615

If you set the XkbModel to "macintosh_vndr", it doesn't actually set it
to that - it drops back to "pc105". You can see this behaviour with
setxkbmap:

nine@aphasia:~$ setxkbmap -rules xorg -model macintosh_vndr -layout gb -print
xkb_keymap {
        xkb_keycodes  { include "xfree86+aliases(qwerty)"       };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc(pc105)+gb+altwin(meta_win)+compose(rwin)"  };
        xkb_geometry  { include "pc(pc104)"     };
};

Versus:
nine@aphasia:~$ setxkbmap -rules xorg -model macintosh -layout gb -print
xkb_keymap {
        xkb_keycodes  { include "macintosh+aliases(qwerty)"     };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc(pc105)+macintosh_vndr/gb+altwin(meta_win)+compose(rwin)"    };
        xkb_geometry  { include "macintosh(macintosh)"  };
};

The aforementioned problem of setting the model to 'macintosh' also
manifests itself with the 'gb' layout.

If I run:
nine@aphasia:~$ setxkbmap -rules xorg -model macintosh -layout gb

I lose all of the letters - numbers work, some symbols work, but letters are
gone (and I have to scrabble through a few terminals to find a 'u' and
's' to paste by mouse into the command history to get the keyboard back!).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-amd64-k8
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

-- no debconf information