Can't input characters {[]}|@€ with German quertz-Keyboard

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Type @ or | on German quertz-Keyboard doesn't put any character in
Terminal. (All this Chars need the AltGr-Key pressed)

What is the expected output? What do you see instead?
- { or [ or ] or } produces beep
- @ or € or | produces nothing
- @@ produces "Display all possibilities?"

What version of the product are you using? On what operating system?
- shellinabox 2.8 self compiled on a
- debian lenny with kernel 2.6.26

Please provide any additional information below.

Original issue reported on code.google.com by WoBaumga...@gmail.com on 12 Jun 2009 at 11:29

[GoogleCodeExporter]

Can you try to provide more information, so that I can attempt to reproduce the
problem. In particular, can you tell me exactly which browser you are using? I
enabled the German keyboard layout on my Debian unstable system, and everything 
works
just fine. When I open http://www.shellinabox.com in Firefox and type in the 
little
demo application, I can use AltGr to enter @, €, {, [, ], } and other keys.

Also, please include both the version and the revision number of ShellInABox. 
You can
see the latter by right-clicking into the window. There is an About menu. 
Maybe, your
browser is still caching an older version?

Original comment by zod...@gmail.com on 17 Jun 2009 at 11:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

In Firefox 3.0.10 on Windows XP German I can use some Keys with AltGr, so "\" 
and
"~", but not in IE 7.0.5730.13

Shellinabox is 2.8 Revision 121

Same behavior on your Test-Shellinaboxscript at http://www.shellinabox.com 
(Shows me
Shellinabox 2.8 Revision 126): in IE 7 no key with AltGR puts an character, in
Firefox 3 only "~" and "\" are able.

Original comment by WoBaumga...@gmail.com on 22 Jun 2009 at 6:24

[GoogleCodeExporter]

Can you try again? I just checked another fix into SVN that should work around 
these
problems.

Original comment by zod...@gmail.com on 30 Jun 2009 at 5:15

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Perfect, you did a good job and it's a wonderful tool.

Thank you
Buxul

Original comment by WoBaumga...@gmail.com on 2 Jul 2009 at 1:15

[GoogleCodeExporter]

Original comment by zod...@gmail.com on 2 Jul 2009 at 4:21

• Changed state: Fixed

[GoogleCodeExporter]

I'm experiencing a similar problem using 2.9 (rev. 139). I have a swedish 
keyboard, 
accessing the server from a Windows XP-system. 

Under Google Chrome (2.0.172.39) I can't produce any of the AltGr dependent 
characters, such as |@£$€{[]}\ 

When using Internet Explorer all of the characters are available -- except the 
pipe-
character (|). I've managed to produce the pipe character once, just after 
login, but 
after this initial success, it's been impossible to reproduce this character. 

The above seems to apply to the demo application as well.

Original comment by cody.cus...@gmail.com on 6 Aug 2009 at 8:30

[GoogleCodeExporter]

I need to figure out how to enter Swedish and then I'll hopefully be able to 
reproduce 
(and fix) your problem.

Original comment by zod...@gmail.com on 6 Aug 2009 at 6:04

• Changed state: Accepted

[GoogleCodeExporter]

Thanks! Please get in touch if I can assist you in any way.

(And thanks again for the great work with shellinabox! It's extremely useful to 
me.)

Original comment by cody.cus...@gmail.com on 7 Aug 2009 at 8:13

[GoogleCodeExporter]

I am a little puzzled here. I added the Swedish keyboard layout to Windows XP, 
switched to it, and then accessed ShellInABox from Chrome. I can successfully 
enter 
{[]}, if I press AltGR and 7, 8, 9, 0. I cannot enter | on my US keyboard as it 
is 
missing one key. But if I connect a German keyboard, < > and | are there.

