[Bugs] #1075 NORM: Since the Sugar switch to Metacity, Sugar shell specific key shortcuts all fail
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Mon Oct 19 21:49:07 EDT 2009
#1075: Since the Sugar switch to Metacity, Sugar shell specific key shortcuts all
fail
----------------------------+-----------------------------------------------
Reporter: garycmartin | Owner: tomeu
Type: defect | Status: new
Priority: Normal | Milestone: 0.86
Component: sugar | Version: 0.85.x
Severity: Major | Keywords:
Distribution: Unspecified | Status_field: Unconfirmed
----------------------------+-----------------------------------------------
Comment(by DanKrejsa):
A couple of notes. I also see this running sugar-emulator under jhbuild on
Fedora 11.
The Xephyr version is
$ rpm -qa | grep Xephyr
xorg-x11-server-Xephyr-1.6.4-0.1.fc11.i586
so it's not just restricted to version 1.6.3.
I tried running the get_mapping.py script attached to the
[https://bugs.freedesktop.org/show_bug.cgi?id=23470]
bug report. I ran
python get_mapping.py
in an xterm in Xephyr, closing the xterm (only client of the Xephyr
server),
started a new xterm in the Xephyr server, and running 'python
get_mapping.py'
again; I see no difference in the keymaps that are printed out. The
keymaps
are not empty in either case. Maybe I'm misunderstanding how you meant to
run get_mapping.py? Also no difference in the keymaps if I just run
get_mapping.py twice in the xterm.
I did notice that if I delete
.sugar/default/gconf/desktop/sugar/user/%gconf.xml
before starting sugar-emulator, the function keys are handled properly and
the 'Keycode out of bounds' messages do not appear in shell.log. But if I
shut down sugar emulator and restart it, on the next run the function keys
stop working again.
That indicates that something is being done differently when
.sugar/default/gconf/desktop/sugar/user/%gconf.xml
needs to be created, which makes the sugar key bindings work; so probably
at
least a workaround is possible. (Possibly the interaction when one has to
reenter one's sugar name and choose one's colors is involved... I've seen
Xephyr key mapping issues in the past in which remapping operations failed
unless done after initial user interaction, not that I understand this
well.)
OK, one correction. I finally figured out how you meant get_mapping.py to
be run.
After closing all clients in the Xephyr server and setting the environment
variable
DISPLAY in an external shell to the Xephyr's display number, if I then run
'python get_mapping.py' twice, on the 2nd time all the mappings are 'None
None None None'.
BUT if I then start an xterm in the Xephyr server, and type a key in the
xterm,
and then go back to the external shell and run 'python get_mapping.py',
the
keycodes come back (no longer all 'None None None None'). Not sure what to
make
of this.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/1075#comment:9>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list