Blender Fails To Start

[Scott Balneaves]

On Tue, Apr 20, 2010 at 02:12:05PM +0000, Lee Harr wrote:
> Scott Balneaves <sbalneav <at> legalaid.mb.ca> writes:
> 
> > 
> > On Tue, Feb 02, 2010 at 02:57:36PM -0700, Jim Christiansen wrote:
> > > Has anyone had this trouble?
> > > 
> > > :~#blender
> > > Compiled with Python version 2.6.2.
> > > Checking for installed Python... got it!
> > > X Error of failed request:  BadRequest (invalid request code or no such
> > > operation)
> > >   Major opcode of failed request:  137 (DRI2)
> > >   Minor opcode of failed request:  1 ()
> > >   Serial number of failed request:  23
> > >   Current serial number in output stream:  23
> > > 
> > > Blender installed without errors but won't start on a client.  I won't start
> > > on the server either from an sshed -Y conection...
> > 
> > More than likely a bug in how it's talking to X.  Any chance you can use ltrace
> > or similar to narrow down where it's failing?
> > 
> > Scott
> > 
> 
> 
> I am having the same trouble. I have the ltrace of starting up blender,
> but it is very long... Here is the end of it.

<snip>

> glXChooseVisual(0x9c801d8, 0, 0xbfea6490, 0, 1440X Error of failed request: 
> BadRequest (invalid request code or no such operation)
>   Major opcode of failed request:  137 (DRI2)
>   Minor opcode of failed request:  1 (DRI2Connect)
>   Serial number of failed request:  32
>   Current serial number in output stream:  32

This is the key bit here.  The glxChooseVisual() call's dying because
it can't connect to DRI, probably because either:

1) Your thin clients aren't supporting DRI
2) There's a bug in the DRI libraries somewhere in handling
   remote displays.

Here's a test: can you run glxgears on one of the thin clients?

That should give a simple test as to whether rendering's at all
possible.

Also, there may be a way to start blender without DRI being used.

Scott

-- 
Scott L. Balneaves | Try to relax and enjoy the crisis.
Systems Department |     -- Ashleigh Brilliant
Legal Aid Manitoba |