XO Frame key shows odd pop-up menu not frame (SoaS1 & SoaS3 on XO nand)

[garycmartin]

Pressing the XO frame keyboard shortcut under SoaS1 displays an unexpected pop-up menu unrelated to frame use (matches right clicking the search input area).

[erikos]

Ok, this is XO specific, could be that the keyboard has not been recognized correctly. alt-shift-f does work fine I presume?

[garycmartin]

Using xev on a SoaS3 image running on an XO; when pressing the XO frame key, the KeyPress event is showing keycode 135 (keysym 0xff67, Menu). When testing xev on a working 8.2 XO image, there is no KeyPress event getting through for the XO frame key so it's getting (correctly) intercepted further up the event chain. Erikos suggests it's possibly the XO keyboard is not being correctly recognised by SoaS.

[garycmartin]

Alt-Shift-F does correctly reveal the frame on SoaS3, just not the custom XO frame key.

[mtd]

Believe this is already reported upstream (in Fedora):
 https://bugzilla.redhat.com/show_bug.cgi?id=468744

Some links for reference:

 http://wiki.laptop.org/go/OLPC_English_Keyboard
 http://lists.freedesktop.org/archives/hal/attachments/20081104/4d02b69c/attachment.wsdl
 http://www.nabble.com/OLPC-XO-1-keymap-td20332819.html

[skierpage]

I believe the olpc XKB tables map the XO-1 Frame key to XF86TaskPane (see  http://wiki.laptop.org/go/Enabling_XO_features_on_other_distributions), I think that's why it brings up a context menu in other window managers. I'm not sure why that no longer works to bring up the Sugar Frame.

[mtd]

This is fixed in my soas-devxo branch (and my XO running a build thereof on NAND) thanks to unmanindu and pgf. sdziallas is aware of the fix and testing it in SoaS.

[garycmartin]

I'll need to retest this on an XO.

[garycmartin]

Testing on an XO-1 with xo-rawhide build (20090528) from cjb, the frame key is now correctly revealing/hiding the frame :-) Hoping Soas also has this fix (I haven't managed to get Soas to boot off XO-1 nand yet) [must try harder].

[mtd]

Yes, Soas has this.

[sdz]

As stated, fedora-xo already has the fix, and I'm going to announce a new devxo (soas for the xo) version in the very near future, which also includes it. Sounds like we're good to close that one now. Thanks for the great work!