Addison | # 11 | 2009-12-04, 09:52 | Report

Awesome!

Thanks for looking at testing this Nick!

You just became my new, personal *head shot*

JustNick | # 12 | 2009-12-04, 10:14 | Report

It does work after rebooting indeed!

Oh crap, too good to be true It works just the first time Xkbd is executed, then everything is capslocked

---

Last edited by JustNick; 2009-12-04 at 10:17.

Addison | # 13 | 2009-12-04, 10:29 | Report

Okay.

If you're using any of my old keyboards, they won't work anymore. They'll be broken now.

Old keyboard layouts

If not, again, the Caps Lock flag has always carried over for some reason.

To resolve, press Caps Lock, close Xkbd and then fire it up again. That should do it.

Even if you have Caps Lock on with the hildon keyboard when you close it, it will still have the same result the next time you use the hildon keyboard.

Post a response if you're back to being golden again after doing this.

---

Last edited by Addison; 2009-12-04 at 10:33.

JustNick | # 14 | 2009-12-04, 10:57 | Report

Here what I did:
1) completely removed xkbd
2) followed linuxeventually post -> everything was capslocked
3) rebooted and launched xkbd -> no caps lock
But unfortunately every time xkbd is executed beside the first time the result is quite the same: capslocked letters with unpredictable output (ie pressing Q gives T or something like that...)
Doing what you just told me to do killed my Dpad too
I guess I'll start over

Addison | # 15 | 2009-12-04, 12:18 | Report

Hey Nick, you're killing my good mood.

Yeah, the results you got were the way it used to be for the past two years. This is why I'm very happy to at least resolve this on my end.

Up, down, left and right on the D-Pad made outputs of the letters a,b,c and d if something went sour.

Not only that but the touch screen weirded out completely and I needed to do a full reboot to correct it.

I've had similar crashes of at least 50 times.

My suggestion was to only type the letter "a", if that turned out as a capital letter, it didn't work and you need to close Xkbd immediately.

I guess we're still testing this theory.

I don't get why you were banging on the keyboard with the letter "q" if you didn't first try with "a". The "a" key seems to be the safest to test.

Well, so far we're looking at 3 out of 4 success stories on this.

If you're a stupid idgit, I'll change those numbers back to 3 out of 3. *lol*

Edit:
Xkbd is not the problem. There should be no benefit at all from uninstalling and then reinstalling it again.
It has something to do with the hildon keyboard only.
We just need to figure out what that is.





Thanks for posting your problem though. It did seem strange that disabling and then immediately enabling the hildon keyboard had anything to do with Xkbd's ability to function correctly.

So yeah, not sure what to say on this.

It worked 3 times straight before your dumb *** arrived.

Hey Nick, can you write back if it works and note any changes on what you did from the previous time of testing?

Thanks

---

Last edited by Addison; 2009-12-04 at 12:25.

linuxeventually | # 16 | 2009-12-04, 12:40 | Report

Hmmm strange. I tested it on a clean install, what about you?

Mind you I did not open xkbd until AFTER I had run the gconftool parameter, so I don't know if there was caps lock at all in the first place. I'll try it on another install momentarily, right now I just figured out why keymouse never worked for me, so testing that now....

However, after using xkbd the hildon finger keyboard refused to come up even after passing the gconftool parameter to tell it the slider wasn't open.

I wonder also if there is something related to N810 vs N800 going on, but I sorta doubt it.

JustNick | # 17 | 2009-12-04, 13:08 | Report

I'm not sure if this can be listed as success...
After having the dpad killed I pasted the gconftool command in a terminal as root and, right before pressing enter, I kept pressed the shift to have capslockenabled... and voilà: non only the dpad returned functional, but now the a in xkbd is in lower case
I exited right away (no q this time ), but it seems to work...
I'm not sure I want to reboot and try again ,though

Addison | # 18 | 2009-12-04, 22:36 | Report

Nice one Nick!

Whenever Xkbd would take a dump on me before, my only option was to reboot the tablet since killall xkbd didn't do a thing.

That took some serious courage to run those commands as root. You're a wild one!

Okay, here's the same keyboard layouts with the fixed coding.
Keyboards.zip

Only use them if you're 100% sure Xkbd is working correctly.

There's no longer a Caps Lock button, now it's just a shift button instead.

The Notes file has the command lines on how to launch each of them.

The "Side" keyboard is for portrait mode.

Linux dude, any ideas yet on what exactly is occurring by running those two commands together?

Cheers!

Addison | # 19 | 2009-12-06, 02:46 | Report

Okay! Renewed hope once again!

There's a newer version I found on the net.

All I did was
root
cd /media/mmc2
dpkg -i xkbd_0.8.16-1_armel.deb

I rebooted since I wasn't getting either the ' or " keys working both before and after the new install.

I think this new version fully works without doing that whole gconftool trick!

Can someone also test this?

Xkbd

shin | # 20 | 2009-12-06, 14:22 | Report

Addison - Would the installation of xkbd break the virtual key board on my N810 or I can select to use them both in tandem..
I can install and check this out, but don't want to go through the hassles of uninstallation, etc if it would break the N810's stock Virtual key board ( big finger friendly KB) I like.

- Shin