Project

General

Profile

Bug #116

@ character in auto-type with cf keyboard layout

Added by Charles Brunet almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Operating System:
Linux
Affected version:
Affected revision:

Description

I realized that is not typed when I use auto-type on my system. However, if I switch keyboard layout to us, then it works. On cf keymap, is produced using AltGr + 2 . My system is on Ubuntu 13.10. I'm not sure if the bug is in keepassx itself, or in the used X11 library. Other character typed using AltGr modifier seem to work (e.g. ± produced by AltGr + 1.


Related issues

Duplicated by Bug #143: Auto-type function broken for some characters with some keymaps Closed 01/11/2014

Associated revisions

Revision 4549c97e
Added by Felix Geyer almost 4 years ago

Merge branch 'bug-116-autotype-single-keycode' of github.com:AlbertWeichselbraun/keepassx

https://github.com/keepassx/keepassx/pull/32

Closes #116

History

#1 Updated by Felix Heinz almost 4 years ago

Charles Brunet wrote:

I realized that is not typed when I use auto-type on my system. However, if I switch keyboard layout to us, then it works. On cf keymap, is produced using AltGr + 2 . My system is on Ubuntu 13.10. I'm not sure if the bug is in keepassx itself, or in the used X11 library. Other character typed using AltGr modifier seem to work (e.g. ± produced by AltGr + 1.

I have the same problem under Fedora 19 with Gnome-Desktop and KeepassX 2.0 Alpha 4. I use a german keymap and the @ is being pasted as 1/2.

#2 Updated by Felix Geyer almost 4 years ago

I could reproduce the problem.
"~" is another char that is typed incorrectly.

This seems to only happen when multiple keyboard layouts are set.
After "setxkbmap de" auto-type works fine, with "setxkbmap de,us" it breaks.

#3 Updated by Felix Heinz almost 4 years ago

I can confirm that setting "setxkbmap de" solves it temporarily.
I'm going to use this for me as workaround till it's fixed in a newer version.
Thank you for the hint.

#4 Updated by Albert Weichselbraun almost 4 years ago

The following pull request should fix the problem:
https://github.com/keepassx/keepassx/pull/28

#5 Updated by Felix Geyer almost 4 years ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed

#6 Updated by Felix Geyer almost 4 years ago

  • Target version set to 2.0 Alpha 5

Also available in: Atom PDF