[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Creating a chroot for cross-building lmi
From: |
Greg Chicares |
Subject: |
Re: [lmi] Creating a chroot for cross-building lmi |
Date: |
Sat, 24 Sep 2016 13:47:16 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0 |
On 2016-09-24 13:20, Greg Chicares wrote:
[...]
> https://help.ubuntu.com/community/BasicChroot#Accessing_graphical_applications_inside_the_chroot
> | You can run graphical applications within a chroot, but you need to
> | provide an X server for them to run in first. ... in the chroot shell type
> | export DISPLAY=:0.0
> | And in the system shell type
> | xhost +
>
> [Actually, I used 'xhost +local:' instead, for security.]
>
> However, now I think that's unnecessary--I just tried this:
>
> (host) $xhost -
> access control enabled, only authorized clients can connect
>
> (guest schroot) $unset $DISPLAY
> (guest schroot) $wine ./lmi_wx_shared.exe --ash_nazg --data_path=../data
>
> and lmi's GUI worked. Am I missing something?
Yes--this:
> (guest schroot) $unset $DISPLAY
should have been:
(guest schroot) $unset DISPLAY
without the last dollar sign. After running the corrected command:
$wine ./lmi_wx_shared.exe --ash_nazg --data_path=../data
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
So $DISPLAY does indeed need to be set, but apparently no xhost liberalization
is necessary.
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], (continued)
Re: [lmi] Creating a chroot for cross-building lmi, Greg Chicares, 2016/09/24