Re: [Xastir] constant warnings in term after update and ipv6 (updated) isn't broke

On Sat, Nov 17, 2018 at 01:33:17PM -0500, we recorded a bogon-computron collision of the flavor, containing: > Hi Tom, > ?? Hopefully this may help as additional troubleshooting info. > > ?? If I revert to the version I downloaded and installed on 30 Sep, I > do not get the Character

Re: [Xastir] Maps

I upgraded my laptop to Ubuntu 18.04 today, and I encountered the libcurl issue. The solution for me was to remove libcurl4-openssl-dev and install libcurl4-gnutls-dev. Recompiling Xastir after that change left me with an installation with maps working normally. In the map chooser, the

Re: [Xastir] constant warnings in term after update and ipv6 (updated) isn't broke

Hi Tom,     Hopefully this may help as additional troubleshooting info.     If I revert to the version I downloaded and installed on 30 Sep, I do not get the Character 260 warnings, so it must be something introduced to the code within the past 6 weeks. -Dj

Re: [Xastir] Weather Stations

I may have figured this out, partially. I was calling xastir_udp_client with both the -to_rf and -to_inet options in a single command, which was producing the unsupported packet. I changed my script to call xastir_udp_client twice, the first time with only -to_inet, and the second with only

Re: [Xastir] constant warnings in term after update and ipv6 (updated) isn't broke

On Sat, Nov 17, 2018 at 09:57:11AM -0700, we recorded a bogon-computron collision of the flavor, containing: > On Sat, Nov 17, 2018 at 10:54:58AM -0500, we recorded a bogon-computron > collision of the flavor, containing: > > I can confirm that doing: > > export LANG="C" > > then running

Re: [Xastir] constant warnings in term after update and ipv6 (updated) isn't broke

On Sat, Nov 17, 2018 at 10:54:58AM -0500, we recorded a bogon-computron collision of the flavor, containing: > I can confirm that doing: > export LANG="C" > then running Xastir in the same shell eliminates the "Character \260" > warning messages at initial startup. > > However, the messages

Re: [Xastir] constant warnings in term after update and ipv6 (updated) isn't broke

I can confirm that doing: export LANG="C" then running Xastir in the same shell eliminates the "Character \260" warning messages at initial startup. However, the messages start appearing after running awhile.  Moving the mouse cursor over the Xastir main screen seems to cause it. fyi -Dj

Re: [Xastir] Weather Stations

Hi Gerry,     Apologies for the late reply.  I've been out of town and am just getting back to this.     I've just changed the server to cwop.aprs.net as you suggest.  A few weather packets have been sent as of 10:40AM EST 17 Nov.     BTW, I am not running an Ambient weather station, I am

Re: [Xastir] constant warnings in term after update and ipv6 (updated) isn't broke

Hi Dave,     It is not isolated to your system. I just pulled a fresh copy of Xastir and compiled, and when I start it in a terminal from within X windows, I see many of: Warning:     Name: create_appshell text_output2     Class: XmTextField     Character '\260' not supported in font. 

Re: [Xastir] constant warnings in term after update and ipv6 (updated) isn't broke

Tom, I am still getting the character 260 warning. Just way way fewer than before, like only three warnings and then a "fopen: No such file or directory" statement that is leaving me clueless for now. With the limited amount of hours per week that I run Xastir, it is an annoyance that I can just