Maybe, I inadvertently fixed it somehow? Or you are doing something different? 
Or 
maybe, you are using an older version of Chrome. I usually track the dev 
channel. So, 
I might have a newer version than you. Of course, that wouldn't explain why you 
had 
problems in IE.

Can you please try if the problem still exists in the newest SVN revision and 
if so 
give step by step instructions on how to reproduce it?

Original comment by zod...@gmail.com on 9 Aug 2009 at 12:09

[GoogleCodeExporter]

I discovered that the version of Chrome I was using at work (where I ran into 
this 
problem) was ancient. So this explains things. Back at home, using a more 
recent 
Chrome build (3.0.196.0) everything seems to work fine. So the issue with 
Chrome 
seems to be fixed.

Using Internet Explorer (7.0.5730.13), though, the bug behaves as follows:

When I first start Shellinabox there are no problems; I can produce the | by 
using 
the combination AltGr-< on the Swedish keyboard. But, if I press AltGR together 
with 
any other key which doesn't produce a character (For example AltGr-1, AltGr-6, 
AltGr-
§, AltGr-[A-Z]) the bug is "activated". After this the | stops working. If I 
close 
down the browser window completely and then open a fresh Shellinabox session 
the 
functionality will be restored -- until it is triggered again, by pressing (for 
example) AltGr-1.

I still haven't tried this procedure with the latest SVN-version. I'll try and 
build 
it later today and report if I find anything new.

Original comment by cody.cus...@gmail.com on 10 Aug 2009 at 7:17

[GoogleCodeExporter]

Update: I've checked out the latest revision (164), and the behaviour in IE is 
identical.

Original comment by cody.cus...@gmail.com on 11 Aug 2009 at 7:04

[GoogleCodeExporter]

Thank you for doing all these tests for me. If this problem only occurs after 
you 
entered "|" for the first time, that sounds as if something is wrong with the 
logic 
that handles "catchModifiersEarly".

I need to dig out the German keyboard again, and start up IE to find the 
correct 
solution for the problem (i.e. a solution that doesn't break anything else). 
Most 
likely, it's going to be a small but subtle change. It could take a few days 
though, 
before I get to this.

But for the time being, you could try commenting out the line that sets 
"this.catchModifiersEarly" to "true". If you are lucky, that will already fix 
it for 
you. It's not quite ideal, as this change can break some other behavior, but it 
would 
be nice to know if this change makes a difference.

Original comment by zod...@gmail.com on 11 Aug 2009 at 7:16

[GoogleCodeExporter]

Thanks! I tried the fix, but it didn't work -- same behaviour as far as I can 
see.

"...If this problem only occurs after you entered '|' for the first time..."

Just to clarify: the problem does not occur until I press AltGr together with a 
"useless" key -- that is, a key combination which doesn't produce (and isn't 
supposed 
to produce) a particular character entity. Like, for example, AltGr and 
together with 
[A,B...Z] or AltGr-[1,6].

Thus, I can enter "|" any number of times *until* I press AltGr together with 
any of 
these "offending" combinations. After this AltGr-< yields nothing and it's 
impossible 
to produce the pipe-character in the terminal without a cut and paste operation.

Original comment by cody.cus...@gmail.com on 11 Aug 2009 at 9:22

[GoogleCodeExporter]

I did a bunch more testing, and I now treat the "<>|" key as if it is a regular 
alphanumeric key. That seems to fix the problem, as far as I can tell. I hope, 
it 
doesn't introduce any problems on other keyboard layouts.

Original comment by zod...@gmail.com on 11 Aug 2009 at 6:40

[GoogleCodeExporter]

Can you let me know, if the bug is fixed now? My testing does suggest that it 
is, but
not knowing how Swedish keyboards are supposed to behave, my testing is 
naturally a
little limited.

Original comment by zod...@gmail.com on 20 Aug 2009 at 8:46

[GoogleCodeExporter]

Original comment by zod...@gmail.com on 21 Aug 2009 at 4:39

• Changed state: Fixed