David Fellows <fellows@unb.ca> skribis:
> To run gnucash  I start an sshd service in the chroot listening on port 2232
> ( and leave it running indefinitely). SSHD is configured to do X forwarding.
> You do NOT start the X server in the chroot.
> In 64 bit I created a /home/me/home32 directory in my 64 bit home directory
> /home/me. Then I made /home available to the chroot.
> As per the the 32 bit chroot instructions I created a user id for myself that
> matches the 64 bit UID with home directory /home/me/home32.
> I also had to set up the ssh  keys, known hosts files, etc.
> 
> Then I use the command 
> ssh -X -p2232 localhost
> to connect to the chroot
> and execute gnucash.
> 
> I have discovered that not all X clients are happy to talk to an X server that
> is running on a machine with a different word size.  This is not chroot 
> specific and it affects both 32 bit client to 64 bit server and 64 bit client 
> to 32 bit server.  My short list, from experience is
>   gnome xterm - OK 
>   emacs - dies on first mouse click
>   xeyes - OK
>   gnucash - spews a steady stream of X errors/warnings, but does its thing.
> 	  (sometimes you are lucky)
>   wine - dies on startup IRCC

I think those may be problems with ssh's X forwarding.

You don't need to use ssh. If you make the tmp directories for the
chroot bind-mounts to the outer tmp directories, then X can make Unix
domain socket connections. You can run X clients from inside the
chroot, then.



-- 
Barry.SCHWARTZ@chemoelectric.org   http://www.chemoelectric.org
Esperantistoj rajtas skribi al Barijo.SXVARCO@chemoelectric.org
     'We're going to have a temporary disruption
      of gasoline product.' -- George W. Bush