Keyboard sends <cr> (or <lf>?) after each symbol

jib · 08-06-2012, 01:51 AM

Let me first thank the developers here for all the wonderful software.

I've installed the GUI launcher, terminal emulator, networking tools, extend, and jbpatch. At some moment, the keyboard occasionally starts misbehaving - seemingly it starts issuing newline characters after each keystroke. This happens both with the native on-screen keyboard and in the xterm emulator keyboard. As a result I cannot type in any searches, and cannot also dump any logs in that state. Restart does help. Unfortunately so far I've been unable to pin down precise combination of events that triggers this misbehaviour.

Would be grateful for any advice on this.

jib · 08-15-2012, 01:58 AM

:sigh:

I realize it's not so easy to figure out, and by now I see I seem to be the only one with the problem...

Still - it was not quite correct what I wrote.

Native keyboard behaves as I wrote, however with the xterm emulator keyboard (and I meant the baf's one) it is different: in the mentioned state, when I invoke the emulator, what I see is a bunch of command prompts filling the whole height of the terminal area; after that, the commands can be actually typed in and executed, although I have to hit enter twice for each of them.

Still doesn't ring any bells?

knc1 · 08-15-2012, 04:16 AM

You are looking for two or more modifications that are causing the conflict over processing the keyboard events.

Uninstall everything, testing in-between each uninstall.
Install only one thing at a time, testing in-between each install.

The first uninstalled item that clears the problem is one of the conflicting items, the other one (or more) items are in the set of things not yet uninstalled.

The first installed item that results in the problem is one of the conflicting items, the other one (or more) items are in the set of things just installed.

Now you have identified one of the two (or more) conflicting installs.
And a (hopefully smaller) set of things that include what it conflicts with.

Revert to a "virgin" system (one without anything extra installed) -
Install the single item identified above, re-test.
Does the problem re-occur? Yes: that item conflicts with the system, No: that item conflicts with the identified small set of other items.

With the one identified item installed, and the trials limited to the smaller set of items; repeat the above.

Keep good notes, let us know what you find out.

silver18 · 08-15-2012, 04:52 AM

I don't know if it's the same problem....
I used prompts in my WAF and I found that the space button acts like the return button, i.e submits the prompt instead of adding space.

08-06-2012, 01:51 AM	#1
jib Member Posts: 11 Karma: 550 Join Date: Aug 2012 Location: Tbilisi, Georgia (GE, not GA) Device: Kindle Touch 5.1.2	Keyboard sends <cr> (or <lf>?) after each symbol Let me first thank the developers here for all the wonderful software. I've installed the GUI launcher, terminal emulator, networking tools, extend, and jbpatch. At some moment, the keyboard occasionally starts misbehaving - seemingly it starts issuing newline characters after each keystroke. This happens both with the native on-screen keyboard and in the xterm emulator keyboard. As a result I cannot type in any searches, and cannot also dump any logs in that state. Restart does help. Unfortunately so far I've been unable to pin down precise combination of events that triggers this misbehaviour. Would be grateful for any advice on this.

08-15-2012, 01:58 AM	#2
jib Member Posts: 11 Karma: 550 Join Date: Aug 2012 Location: Tbilisi, Georgia (GE, not GA) Device: Kindle Touch 5.1.2	More precisely... :sigh: I realize it's not so easy to figure out, and by now I see I seem to be the only one with the problem... Still - it was not quite correct what I wrote. Native keyboard behaves as I wrote, however with the xterm emulator keyboard (and I meant the baf's one) it is different: in the mentioned state, when I invoke the emulator, what I see is a bunch of command prompts filling the whole height of the terminal area; after that, the commands can be actually typed in and executed, although I have to hit enter twice for each of them. Still doesn't ring any bells?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre sends by email only one format	frandav	Library Management	2	02-09-2012 01:59 PM
Calibre sends AZW instead of MOBI by email	rfog	Calibre	6	12-07-2011 02:12 PM
Sending books via email, the second book never sends	MrTissues	Calibre	1	12-27-2010 02:34 AM
Amazon sends out Kindle ad disguised as a press release	Nate the great	News	12	11-30-2009 12:34 PM
2nd Reader sends me down the rabbit hole	Penforhire	Sony Reader	3	12-31-2007 05:00 PM

08-15-2012, 04:16 AM	#3
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	You are looking for two or more modifications that are causing the conflict over processing the keyboard events. Uninstall everything, testing in-between each uninstall. Install only one thing at a time, testing in-between each install. The first uninstalled item that clears the problem is one of the conflicting items, the other one (or more) items are in the set of things not yet uninstalled. The first installed item that results in the problem is one of the conflicting items, the other one (or more) items are in the set of things just installed. Now you have identified one of the two (or more) conflicting installs. And a (hopefully smaller) set of things that include what it conflicts with. Revert to a "virgin" system (one without anything extra installed) - Install the single item identified above, re-test. Does the problem re-occur? Yes: that item conflicts with the system, No: that item conflicts with the identified small set of other items. With the one identified item installed, and the trials limited to the smaller set of items; repeat the above. Keep good notes, let us know what you find out.

08-15-2012, 04:52 AM	#4
silver18 THE NOOB Posts: 701 Karma: 1545649 Join Date: Jan 2012 Location: Italy Device: Kindle Touch 5.3.2	I don't know if it's the same problem.... I used prompts in my WAF and I found that the space button acts like the return button, i.e submits the prompt instead of adding space.