[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020110: Gempak5.6e for LINUX

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20020110: Gempak5.6e for LINUX
  • Date: Thu, 10 Jan 2002 13:19:35 -0700
Jim,


If may be that you are using GNOME which sets all colors to read-only.
Instead use KDE, TWM or one of the FWMx options.

If you want to use GNOME for all your desktop functions, then
set up your X server to run a second server and hotswap between
the servers.

Steve Chiswell
Unidata User Support






>From: address@hidden (James A Smith (address@hidden))
>Organization: UCAR/Unidata
>Keywords: 200201101757.g0AHvON06192

>Hi -
>
>  We recently downloaded GENPAK5.63 onto out LINUX 7.2 system. We are
>having color allocation problems which we have seen mentioned at several of
>the GEMPAK troublechooting sites.  However, the fix that is suggested does
>not help our problem:
>
>When we run ntl:
>
>
>[mlbaeck@indus linux]$ ntl
>Resource File: /usr/GEMPAK5.6e/resource/Ntop
>graphic, satellite, radar -- 33 95 20
>        Request total # of colors = 148
>X Error of failed request:  BadValue (integer parameter out of range for
>operation)  
>  Major opcode of failed request:  86 (X_AllocColorCells)
>  Value in failed request: 0X0
>  Serial Number of Failed Request: 390
>  Current Serial Number in Output Stream: 390
>
>
>and out default visual info from xdpyinfo:
>
>
>default visual id:  0x22
>  visual:
>    visual id:   0x22
>    class:    PseudoColor
>    depth:    8 planes
>    available colormap entries:    256
>    red, green, blue masks:    0x0, 0x0, 0x0 
>    significant bits in color specification:   8 bits
>
>
>
>If we run ntl -s32 or a smaller number we get the same error message.
>
>Have you encountered this problem and do you have any suggestion for a fix?
>
>
>Thank you,
>
>Jim Smith
>
>
>
>
>