Your message dated Sun, 13 Oct 2013 14:18:15 -0500 with message-id <87zjqd9dzc....@earlgrey.lan> and subject line Duplicate of #726242 has caused the Debian Bug report #726244, regarding python-xdo: Wrong output given for US querty input to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 726244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: python-xdo Version: 0.2-2 Severity: grave Hello, I recently discovered that all of my passwords in assword were being substitution ciphered without my knowledge! Hence the "grave" rating here, this has the risk for any assword users of them creating a database of passwords that don't match the passwords they're creating on various services. I found that while many characters did enter their proper characters on a US Querty keyboard, the following did not: ,<LPlp'/?CG[cg{".>FNfnY]y} instead map to: wWPRprq[{IU-iu_QeEYLylT=t+ With the help of Simon Fondrie-Teitler we figured out that there is a small amount of pattern to this: <simonft> wWPRprq[{IU-iu_QeEYLylT=t+ <simonft> paroneayea: I just typed that string when my keyboard was in qwerty as if it were in dvorak <simonft> paroneayea: it's also just the top row of dvorak <simonft> and the two keys to the right of the number keys Which leaves me wondering if I should blame the large number of dvorak users in Debian for the cause of this bug. ;) The only "strange modification" to my keyboard setup software-wise that I know of is that I have caps lock bound to control in Gnome.... no idea how that could affect this though. I'm not certain if this is a python-xdo bug or a libxdo/xdotool bug... please move if appropriate! Thank you very much! PS: Apologies if I somehow opened this bug multiple times, I am having weird errors with debian-el combined with mu4e. :\ -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-xdo depends on: ii libc6 2.17-93 ii libxdo3 1:3.20130111.1-3 ii python 2.7.5-5 python-xdo recommends no packages. python-xdo suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Apologies! I had some errors in mu4e mixing with debian-el.
--- End Message ---
