[GRASS5] xdriver: Unable to get sufficient colors
Glynn Clements
glynn.clements at virgin.net
Wed Jun 27 11:15:06 EDT 2001
Robert Lagacé wrote:
> > > > I have fresh devel and stable grass50 here with following problem:
> > > >
> > > > d.mon in stable branch:
> > > >
> > > > d.mon start=x0
> > > > using default visual which is PseudoColor
> > > > ERROR: Unable to get sufficient colors
> > > > No socket to connect to for monitor <x0>.
> > > > Problem selecting x0. Will try once more
> > > > No socket to connect to for monitor <x0>.
> > > >
> > > > I have 256 colors only here on KDE2.1/RH7.1. It starts OK in devel branch.
> > >
> > > Has the colourmap been consumed by existing clients? Does the problem
> > > occur if the monitor is the only program running using the display?
> >
> > Thanks. It works after X restart. No other program was running (except console), I know that
> > problem. It seems that if konqueror (other apps?) is started and closed, its colors are still in use.
>
> Can we avoid the color problem using a private color map as it is possible in
> Netscape (using the command nestcape -install) ? Doing that, GRASS can use any
> color with only a drawback, the other appliactions get bizare colors when not
> focus.
That would be simple enough. It already uses a private colourmap if
it's using a visual other than the default, or when using a
DirectColor visual.
I'll add this today (assuming that the CVS stays up).
--
Glynn Clements <glynn.clements at virgin.net>
More information about the grass-dev
mailing list