LANG=C is required if you want to write and read back in config files. It messes up how the strings get written out and read back in using any of:
printf fprintf sprintf scanf fscanf On Wed, Mar 25, 2015 at 4:21 PM, Tom Russo <[email protected]> wrote: > On Wed, Dec 31, 2014 at 11:47:06PM -0700, we recorded a bogon-computron > collision of the <[email protected]> flavor, containing: >> Have had this issue a few times recently while trying to use Xastir on >> Ubuntu 14.04 during SAR missions. >> >> After a few uses of dialog boxes, suddenly am finding that I can't type into >> the text fields. This seems unrelated to keyboard focus issues, and I >> haven't >> correlated it with any particular events during the run. >> >> The issue is cleared if I exit Xastir and restart, but returns after a few >> uses. >> >> I can paste data into the text boxes by typing into another window, >> highlighting text, and then middle-clicking the text box. It applies to all >> dialogs --- object creation, messaging, coordinate calculator, you name it. >> >> Has anyone else seen this crop up? >> >> Windowing system is "gnome flashback." Wondering if there's some weird >> Motif/Gnome3 interaction problem. Have not yet tried it under Unity (which I >> hate (hate, hate, hate)). >> >> Since this impacts object and message input, it makes for a very bad problem >> during active SAR missions, and I'd like to start nailing it down. I'm >> working an ELT mission as I type this, and the issue resurfaced after exactly >> two dialog boxes. > > I just thought I'd follow up on that, as I appear to have found the trigger > for the problem, if not its source and solution. > > On my Ubuntu laptop I've created an Xastir icon (launcher) to double click > for ease of access. I had set this launcher up to run "env LANG=C xastir" > instead of just "xastir." Only when I started running xastir from the > command line to track down the issue did I find that it appears this > LANG setting is what's breaking it for me. > > By running xastir from the command line with and without the "env LANG=C" I > can > pretty well conclude that doing the LANG setting is what triggers this > annoying bug, which must be a bug in openmotif or its interaction with > the gnome3/flashback desktop. Without "env LANG=C", the dialog boxes never > break, and with "env LANG=C" they break almost immediately upon doing anything > that changes the dialog shape (selecting "Probability circles" or "Signpost", > and so forth). Once broken, ALL dialogs are broken -- no keyboard input into > any text box works. > > So if you are seeing this problem, and you are using LANG=C in the start-up, > then try it without. > > I do not recall what problems the default LANG was causing, but this one issue > alone has bitten me so many times recently that I'm going to stop setting > this on Ubuntu. I don't think I have enough information to make this into > an openmotif bug report, though. And from the look of the openmotif issue > tracker (which has all bugs in the NEW state, many of them not touched since > 1997), opening one seems pointless anyway. > > -- > Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ > Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > _______________________________________________ > Xastir mailing list > [email protected] > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7U _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
