Re: [Xastir] constant warnings in term after update and ipv6 might be partially broken again
Warning: Name: create_appshell text_input2 Class: XmTextField Charater '\260' not supported in font. Discarded I seem to remember such messages from several years back. I'll search through my email archives to see if there was a solution. -- Curt, WE7U.http://we7u.wetnet.net APRS Device Capabilities: http://we7u.wetnet.net/aprs_device_capabilities.html Coordinate Converter (Android): http://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] constant warnings in term after update and ipv6 might be partially broken again
I was not seeing these warnings on my primary BSD machine at all. But then I looked and saw that my LANG was set to a null string (which means everything is defaulting to C locale). When I set LANG to en_US.UTF-8 and restarted Xastir, the noise started. Clearing LANG and restarting made it stop. Try setting LANG=C or LANG="" (not LOCALE="C") and see if it goes away. On Sun, Nov 11, 2018 at 07:10:37AM -0800, we recorded a bogon-computron collision of the flavor, containing: > Question Curt: Do all language users need to do that? I just 'git > pulled/bootstrap/compile/install' and now my terminal window is flooded > with: > > Warning: > Name: create_appshell text_input2 > Class: XmTextField > Charater '\260' not supported in font. Discarded > > My locale is set to en_US.utf8 > > Also something has broken the IPV6 connection to firenet.aprs2.net (but not > rotate.aprs2.net). If I force my VM to use just IPV4 the connection works > (oh and the character warnings continue so they're not related to > firenet...). > > Dave > KD7MYC > > -Original Message- > From: Xastir [mailto:xastir-boun...@lists.xastir.org] On Behalf Of Curt, > WE7U > Sent: Monday, November 05, 2018 09:11 > > I had one instruction wrong regarding xfontsel on the web page. Updated it. > You must quit that program to get it to pass the selected font back to > Xastir. > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Tom RussoKM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] constant warnings in term after update and ipv6 might be partially broken again
IPV6 worked for rotate.aprs2.net but not firenet.aprs2.net...so it might have been something about IPV6 and the firenet pool of addresses...or it might be related to the interface order patches announced yesterday...I'll try the old version again and then git pull to update and try again. I have a real world interruption this AM but should have some ATUs this afternoon to try things again. And if I only try to fire up the firenet interface then any error message shouldn't scroll off since I won't be getting the character error with each new station received since a failed connection doesn't receive any data. Dave KD7MYC -Original Message- From: Xastir [mailto:xastir-boun...@lists.xastir.org] On Behalf Of Jason Godfrey Sent: Wednesday, November 14, 2018 08:11 Are you still having IPv6 issues? Was it not connecting at all if you have IPv6 enabled? - Jason On Sun, Nov 11, 2018 at 9:24 AM David Flood wrote: > I also tried LOCALE="C"...same errors... > > My locale is set to en_US.utf8 ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] constant warnings in term after update and ipv6 might be partially broken again
Are you still having IPv6 issues? Was it not connecting at all if you have IPv6 enabled? I have a busy streak but I can take a look when I have some free time. - Jason On Sun, Nov 11, 2018 at 9:24 AM David Flood wrote: > I also tried LOCALE="C"...same errors... > > -Original Message- > From: Xastir [mailto:xastir-boun...@lists.xastir.org] On Behalf Of David > Flood > Sent: Sunday, November 11, 2018 07:11 > > My locale is set to en_US.utf8 > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > -- "The problem with quotes on the Internet is that it is often difficult to verify their authenticity." - *Abraham Lincoln* ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] constant warnings in term after update and ipv6 might be partially broken again
I also tried LOCALE="C"...same errors... -Original Message- From: Xastir [mailto:xastir-boun...@lists.xastir.org] On Behalf Of David Flood Sent: Sunday, November 11, 2018 07:11 My locale is set to en_US.utf8 ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] constant warnings in term after update and ipv6 might be partially broken again
Question Curt: Do all language users need to do that? I just 'git pulled/bootstrap/compile/install' and now my terminal window is flooded with: Warning: Name: create_appshell text_input2 Class: XmTextField Charater '\260' not supported in font. Discarded My locale is set to en_US.utf8 Also something has broken the IPV6 connection to firenet.aprs2.net (but not rotate.aprs2.net). If I force my VM to use just IPV4 the connection works (oh and the character warnings continue so they're not related to firenet...). Dave KD7MYC -Original Message- From: Xastir [mailto:xastir-boun...@lists.xastir.org] On Behalf Of Curt, WE7U Sent: Monday, November 05, 2018 09:11 I had one instruction wrong regarding xfontsel on the web page. Updated it. You must quit that program to get it to pass the selected font back to Xastir. ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
