[MeeGo-dev] MeeGo UX in VirtualBox

Auke Kok auke-jan.h.kok at intel.com
Tue Jul 20 10:12:03 PDT 2010


On 07/20/10 08:01, Juerg Haefliger wrote:
> Hi Sivan,
>
>> List,
>>
>>   After googling around I saw there is no authoritative page with
>> proper instructions to get up MeeGo UX (the complete UX , not just X
>> booting or a very lightweight window manager) under VirtualBox for
>> either Intel or nVidia host GFX chips.
>>
>> I suggest anybody who had success doing so, put his findings and
>> instructions on this page[0] so we can later on tidy it up and have a
>> canonical place to start.
>
> I just started to get involved with MeeGo and I too ran into the
> problem of not being able to run the UI in VirtualBox nor on my
> laptop. I took a closer look at it but I must say I'm puzzled by how
> this is supposed to work.
>
> I can do the 'init 3' trick and then start the X server as root vi
> startx just fine. But trying to launch it via uxlaunch always fails
> with the following error:
> xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted.
>
> Basically, uxlaunch is doing the following:
> 1) activate /dev/tty2
> 2) change owner and group of /dev/tty2 to meego user/group
> 3) set uid and gid of calling process to meego user/group
> 4) setsid /* this always seems to fail but the return value is not checked?? */
> 5) launch Xorg on vt2
>
> Xorg itself is doing the following in xf86OpenConsole before it croaks
> with the above error:
> 1) setsid /* here they do some tricks to make it succeed */
> 2) fd = open /dev/tty2
> 3) ioctl (fd, VT_GETSTATE)
> 4) ioctl (fd, VT_ACTIVATE, 2) /* and this is the line that fails */
>
> Even if I login with user meego on tty2 I cannot start the X server as
> user meego on vt2. I'm not an expert on these permission things but
> something funny is going on. Anybody on the list care to explain how
> this is supposed to work?

ha

I'm the person who hacked up most of uxlaunch and should be able to 
explain you this.

However, I've seen the above issue as well and it appears that something 
in between pam and console permissions gets in the way of uxlaunch/XOrg.

I haven't tracked this problem down yet and it solely affects the case 
where the user has a console open - which changes the settings on the 
console.

uxlaunch *should* work, and it doesn't in all cases when launched from 
the console. Can you open a bugreport so we can start tracking this 
issue? I have no solution for now, other than that I need to dig into 
this particular issue...

Auke


More information about the MeeGo-dev mailing list