[Wine] Re: Wine Client Error:b: write: Bad file descriptor

[iwoloschin at gmail.com]

I can't say I remember the GLX message on the first day, though it
could have been there.

I looked at xorg.conf, and it's set to load glx, though it is also set
to load DRI, and while I haven't fooled around with xorg.conf settings
in a while, I remember there being problems with stuff like that.

The programs I am trying to run are actually all console, they were
originally run as services under Windows.  All I need is for them to
output to logfiles and/or console, I don't even need X for anything
related to Wine.  Is there a simple way to just disable all of the X
parts of Wine, or is it one of those things that's built in and not
worth it to take out?

Regardless of whether or not I need GLX to be running, I will try to
talk to IT and get them to see if they know why it's not functioning
properly.  I figure if it's set to load, it should be loading, even if
I don't need it for my purposes.

Thanks,
Ian


Daniel Skorka wrote:
> iwoloschin at gmail.com wrote:
> > http://users.wpi.edu/~woloi/wine.txt
> >
> > Obviously, running programs after this causes more errors and debug
> > messages to happen.
>
> =>1 0x7e67719f (0x7e67719f)
>   2 0x7ecea57c X11DRV_GDI_Finalize+0x2c in winex11.drv (0x7ecea57c)
>
> Interesting. You are lacking debuggin symbols, but the crash seems to
> happen when calling XCloseDisplay. Why that happens I can only
> speculate. Can you convince you admin to let the X server load the
> GLX extension?
>
> > The oddest part is, I don't believe I was getting errors like this the
> > first day or so that I was testing on this computer, yet nothing (that
> > I know of) has changed on this computer.
>
> Did that message about GLX appear on the first day, too?
> 
> Daniel