Build complete, on to runtime errors (was Re: [sugar] sugar-jhbuild changes)

[Tomeu Vizoso]

On Thu, 2007-02-08 at 21:24 -0500, Mike Hunter wrote:
> Hey everybody,
> 
> On Feb 08 at 22:28, Marco Pesenti Gritti wrote:
> 
> > On Thu, 2007-02-08 at 08:29 -0500, Mike Hunter wrote:
> > > > > 
> > > Then ended up here:
> > > 
> > > 
> > > python setup.py install /home/mhunter/sugar-jhbuild/build
> > > Need pysqlite version 2 or higher (http://pysqlite.org/)
> > > *** error during stage install of penguintv: ########## Error running python setup.py install /home/mhunter/sugar-jhbuild/build *** [21/23]
> > > 
> > > But you said somebody's working on pysqlite...so I guess that's kinda good!  :)
> > > > 
> > 
> > This should be fixed now.
> 
> Thanks, my build completed successfully.
> 
> I tried
> 
> ./sugar-jhbuild run
> 
> But I got wacky results.  At the console I got:
> 
> Running the installed sugar...
> error opening security policy file /usr/lib/xserver/SecurityPolicy
> Extended Input Devices not yet supported. Impelement it at line 625 in ../../../../hw/kdrive/src/kinput.c
>     xkb_keycodes             { include "xfree86+aliases(qwerty)" };
>     xkb_types                { include "complete" };
>     xkb_compatibility        { include "complete" };
>     xkb_symbols              { include "pc(pc101)+us" };
>     xkb_geometry             { include "pc(pc101)" };
> Could not init font path element /usr/share/fonts/X11/TTF/, removing from list!
> Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
> Could not init font path element /usr/share/fonts/X11/CID/, removing from list!
> Couldn't start XPCOM.Segmentation fault (core dumped)
> 
> It launched a gui window, but the window was filled with an x-server-looking
> grey checkerboard type pattern, but with wavy vertical bands (almost
> like refresh hz aliasing).
> 
> I can't seem to find a core file, let me know if I should go after that.

Hi Mike,

I got the same error, but vanished when I updated and rebuilt xulrunner
and sugar. I guess there was a temporary bug in mozilla.

Cheers,

Tomeu