Thank you both for your efforts! I finally had some time to look at it again:
1.) Booting into the recovery mode results in the same, i.e. z and y are changed as well as other keyboard specific issues such as Umlaute (ä.ö etc.) do not work. 2.) Executing setkbmap - query in normal mode shows that the layout is ch - although it is obviously not. Note that the problem exists due to a post also in Arch Linux, with the same keyboard and German (de) layout. 3.) I could fix it by putting a *.desktop file into /usr/share/gnome/autostart, executing setxkbmap (full path was necessary, else it did not work), i.e.: [Desktop Entry] Type=Application Exec=/usr/bin/X11/setxkbmap ch Hidden=false X-GNOME-Autostart-enabled=true Name=setkeyboard I have in the meanwhile submitted this issue as a bug to Debian concerning package X11 - although it might concern another package. greetings, chris Am 19. März 2012 18:25 schrieb Kelly Clowers <kelly.clow...@gmail.com>: > On Mon, Mar 19, 2012 at 04:55, Christian Frey > <christian.frey...@gmail.com> wrote: >> OK, let's write it up properly ;) > > <snip> >> Then I attached the Logitech K340 USB keyboard, the keyboard >> works but the language settings don't, i.e. I have obviously a GB >> layout. The only way to change this so far is to use: >> >> setxkbmap ch >> >> After executing this commmand, everything works fine - in the terminal >> as well as in GNOME, meaning I have the proper layout (I know that >> there are specific problems with Wheezy and USB keyboards known, and >> it is suggested to activate Legacy support in the BIOS. I have first >> to check if I have this option in the BIOS at all. Remark: Ubuntu >> 10.10 does not have all these problems). >> >> 2.) My etc/default/keyboard looks ok: >> >> # KEYBOARD CONFIGURATION FILE >> >> # Consult the keyboard(5) manual page. >> >> XKBMODEL="pc105" >> XKBLAYOUT="ch" >> XKBVARIANT="" >> XKBOPTIONS="terminate:ctrl_alt_bksp" >> >> BACKSPACE="guess" > > <snip> > > Lets see, a couple of things to check. The /etc/default/keyboard file > sets the console as well, so you can try rebooting and choose to go > into single user mode (recovery mode). That way you can see if > something at a higher runlevel (in gnome or similar) is overriding it > or if it not applying in the first place. > > Another test would be to reboot and before running "setxkbmap ch" > run "setxkbmap -query", which will print the current setup. > > If it is ok at first, but gets overridden, we will have to track down > what is changing it. If it is not setting it correctly in the first place, > we need to figure out why. > > > Cheers, > Kelly Clowers > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: > http://lists.debian.org/CAFoWM=8+fKXTgO2y71=aVedhwRE1-ZiC=9je5cnl+itckcf...@mail.gmail.com > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cad5x0ead2+27tujdzoxgeco062nzl1z01p_x6grmp7cdxdn...@mail.gmail.com
