Dear Sirs,

I am taking advantage of your efforts in the mobile area to build a 
compact, minimal ubuntu LiveUSB system running on generic i386 PCs.

I am using MIC and created a project based on the mccaslin-lpia 
platform, with the custom fsets defined below:

[i386-Image]
DESC=Packages needed for the i386 platform (Generic i386)
PKGS=linux-image
DEBUG_PKGS=
DEPS=core

[Generic-X11]
DESC=Subset of X11 components
PKGS=xorg fluxbox
DEBUG_PKGS=
DEPS=i386-Image

This way I managed to have a live test image booting correctly and, by 
means of a proper xorg.conf, running X on Intel GPUs when launched with 
"startx" from the console both as root and as unprivileged user. Not bad 
considering the size of 120 MB in total and the superfast boot...

Now the challenge: I would like to start X as the unprivileged user 
during the boot sequence, so I tried using the "session" upstart script 
from Rusty:

----
# session
#
# This service is started automatically by init to kick off X

description     "session starting daemon"
author          "Rusty Lynch <[EMAIL PROTECTED]>"

start on runlevel 2
stop on runlevel [!2]

# Run as user
exec su -l luigi -c "/usr/bin/startx -- -config xorg-intel.conf"
# Run as roor
# exec /usr/bin/startx -- -config xorg-intel.conf
# respawn
-----

this way X tries to start upon booting the image, gets at the point of 
showing the cross cursor and then dies (both when run as root and as 
normal user), reverting at the console login prompt.

If I immediately login as root (or normal user) and execute

/usr/bin/startx -- -config xorg-intel.conf

I have a working graphical environment.

I have compared the two Xorg logfiles produced by X in these two 
circumstances and they are exactly the same (except for the time of 
execution), and the .xsession-errors is not produced when X is started 
from upstart.

Anyone having ideas on how to tackle this issue?

Best regards

Luigi

-- 
Ubuntu-mobile mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile

Reply via email to