[Damien]

Hi,

I noticed today that a randomly generated password using special characters is not auto-typed correctly:

8Bc9I?U1G ==> 8Bc9IU1G (the question mark is gone)

I'm running KeePass 2.16 on Ubuntu 11.04, xdotool version 2.20100818.3004

can't reproduce that on 11.04 with xdotool 1:2.20100701.2961-3ubuntu1 and 1:2.20110530.1-3
In which application are you typing?
does:
xdotool type "8Bc9I?U1G"
also drop the questionmark?
which keyboard layout are you using, do you have more than one keyboard layout listed in keyboard preferences -> layout? are you using two channel autoobsfuscation?

does it happen with keepass and xdotool from this ppa?
https://launchpad.net/~jtaylor/+archive/keepass

Hi Julian,

Actually, I used your package to install keepass (btw, thanks for building and making it available !).

I tried to auto-type this into firefox (it was a pw for a web site), but I get the same results auto-typing into a text editor (tried gedit and scite), which is how I noticed the problem (the web site would just complain about a wrong password).

Using copy/paste from Keepass works fine.

> does:
> xdotool type "8Bc9I?U1G"
> also drop the questionmark?

$ xdotool type "8Bc9I?U1G"
8bC9i^[u1g$ 8bC9i1g

The output is quite strange - as you can see the , and the string is repeated as a command after the $ prompt.? gets converted to "^[" (looks like some sort of escape sequence), the letters' case is toggled. Without the ?, all is fine:

$ xdotool type 8Bc9IU1G
8Bc9IU1G$ 8Bc9IU1G

Similar results with a simple test case (note that "something" is typed, because I need to press enter twice to get back to the prompt):

$ xdotool type ?
^[$

My keyboard layout is Switzerland French, and that's the only one I have setup.

I was not using 2-channel obfuscation before, but I just tried it and I get the same results.

Hope this helps.
Damien

this is probably a xdotool issue then.
I still also can't reproduce it with your keyboard layout.
does:
xdotool key question
print a questionmark?

Yes it does:
$ xdotool key question
$ ?

> this is probably a xdotool issue then.
Maybe it would be more appropriate if I opened an issue on the xdotool tracker ?

http://code.google.com/p/semicomplete/issues/detail?id=55