xpra icon
Bug tracker and wiki

Opened 6 years ago

Closed 6 years ago

#383 closed defect (fixed)

Xephyr + Xpra keyboard problem on Mac OS X 10.8

Reported by: roberto hashioka Owned by: roberto hashioka
Priority: minor Milestone: 0.11
Component: platforms Version: 0.9.x
Keywords: keyboard xephyr Cc:

Description

I'm starting a child with Xephyr on Linux xpra 0.9.7 and when I access it from my Mac v.0.9.6. The enter-key and the arrows doesn't work. If I start xpra without the child it works fine across Linux and Mac. Please check the logs attached.

I've noticed that the log with Xephyr, the xkb is not set with options keys.

Attachments (2)

10_with_Xephyr.log (5.9 KB) - added by roberto hashioka 6 years ago.
10.log (4.7 KB) - added by roberto hashioka 6 years ago.

Download all attachments as: .zip

Change History (20)

Changed 6 years ago by roberto hashioka

Attachment: 10_with_Xephyr.log added

Changed 6 years ago by roberto hashioka

Attachment: 10.log added

comment:1 Changed 6 years ago by roberto hashioka

Sorry, after checking again the logs. On both logs the option keys are being configured by xkb. So, should be something else.

Thanks.

comment:2 Changed 6 years ago by roberto hashioka

The command that I'm using is:

xpra start :10 \
   --start-child="Xephyr -ac -screen 1440x900 -query localhost \
       -host-cursor -reset -terminate :11" \
   --xvfb="Xvfb +extension Composite -screen 0 1440x900x24+32 -nolisten tcp \
       -noreset -auth /home/docker/.Xauthority"
Last edited 6 years ago by Antoine Martin (previous) (diff)

comment:3 Changed 6 years ago by roberto hashioka

Even if I set the xkb it doesn't work:

docker@9b5c0b4b7e54:~$ DISPLAY=:11 setxkbmap -rules evdev -model pc105 -layout us -option "terminate:ctrl_alt_bksp"
docker@9b5c0b4b7e54:~$ DISPLAY=:11 setxkbmap -query
rules:      evdev
model:      pc105
layout:     us
options:    terminate:ctrl_alt_bksp
Last edited 6 years ago by Antoine Martin (previous) (diff)

comment:4 Changed 6 years ago by roberto hashioka

Summary: Xephyr + XpraXephyr + Xpra keyboard problem on Mac OS X 10.8

comment:5 Changed 6 years ago by Antoine Martin

Keywords: xpra removed
Owner: changed from Antoine Martin to roberto hashioka
Priority: majorminor

Have you tried using Xephyr as your xvfb instead?

comment:6 Changed 6 years ago by roberto hashioka

No. How should I do that?

xpra start :10 --xvfb="Xephyr -ac -screen 1440x900 -query localhost -host-cursor -reset -terminate"

?

Last edited 6 years ago by roberto hashioka (previous) (diff)

comment:7 Changed 6 years ago by Antoine Martin

Never mind, this cannot work as Xephyr is itself an X11 client and therefore requires an existing X11 server to run.

So back to key mapping, you will have to tell Xephyr to use the same keymap as the Xvfb, see xmodmap and xkbcomp.

comment:8 Changed 6 years ago by roberto hashioka

I tried :

xkbcomp :10 :11

But it didn't work! On windows and on Linux the keyboard works fine, only on Mac that it happens!

comment:9 Changed 6 years ago by Antoine Martin

wiki/Keyboard may help you, but OSX support is not on the same level as the other platforms.

comment:10 Changed 6 years ago by Antoine Martin

As for xkbcomp, the usual way of doing it is to dump the keymap from setxkbmap -print to xkbcomp.

See http://www.x.org/releases/X11R7.7/doc/man/man1/setxkbmap.1.xhtml

comment:11 Changed 6 years ago by roberto hashioka

Do you think it is happening due the version? The most recent version on Mac is 0.9.6.

comment:12 Changed 6 years ago by roberto hashioka

Both xkb are the same. But the problem persists.

docker@9b5c0b4b7e54:~$ DISPLAY=:11
docker@9b5c0b4b7e54:~$ setxkbmap -print
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
docker@9b5c0b4b7e54:~$ DISPLAY=:10
docker@9b5c0b4b7e54:~$ setxkbmap -print
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
docker@9b5c0b4b7e54:~$

comment:13 Changed 6 years ago by roberto hashioka

ps ax 

 6020 ?        Sl     0:12 /usr/bin/python /usr/bin/xpra start :10 \
    --start-child=Xephyr -ac -screen 1440x900 -query localhost -host-cursor -reset -terminate :11 \
    --xvfb=Xvfb +extension Composite -screen 0 1440x900x24+32 -nolisten tcp -nore
 6021 ?        Ss     0:01 Xvfb-for-Xpra-:10 +extension Composite -screen 0 1440x900x24+32 \
    -nolisten tcp -noreset -auth /home/docker/.Xauthority :10
 6030 ?        S      0:00 dbus-launch --autolaunch 610097d84ec52199cdf0f8d751e75ea7 --binary-syntax --close-stderr
 6031 ?        Ss     0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
 6034 ?        S      0:00 /bin/sh -c Xephyr -ac -screen 1440x900 -query localhost -host-cursor -reset -terminate :11
 6035 ?        S      0:09 Xephyr -ac -screen 1440x900 -query localhost -host-cursor -reset -terminate :11
Last edited 6 years ago by Antoine Martin (previous) (diff)

comment:14 Changed 6 years ago by Antoine Martin

Having the same layout is not sufficient, you also need the same keymap:

xmodmap -pke

But even then, keyboard support in sharing mode is unlikely to work with heterogeneous clients - at least in current versions.

comment:15 Changed 6 years ago by roberto hashioka

I'm not using sharing mode any more are it still has some issues. I'm now connecting one by one separately. When I connect from the other machine, the previous one lose the connection.

comment:16 Changed 6 years ago by roberto hashioka

Yes, the keymap are different between :11 and :10. How can I change the mapping? Which is the best way of telling Xephyr to use the same keymap as Xvfb?

comment:17 Changed 6 years ago by roberto hashioka

Hi Antoine,

Now it's working! I created a file (xmodmap) from the Xvfb display and then I used it on the Xephyr's display! :)

comment:18 Changed 6 years ago by Antoine Martin

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.