#526 X failure, X_CreatePixmap, Shapefiles
when using Tigerline Shapefiles, zoom levels below ~512 cause Xastir to dump and the following message is diplayed in Xterm:
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Value in failed request: 0x0
Serial number of failed request: 461689
Current serial number in output stream: 461695
Versions & info -
Xastir 1.7.0 / Cygwin($ uname -a, CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 i686)
XTERM_VERSION="Cygwin 6.8.2.0(202)"
GNU/LessTif Version 2.1 Release 0.93.94
ImageMagick 6.0.4
xvertext routines Version 5.00
Built-in map types:
gnis USGS GNIS Datapoints
map APRSdos Maps
map WinAPRS/MacAPRS/X-APRS Maps
pdb PocketAPRS Maps
Support for these additional map types has been compiled in:
geo Image Map (ImageMagick library, many formats allowed)
geo URL (Internet maps via libcurl library)
shp ESRI Shapefile Maps (Shapelib library)
tif USGS DRG Geotiff Topographic Maps (libgeotiff/libproj)
xpm X Pixmap Maps (XPM library)
Has worked fine since installed a few years ago. I used it earlier this month in VA and had a county shapefile running there at zoom level 10. Upon return to FL, connected GPS and when system attempted to load Orange County Shapefile (auto maps enabled), error occured. I have tried changing position and forcing load of other Shapefiles, problem still occurs.
Works fine with static GEO images (converted UI-View maps). When connected to Internet, online Tiger maps work fine, at all zoom levels.
Thanks
Dean
kd4twj@arrl.net
21 oct 2008 -
Forget to mention previously that APRSdos maps worked fine at all levels too.
Due to the <overwhelming> response here ....
I finally had some more time to spend on this, after ~two months.
Without anything else to go on, I re-named the xastir.cnf file, effectively resetting my configuration to 0.
After doing a basic re-config and trying out shapefiles at close zoom levels, I am back in business.
Having compared the old and new xastir.cnf files, the only possible cause that I can find for the problem, is in the MAPS_LABEL_FONT statements.
It appears that there is some corruption in the following:
MAPS_LABEL_FONT_SMALL:8<E3>"
I was of the impression that the only font statement that applied to shapefiles was MAPS_LABEL_FONT_MEDIUM, but maybe not.
Of course, after struggling and living with this problem for a few months, I have discovered that we have newer / better Win32 environments to run Xastir in Windows. I am looking forward to trying out andLinux and see how that works. I would try VMWare, which I use for testing at work, however my EMCOMM Notebook just does not have the horsepower for that.
Dean
kd4twj@arrl.net
This bug has been fixed in CVS. Please retest against current repository.
Corruption of the configuration file and other text files would happen if the language environment if not set to a "C" compatible setup. The package has now been updated to establish a proper internal configuration for character type string manipulations.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).