#1000 can't autotype @ with german keyboard setting

open
Linux (85)
5
2015-03-10
2011-11-18
Dan42
No

Ubuntu 11.04 with pswdsafe 0.7 (4492) beta cant autotype @ sign:

Perform autotype with email adress "user@domain.com". The target window receives "userQdomain.com". So instead of "@", a "Q" is received.

I suspect it has something to do with the "AltGr"- Key on the german keyboard, which is required to enter a "@" sign: "AltGr-q" results in "@", so probably this key modifier is missing.

uname -a: Linux dfroehli-laptop 2.6.38-11-generic-pae #50-Ubuntu SMP Mon Sep 12 22:21:04 UTC 2011 i686 i686 i386 GNU/Linux
echo $LANG: de_DE.UTF-8
Keyboard input method system: ibus
Languages for menus and windows: English, German
Keyboard layout: Germany
Keyboard model: Generic 105-key (intl) PC

Discussion

  • Saurav Ghosh

    Saurav Ghosh - 2011-11-21

    You are probably right. The current autotype code is "hard-coded" for Latin-1 charset, and doesn't generate modifier keypresses other than "Shift". I can make a patch for you if you can test it, but I can't verify those changes since I don't have a German keyboard.

    What does "xev" show when you enter "@" using AltGr-q? Also, does Shift-q result in "Q" ( Uppercase Q)?

     
  • Mark McCracken

    Mark McCracken - 2011-11-21

    I use a Dvorak layout in 64-bit Arch, and I can confirm that what I get from Auto-Type is what I would get if I hunt-and-pecked at a keyboard labeled in Qwerty.

    Example: Intended password: "password". On a Dvorak layout and Qwerty labels, fingers would strike keys labeled "ra;;,soh". Auto-typing this password in 64-bit Arch with a Dvorak layout does in fact yield "ra;;,soh".

    System info:

    $ uname -a
    Linux arch64test 3.1.1-1-ARCH #1 SMP PREEMPT Fri Nov 11 22:28:29 CET 2011 x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
    $ echo $LANG
    en_US.UTF-8
    $ grep -B5 -A1 XkbLayout /etc/X11/xorg.conf.d/10-evdev.conf
    Section "InputClass"
    Identifier "evdev keyboard catchall"
    MatchIsKeyboard "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "XkbLayout" "dvorak"
    EndSection
    $ grep ^KEYMAP /etc/rc.conf
    KEYMAP="dvorak"

     
  • Dan42

    Dan42 - 2011-11-23

    I would be happy to test a patch. Yes, Shift-q does result in "Q".

    xev output for "@" entered:

    KeyPress event, serial 36, synthetic NO, window 0x2400001,
    root 0xb9, subw 0x0, time 4808873, (108,86), root:(112,135),
    state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XKeysymToKeycode returns keycode: 92
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

    KeyPress event, serial 36, synthetic NO, window 0x2400001,
    root 0xb9, subw 0x0, time 4809056, (108,86), root:(112,135),
    state 0x80, keycode 24 (keysym 0x40, at), same_screen YES,
    XLookupString gives 1 bytes: (40) "@"
    XmbLookupString gives 1 bytes: (40) "@"
    XFilterEvent returns: False

    xev output for "q" entered:
    KeyPress event, serial 36, synthetic NO, window 0x5200001,
    root 0xb9, subw 0x0, time 5175907, (103,82), root:(107,131),
    state 0x0, keycode 24 (keysym 0x71, q), same_screen YES,
    XLookupString gives 1 bytes: (71) "q"
    XmbLookupString gives 1 bytes: (71) "q"
    XFilterEvent returns: False

    xev output for "Q" entered:
    KeyPress event, serial 36, synthetic NO, window 0x5200001,
    root 0xb9, subw 0x0, time 5276146, (118,90), root:(122,139),
    state 0x0, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

    KeyPress event, serial 36, synthetic NO, window 0x5200001,
    root 0xb9, subw 0x0, time 5277024, (118,90), root:(122,139),
    state 0x1, keycode 24 (keysym 0x51, Q), same_screen YES,
    XLookupString gives 1 bytes: (51) "Q"
    XmbLookupString gives 1 bytes: (51) "Q"
    XFilterEvent returns: False

     
  • Saurav Ghosh

    Saurav Ghosh - 2011-11-25

    I believe this (Q vs @) has been fixed in repository. Do you need a patch for the 0.7 beta code, or can you build it from svn HEAD?

    desade7 - can you please open another bug for the DVORAK vs. QWERTY issue? Its probably a different problem. Also attach what your "xmodmap -pk" shows, and the xev output when you type "password" on the DVORAK keyboard.

     
  • Dan42

    Dan42 - 2011-11-29

    I did build from svn trunk v0.7 (4600M) beta: still does not work.
    Behaviour has slightly changed: @ is now auto-typed as "q" (lower case) instead of "Q" (upper case) as it was in 4492.

     
  • Saurav Ghosh

    Saurav Ghosh - 2011-12-03

    I realize what the (additional) problem is. Need to build in support for XKB. But it will take me some time.

     
  • Saurav Ghosh

    Saurav Ghosh - 2011-12-05

    dan42n - which keyboard layouts are you using in Ubuntu 11.04? Can you please post the output from "xmodmap -pk" and "xmodmap" for those layouts?

     
  • Saurav Ghosh

    Saurav Ghosh - 2011-12-06

    Safe to test autotyping of @ char in German keyboard layout

     
  • Saurav Ghosh

    Saurav Ghosh - 2011-12-06

    Can you please update your svn sources to at least 4612, rebuild and try again?

    If you are using multiple keyboard layouts and have checked "Separate layout for each window" under Keyboard->Layouts, please make sure the German layout is active for both pwsafe and the autotype target window.

    If it still doesn't work for you, please let me know

    1. The exact keyboard layout(s) that are selected in "Keyboard Preferences -> Layouts", not just the one that is active. Also, there are several German layout variants in Ubuntu 11.04. Please let me know the exact one you're using.
    2. the outputs from "xmodmap" and "xmodmap -pk" with the particular German layout enabled.
    3. What you get if you try to autotype the single entry in attached natty.psafe3 (passphrase test123).

    I have tried various combinations of language & keyboard layout (German & English), with or without LANG being de_DE.UTF-8 (doesn't matter, I think), and the "@" char is autotyped correctly in all cases (since svn 4612), except if you have a char layout in which some chars being autotyped are not available in X keymap. Hence the request for output of xmodmap...

     
  • Dan42

    Dan42 - 2011-12-06

    Bingo! Build with 4613 and now '@' works! Many many thanks!

     
  • Saurav Ghosh

    Saurav Ghosh - 2011-12-07

    You're welcome. Thanks for filing the bug and the followup.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks