I've followed the instructions at that link (thanks for sending, Ling) but
I've hit a failure point at Step 5 (Test the target image UI on the
workstation -- which for me is the final goal, so it's not really an
optional step).
When I run ume-xephyr-start per the instructions, I get this:
======================================
Setting screen resolution to 1024x600
Setting DISPLAY=:0
Starting dbus
* system message bus already started; not starting.
Starting UI in Xephyr
error opening security policy file /etc/X11/xserver/SecurityPolicy
Extended Input Devices not yet supported. Impelement it at line 625 in
../../../../hw/kdrive/src/kinput.c
sh: /usr/bin/xkbcomp: not found
Could not init font path element /usr/share/fonts/X11/misc, removing from
list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing
from list!
Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled,
removing from list!
Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled,
removing from list!
Could not init font path element /usr/share/fonts/X11/Type1, removing from
list!
Could not init font path element /usr/share/fonts/X11/100dpi, removing from
list!
Could not init font path element /usr/share/fonts/X11/75dpi, removing from
list!
Could not init font path element
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
Fatal server error:
could not open default font 'fixed'
XIO: fatal IO error 104 (Connection reset by peer) on X server ":2.0"
after 0 requests (0 known processed) with 0 events remaining.
It appears that the UI or Xephyr did not start
Note 1: Make sure that dbus is started successfully
Note 2: Make sure you have enabled control access on DISPLAY :0
Example (run on workstation terminal): xhost +SI:localuser:root
====================
OK, so Notes 1 and 2 at the end are not relevant -- the output above confims
dbus is already started; and I have run the command from Note 2 on the
workstation terminal before trying ume-xephyr-start per the instructions.
So, it seems like there are multiple other problems; where do I begin to
tackle them?
Thanks,
RL
On 3/18/08 8:10 PM, "Yu, Ling L" <[EMAIL PROTECTED]> wrote:
> If you are trying create a image or playing with the image creator,
> recommend you to read
> http://www.moblin.org/documentation_howto/howto_create-image.php which a
> good start point.
>
> Thanks
> - Ling
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Rob Lifford
> Sent: Wednesday, March 19, 2008 6:23 AM
> To: ubuntu-mobile@lists.ubuntu.com
> Subject: test-running the UI
>
> Hi all; just joined the list as I'm eager to see what's in store with
> UME.
>
> I'm following the directions here, just hoping to test-run the UI:
>
> https://wiki.ubuntu.com/MobileAndEmbedded/CreatingAnImageForUMEDevice
>
> It's easy to follow until I reach the "Choose a Functional Set" section.
> My
> issues:
>
> 1. I can't seem to find any documentation to help me choose which
> functional
> set I should choose for my purposes -- I'm fine assuming that
> "samsung-full-mobile-stack," as shown in the example is most
> appropriate,
> but please correct me if I'm wrong or point me toward more info on this
>
> 2. At the end of this section I come to this: "...we can use the
> Terminal
> button to open a chrooted terminal and run the hildon environment
> directly
> in a Xephyr session." How? I got Xephyr installed but I don't really
> understand its README well enough yet to know how to actually make
> UME/Hildon run in it. I'm trying to figure it out myself but hoping
> someone
> on the list can help set the context better for all this, because it's
> is
> all new stuff for me.
>
> Thanks,
> Rob
>
--
Ubuntu-mobile mailing list
Ubuntu-mobile@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
