I killed the two processes that were running and moved .xastir like you suggested. Xastir is now up and running. Now it's time to start playing with the maps. I'll let you know how it goes.
Thanks! 73, Hank Lambert KB4MTO/TA5ZC [email protected] [email protected] www.hanklambert.com PGP Key: 0x96D33D71 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tom Russo Sent: Monday, January 10, 2011 8:22 PM To: Xastir - APRS client software discussion Subject: Re: [Xastir] New User On Mon, Jan 10, 2011 at 07:17:10PM -0500, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: > Well I followed the Ubuntu 10.04 How-to for installing Xastir, including the > installation of GDAL. Everything went fine and I encountered no errors > during installation. Xastir, however, will not start. When I go to launch > it, this is what is displayed: > > h...@mint10 ~ $ xastir > Found pid file: /home/hank/.xastir/xastir.pid > Other Xastir process, pid: 6238 does not appear be running. > > [...] > > x_spider: Can't bind local address > Could some processes still be running from a previous run of Xastir? > Error: BindingCould some processes still be running from a previous run of > Xastir? > UDP_Server process died. > x_spider: Couldn't set read-end of pipe_udp_server_to_xastir non-blocking > Could some processes still be running from a previous run of Xastir? > XReadBitmapFile() failed: Bitmap not found? > /usr/share/xastir/symbols/2x2.xbm > XReadBitmapFile() failed: Bitmap not found? > /usr/share/xastir/symbols/2x2.xbm > h...@mint10 ~ $ Is there any process named "xastir" actually running? ps auxww | grep xastir If so, kill -9 it. You also seem not to have removed your .xastir directory, because it's trying to look for files in /usr/share/xastir, which is where the synaptic-installed version would have put things. Your scratch-built version should be looking in /usr/local/share/xastir. This is controlled by the file xastir.cnf in your .xastir/config directoy. It was first created by the synaptic version you installed, and is now pointing to the wrong place. So: mv .xastir dot_xastir_old and restart (after killing any stray old processes). It should regenerate your .xastir directory and repopulate it appropriately. You'll have to re-enter all of your callsign/callpass/interface data if you do it that way. But it's a clean, fresh start. The other option you can take rather than moving .xastir is to edit .xastir/config/xastir.cnf and change all the places where it refers to /usr/share and replace them with /usr/local/share. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "The truth will set you free, but first it will piss you off." _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
